View Issue Details

IDProjectCategoryView StatusLast Update
0001148bareos-core[All Projects] directorpublic2019-12-07 17:21
ReporterbozoniusAssigned To 
PriorityhighSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSDebianOS Version9
Product Version18.2.5 
Fixed in Version 
Summary0001148: How to cancel "waiting" job (status = "Created")
DescriptionThere really needs to be a clean way to cancel jobs no matter what state they are in. I have a job that failed because it could not contact the client file daemon. I also had another job having an unrelated issue that required restarting the bareos storage daemon. (The problem there was the packet size too big; I had set the network buffer size too large.)

Since it was the only job I wanted to cancel, I tried using "cancel all status=waiting" and "cancel all status=created" (I tried the latter since the client status indicated the job was in the "Created" state; I also tried "cancel all status=Created" thinking maybe the case could matter in some contexts). None of these worked. I even tried "cancel all yes" to no avail; every one of these came back with "No jobs running."
Steps To ReproduceTerminate and restart the storage daemon while a job is in this "created" state. The job cannot be terminated.
Additional InformationThe director and storage daemons are running on the same server. In this case, client was on different system.
TagsNo tags attached.
bareos-master: impact
bareos-master: action
bareos-19.2: impact
bareos-19.2: action
bareos-18.2: impact
bareos-18.2: action
bareos-17.2: impact
bareos-17.2: action
bareos-16.2: impact
bareos-16.2: action
bareos-15.2: impact
bareos-15.2: action
bareos-14.2: impact
bareos-14.2: action
bareos-13.2: impact
bareos-13.2: action
bareos-12.4: impact
bareos-12.4: action

Activities

There are no notes attached to this issue.

Issue History

Date Modified Username Field Change
2019-12-07 17:21 bozonius New Issue