View Issue Details

IDProjectCategoryView StatusLast Update
0001248bareos-core[All Projects] directorpublic2020-06-09 11:59
Reporter205946a8b92Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status newResolutionopen 
PlatformLinuxOSDebianOS Version10
Product Version19.2.7 
Fixed in Version 
Summary0001248: SIGSEGV with incorrect time specification
DescriptionSegmentation fault while parsing a Schedule resource
Steps To Reproduce1. Add a Schedule resource with an incorrectly set time, for example, “02:00 am” (space before “am”);
Schedule {
 Name = am_02_00_everyday;
 Run = daily at 02:00 am;
}
2. Update the resource using bconsole:
*reload sche
3. bareos-dir will be killed; log entry:
ERROR in dird/run_conf.cc:406 Config error: Job type field: am in run record not found
: line 3, col 24 of file /etc/bareos/bareos-dir.d/schedule/am_02_00_everyday.conf
Run = daily at 02:00 am;
ERROR in dird/run_conf.cc:464 Config error: Time logic error.
: line 3, col 24 of file /etc/bareos/bareos-dir.d/schedule/am_02_00_everyday.conf
Run = daily at 02:00 am;
BAREOS interrupted by signal 11: Segmentation violation
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
2020-06-09 11:59 205946a8b92 New Issue