View Issue Details

IDProjectCategoryView StatusLast Update
0000843bareos-core[All Projects] directorpublic2019-02-27 08:58
ReportervshkolinAssigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status newResolutionopen 
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

Activities

MarceloRuiz

MarceloRuiz

2018-03-09 02:56

reporter   ~0002939

Last edited: 2018-03-09 03:04

View 2 revisions

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

 ==== bactrace output ====

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

IvanBayan

IvanBayan

2019-02-27 08:56

reporter   ~0003273

Today same happened to me, I've hit reload and bareos have crashed:
Feb 27 02:52:48 mia-backup03 bareos-dir[35840]: BAREOS interrupted by signal 11: Segmentation violation
root@mia-backup03:/var/log/bareos# apt-cache policy bareos-director
bareos-director:
  Installed: 18.2.5-139.1
  Candidate: 18.2.5-139.1
  Version table:
 *** 18.2.5-139.1 500
        500 http://download.bareos.org/bareos/release/latest/xUbuntu_16.04 Packages
        100 /var/lib/dpkg/status
     14.2.6-3 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
IvanBayan

IvanBayan

2019-02-27 08:58

reporter   ~0003274

$ sudo dmesg|tail -n1
[71272674.289931] bareos-dir[20454]: segfault at 7fec1b7fe9d0 ip 00007fec278f08d9 sp 00007fec1a7fa858 error 4 in libpthread-2.23.so[7fec278e8000+18000]

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
2019-02-27 08:56 IvanBayan Note Added: 0003273
2019-02-27 08:58 IvanBayan Note Added: 0003274