Bug 87592 – bacula-dir crashes when trying to schedule a job from bconsole using 1.36.0

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Jeffrey Crawford 2005-04-01 13:00:25 UTC]

This only seems to occure when trying to schedule a backup job from "bconosle" for an arbitray time in the future. I have set up an example:

===============================================================================
akebono root # /etc/bacula/bconsole
Connecting to Director akebono:9101
1000 OK: akebono-dir Version: 1.36.0 (20 October 2004)
Enter a period to cancel a command.
*run
Using default Catalog name=ProTradeCatalog DB=bacula
A job name must be specified.
The defined Job resources are:
     1: Brady
     2: Beckham
     3: Ali
     4: Pele
     5: Practice1
     6: Akebono
     7: Aaron
     8: Vpn
     9: Fw
    10: BackupCatalog
    11: RestoreTemplate
Select Job resource (1-11): 1
Run Backup job
JobName:  Brady
FileSet:  BeckhamBradyFiles
Level:    Incremental
Client:   brady-fd
Storage:  Tape
Pool:     AutoChanger
When:     2005-04-01 12:25:20
Priority: 10
OK to run? (yes/mod/no): mod
Parameters to modify:
     1: Level
     2: Storage
     3: Job
     4: FileSet
     5: Client
     6: When
     7: Priority
     8: Pool
Select parameter to modify (1-8): 6
Please enter desired start time as YYYY-MM-DD HH:MM:SS (return for now): 2005-04-01 13:00:00
Run Backup job
JobName:  Brady
FileSet:  BeckhamBradyFiles
Level:    Incremental
Client:   brady-fd
Storage:  Tape
Pool:     AutoChanger
When:     2005-04-01 13:00:00
Priority: 10
OK to run? (yes/mod/no): mod
Parameters to modify:
     1: Level
     2: Storage
     3: Job
     4: FileSet
     5: Client
     6: When
     7: Priority
     8: Pool
Select parameter to modify (1-8): 8
The defined Pool resources are:
     1: AutoChanger
     2: Persistant
Select Pool resource (1-2): 2
Run Backup job
JobName:  Brady
FileSet:  BeckhamBradyFiles
Level:    Incremental
Client:   brady-fd
Storage:  Tape
Pool:     Persistant
When:     2005-04-01 13:00:00
Priority: 10
OK to run? (yes/mod/no): yes
Job started. JobId=1566
*message
bconsole:  Error: bnet.c:403 Write error sending to Director daemon:akebono:9101: ERR=Broken pipe
===============================================================================

After this point bacula-dir is no longer running and I recieved the following in an email:

===============================================================================
akebono-dir: Job Brady.2005-04-01_12.10.58 waiting 31742 seconds for scheduled start time.
akebono-dir: ABORTING due to ERROR in jobq.c:184
Mutex lock failure. ERR=Invalid argument
===============================================================================

I can only get the system to crash if I change the "When" field all others do not seem to have any effect. My workaround is to schedule a job using at and a script file.

Reproducible: Always
Steps to Reproduce:
See Above

Actual Results:  
See Above

Expected Results:  
Job to run as scheduled

[Comment 1 Arnaud Launay 2005-08-09 07:21:49 UTC]

Could you try with bacula 1.36.3 please ?

[Comment 2 Jeffrey Crawford 2005-08-16 07:51:23 UTC]

Sorry for the delay. I will try with the new version as soon as I can this is
running on a production system. It may take me a couple of days

[Comment 3 Arnaud Launay 2005-10-20 08:45:58 UTC]

1.36.3 is out in the stable tree, this is probably fixed. Jeffrey ?

[Comment 4 Jeffrey Crawford 2005-10-23 21:47:45 UTC]

I was able to schedule a job for the future after upgrading so I think this is
now ok

[Comment 5 Arnaud Launay 2005-10-27 10:56:42 UTC]

Fixed by new version, then. Could you please close it ? I don't have enough
permissions.

[Comment 6 Chris Lee (RETIRED) 2005-11-22 14:58:00 UTC]

Fixed in 1.36.3.  Please reopen if necessary.