Bareos Bug Tracker
Bareos Bug Tracker

View Issue Details Jump to Notes ] Issue History ] Print ]
IDProjectCategoryView StatusDate SubmittedLast Update
0000843bareos-core[All Projects] directorpublic2017-08-10 22:392018-03-09 03:04
Assigned To 
PlatformLinuxOSCentOSOS Version7
Product Version16.2.4 
Target VersionFixed in Version 
Summary0000843: bareos-dir crashed with Segfault when parsing config files with job type = consolidate w/o pool and storage definition
DescriptionJob {
  Name = "Consolidate"
  Type = "Consolidate"
  Accurate = "yes"
  Max Full Consolidations = 1
  Client = bareos.home.loc
  FileSet = "SelfTest"

# Storage = File
# Pool = Incremental
[root@bareos ai]# bareos-dir -u bareos -g bareos -t -v
BAREOS interrupted by signal 11: Segmentation violation
Kaboom! bareos-dir, bareos-dir got signal 11 - Segmentation violation. Attempting traceback.
Kaboom! exepath=/etc/bareos/bareos-dir.d/ai
Calling: /etc/bareos/bareos-dir.d/ai/btraceback /etc/bareos/bareos-dir.d/ai/bareos-dir 8216 /var/lib/bareos
execv: /etc/bareos/bareos-dir.d/ai/btraceback failed: ERR=No such file or directory
The btraceback call returned 255
Dumping: /var/lib/bareos/bareos-dir.8216.bactrace
Steps To Reproduce1. Install and configure bareos-dir
2. Add consolidate job w/o pool and storage definition
3. Run bareos-dir -> Segmentation violation
4. Uncomment storage and pool definition
5. Run bareos-dir -> config is successfully parsed with diagnostic '"Messages" directive in Job "Consolidate" resource is required'
6. Comment storage and pool definition
7. Run bareos-dir -> Segmentation violation

Checked on two systems with same result.
TagsNo tags attached.
bareos-master: impact
bareos-master: 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
Attached Files

- Relationships

-  Notes
MarceloRuiz (reporter)
2018-03-09 02:56
edited on: 2018-03-09 03:04

I have the same problem...
The backtrace is:

 ==== bactrace output ====

Attempt to dump locks
Attempt to dump current JCRs. njcrs=0
 ==== End baktrace output ====

- Issue History
Date Modified Username Field Change
2017-08-10 22:39 vshkolin New Issue
2018-03-09 02:56 MarceloRuiz Note Added: 0002939
2018-03-09 03:04 MarceloRuiz Note Edited: 0002939 View Revisions

Copyright © 2000 - 2018 MantisBT Team
Powered by Mantis Bugtracker