View Issue Details

IDProjectCategoryView StatusLast Update
0000843bareos-core[All Projects] directorpublic2019-12-20 11:21
ReportervshkolinAssigned To 
PrioritynormalSeveritycrashReproducibilityalways
Status acknowledgedResolutionopen 
PlatformLinuxOSCentOSOS Version7
Product Version16.2.4 
Fixed 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-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

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]
arogge

arogge

2019-07-12 10:33

developer   ~0003449

Can you please reproduce this with our latest nightly-build from https://download.bareos.org/bareos/experimental/nightly/ ?
Thank you!
ironiq

ironiq

2019-12-12 10:24

reporter   ~0003660

Hi!
Same happened with me today:

root@nas:~# apt-cache policy bareos-director
bareos-director:
  Installed: 18.2.5-147.2
  Candidate: 18.2.5-147.2
  Version table:
 *** 18.2.5-147.2 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://cz.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages
root@nas:~# bareos-dir -u bareos -g bareos -t -v
BAREOS interrupted by signal 11: Segmentation violation
Segmentation fault (core dumped)
root@nas:~# dmesg|tail -n1
[63085.221143] bareos-dir[19067]: segfault at 7fb75836f510 ip 00007fb75836f510 sp 00007ffc7c79b1f8 error 14 in locale-archive[7fb758ade000+2d8000]
root@nas:~#
ironiq

ironiq

2019-12-12 10:47

reporter   ~0003661

It's happening only when running the "bareos-dir" with "-t" option. Attached a console output with "-d 300" and a part with "-d 900". If running without "-t" everything seems working.

bareos-dir.debug (16,760 bytes)
arogge

arogge

2019-12-18 15:52

developer   ~0003698

Thanks for the report.
Could you try to reproduce the issue in the nightly-build from https://download.bareos.org/bareos/experimental/nightly/ so we don't go chasing bugs that have already been fixed?

Thank you!
ironiq

ironiq

2019-12-18 16:06

reporter   ~0003699

Hi!

Here is the result:
root@nas:~# bareos-dir -t -f
BAREOS interrupted by signal 11: Segmentation violation
Segmentation fault (core dumped)
root@nas:~# bareos-dir -?

pre-release versions are UNSUPPORTED.
Get a released version and vendor support on https://www.bareos.com
Copyright (C) 2013-2019 Bareos GmbH & Co. KG
Copyright (C) 2000-2012 Free Software Foundation Europe e.V.
Copyright (C) 2010-2017 Planets Communications B.V.

Version: 19.2.4~pre1228.1b4462ef8 (18 December 2019) Linux-3.10.0-1062.9.1.el7.x86_64 ubuntu Ubuntu 16.04 LTS

Usage: bareos-dir [options]
        -c <path> use <path> as configuration file or directory
        -d <nn> set debug level to <nn>
        -dt print timestamp in debug output
        -f run in foreground (for debugging)
        -g <group> run as group <group>
        -m print kaboom output (for debugging)
        -r <job> run <job> now
        -s no signals (for debugging)
        -t test - read configuration and exit
        -u <user> run as user <user>
        -v verbose user messages
        -xc print configuration and exit
        -xs print configuration file schema in JSON format and exit
        -? print this message.
root@nas:~#
arogge

arogge

2019-12-18 16:23

developer   ~0003700

Thanks.
We'll look into it.
lborek

lborek

2019-12-20 11:19

reporter   ~0003710

Last edited: 2019-12-20 11:21

View 2 revisions

Same problem here for 18.2.5-147.2 and Ubuntu 16.04. But we don't use consolidate job in config.

To fix bareos-dir startup for Ubuntu :

root@:/etc# cat ./systemd/system/bareos-dir.service | grep "ExecStartPre"
#ExecStartPre=/usr/sbin/bareos-dir -t -f
root@:/etc# systemctl daemon-reload
root@:/etc# service bareos-dir start


Thanks.

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
2019-07-12 10:33 arogge Status new => feedback
2019-07-12 10:33 arogge Note Added: 0003449
2019-12-12 10:24 ironiq Note Added: 0003660
2019-12-12 10:47 ironiq File Added: bareos-dir.debug
2019-12-12 10:47 ironiq Note Added: 0003661
2019-12-18 15:52 arogge Note Added: 0003698
2019-12-18 16:06 ironiq Note Added: 0003699
2019-12-18 16:23 arogge Status feedback => acknowledged
2019-12-18 16:23 arogge Note Added: 0003700
2019-12-20 11:19 lborek Note Added: 0003710
2019-12-20 11:21 lborek Note Edited: 0003710 View Revisions