View Issue Details

IDProjectCategoryView StatusLast Update
0001101bareos-core[All Projects] directorpublic2019-07-29 17:31
ReporterprogseregaAssigned To 
PriorityhighSeveritycrashReproducibilityhave not tried
Status feedbackResolutionopen 
PlatformLinuxOSDebianOS Version9
Product Version17.2.4 
Target VersionFixed in Version 
Summary0001101: bareos-dir segfault after start new job to run
Descriptionиюл 15 12:01:51 bareos kernel: bareos-dir[889]: segfault at 0 ip 00007f3b7b8fcda1 sp 00007f3b6f7fc658 error 4 in libbareos-17.2.4.so[7f3b7b8e2000+6b000]
Steps To Reproduce1. create new backup job
2. add to director
3. reload director (all good),
4. start job
5. see in webui that job started and work
6. some time after that bareos-dir is segfault
Additional InformationI get develop files for bareos and try start it in debugger, but can not:

Starting program: /usr/sbin/bareos-dir
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Inferior 1 (process 31748) exited normally]
(gdb) r
Starting program: /usr/sbin/bareos-dir
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Inferior 1 (process 31796) exited normally]
(gdb)
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

arogge

arogge

2019-07-17 11:20

developer   ~0003496

Please install the debug package (bareos-dbg on debian) and attach the latest generated traceback (/var/lib/bareos/*.traceback).
Thank you!
progserega

progserega

2019-07-19 03:24

reporter   ~0003498

bareos-dbg was installed. Attach traceback from this bug

bareos.867.traceback (636 bytes)
arogge

arogge

2019-07-19 08:04

developer   ~0003499

That did not (yet) work as expected.
Does the bareos-dbg package match your other installed bareos packages?
gdb in the traceback doesn't seem to load the symbol table, so there's no meaningful traceback information.

You can try this with "btraceback test <pid-of-bareos-process> /tmp". This should write a traceback for a running bareos program to /tmp/bareos.<pid-of-bareos-process>.traceback and it should contain debug symbols and the stack traces for each running thread.
Once you get that working (usually just by installing gdb and the right version of bareos-dbg) crashes will generate a meaningful traceback that we can look at.
progserega

progserega

2019-07-29 08:09

reporter   ~0003529

dpkg-query -l|grep 'bareos\|gdb'
ii bareos-bconsole 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - text console
ii bareos-client 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - client metapackage
ii bareos-common 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - common files
ii bareos-database-common 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - common catalog files
ii bareos-database-postgresql 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - PostgreSQL backend
ii bareos-database-tools 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - database tools
ii bareos-dbg 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - debugging symbols
ii bareos-devel 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - development files
ii bareos-director 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - director daemon
ii bareos-filedaemon 17.2.4-9.1 amd64 Backup Archiving Recovery Open Sourced - file daemon
ii bareos-webui 17.2.4-15.1 all Backup Archiving Recovery Open Sourced - webui
ii gdb 7.12-6 amd64 GNU Debugger
ii libgdbm3:amd64 1.8.3-14 amd64 GNU dbm database routines (runtime version)

'"btraceback test <pid-of-bareos-process> /tmp ' succsess create file.

Sorry, I was not attach core file for bareos.867.traceback:
https://yadi.sk/d/i2s-Rs1mOjxxuA (it is more then 5 mb)
arogge

arogge

2019-07-29 17:31

developer   ~0003531

Thanks, but we really need the traceback muck more than the core file.

Issue History

Date Modified Username Field Change
2019-07-17 03:10 progserega New Issue
2019-07-17 11:20 arogge Status new => feedback
2019-07-17 11:20 arogge Note Added: 0003496
2019-07-19 03:24 progserega File Added: bareos.867.traceback
2019-07-19 03:24 progserega Note Added: 0003498
2019-07-19 03:24 progserega Status feedback => new
2019-07-19 08:04 arogge Status new => feedback
2019-07-19 08:04 arogge Note Added: 0003499
2019-07-29 08:09 progserega Note Added: 0003529
2019-07-29 08:09 progserega Status feedback => new
2019-07-29 17:31 arogge Status new => feedback
2019-07-29 17:31 arogge Note Added: 0003531