View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000406bareos-coredirectorpublic2015-01-23 14:222015-04-16 22:50
Reporterskeal Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionunable to reproduce 
PlatformLinuxOSUbuntuOS Version14.04
Product Version14.2.2 
Summary0000406: Second Job in jobs config file always ignored
DescriptionI've created my own jobs_global.conf which i've attached.

As you can see, there is a Dummy entry for a Dummy job. Only when this or any other job is defined the next job is used in the scheduler.

This is without dummy-entry:

status scheduler
Scheduler Jobs:


Schedule Jobs Triggered
===========================================================
WeeklyCycle
                       BackupOpossumwinOCFull
                       BackupOpossumConfigsFull
                       BackupYavdrConfigsFull
                       BackupOpossumwinOCIncr
                       BackupOpossumwinFotografieIncr
                       BackupOpossumConfigsIncr
                       BackupYavdrConfigsIncr

WeeklyCycleAfterBackup
                       BackupCatalog

====

Scheduler Preview for 7 days:

Date Schedule Overrides
==============================================================
Fr 23-Jan-2015 21:00 WeeklyCycle Level=Incremental
Fr 23-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Sa 24-Jan-2015 21:00 WeeklyCycle Level=Incremental
Sa 24-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
So 25-Jan-2015 21:00 WeeklyCycle Level=Full
So 25-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Mo 26-Jan-2015 21:00 WeeklyCycle Level=Incremental
Mo 26-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Di 27-Jan-2015 21:00 WeeklyCycle Level=Incremental
Di 27-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Mi 28-Jan-2015 21:00 WeeklyCycle Level=Incremental
Mi 28-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Do 29-Jan-2015 21:00 WeeklyCycle Level=Incremental
Do 29-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
====

-------------------------------

This is with dummy entry:

status scheduler
Scheduler Jobs:


Schedule Jobs Triggered
===========================================================
WeeklyCycle
                       BackupOpossumwinFotografieFull
                       BackupOpossumwinOCFull
                       BackupOpossumConfigsFull
                       BackupYavdrConfigsFull
                       BackupOpossumwinOCIncr
                       BackupOpossumwinFotografieIncr
                       BackupOpossumConfigsIncr
                       BackupYavdrConfigsIncr

WeeklyCycleAfterBackup
                       BackupCatalog

====

Scheduler Preview for 7 days:

Date Schedule Overrides
==============================================================
Fr 23-Jan-2015 21:00 WeeklyCycle Level=Incremental
Fr 23-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Sa 24-Jan-2015 21:00 WeeklyCycle Level=Incremental
Sa 24-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
So 25-Jan-2015 21:00 WeeklyCycle Level=Full
So 25-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Mo 26-Jan-2015 21:00 WeeklyCycle Level=Incremental
Mo 26-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Di 27-Jan-2015 21:00 WeeklyCycle Level=Incremental
Di 27-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Mi 28-Jan-2015 21:00 WeeklyCycle Level=Incremental
Mi 28-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
Do 29-Jan-2015 21:00 WeeklyCycle Level=Incremental
Do 29-Jan-2015 23:10 WeeklyCycleAfterBackup Level=Full
====
Steps To ReproduceAdd or remove the dummy entry (DummyFull) in jobs_global.conf
TagsNo tags attached.

Activities

skeal

skeal

2015-01-23 14:22

reporter  

bareos.tar.gz (7,299 bytes)
stephand

stephand

2015-01-23 18:55

developer   ~0001212

There is an unterminated string in
  Write Bootstrap = "|/usr/bin/bsmtp -h localhost -f \"\(Bareos\) \" -s \"Boots$

in your jobs_global.conf

That line normally looks like this:
  Write Bootstrap = "|/usr/sbin/bsmtp -h localhost -f \"\(Bareos\) \" -s \"Bootstrap for Job %j\" root@localhost"

Do you see any error in /var/log/bareos/bareos.log when do reload in bconsole?
May be that this case can not be easily detected as misconfiguration.
Looks like that's why the first Job definition is ignored.

Could you please try to correct your Write Bootstrap line and try again?

Regards

Issue History

Date Modified Username Field Change
2015-01-23 14:22 skeal New Issue
2015-01-23 14:22 skeal File Added: bareos.tar.gz
2015-01-23 18:55 stephand Note Added: 0001212
2015-01-23 18:55 stephand Assigned To => stephand
2015-01-23 18:55 stephand Status new => feedback
2015-04-16 22:50 mvwieringen Assigned To stephand =>
2015-04-16 22:50 mvwieringen Status feedback => closed
2015-04-16 22:50 mvwieringen Resolution open => unable to reproduce