View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0001148bareos-coredirectorpublic2019-12-07 17:212023-09-05 16:00
Reporterbozonius Assigned Tobruno-at-bareos  
PriorityhighSeverityminorReproducibilityalways
Status closedResolutionno change required 
PlatformLinuxOSDebianOS Version9
Product Version18.2.5 
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.

Activities

bruno-at-bareos

bruno-at-bareos

2023-09-05 16:00

manager   ~0005377

Hello there, cleaning our bugs entries this summer, we would like to ask if you can still reproduce this with recent version of Bareos like 22.1.0 for example.
We don't think there's a bug here, but a misuse of the command
The help command would have show you the way to achieve correctly your command
*help cancel
  Command Description
  ======= ===========
  cancel Cancel a job

Arguments:
        storage=<storage-name> |
        jobid=<jobid> |
        job=<job-name> |
        ujobid=<unique-jobid> |
        state=<job_state> |
        all yes

so either it is "all" either you can use "state=XXX" not both.

Issue History

Date Modified Username Field Change
2019-12-07 17:21 bozonius New Issue
2023-09-05 16:00 bruno-at-bareos Assigned To => bruno-at-bareos
2023-09-05 16:00 bruno-at-bareos Status new => closed
2023-09-05 16:00 bruno-at-bareos Resolution open => no change required
2023-09-05 16:00 bruno-at-bareos Note Added: 0005377