bacula-fd segfault on status client from Bat
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bacula (Ubuntu) |
Triaged
|
Low
|
Unassigned |
Bug Description
Architecture: armhf - bacula-fd, bacula-dir, bacula-sd, bconsole (hostname: selene)
amd64 - bacula-console-qt (bat)
Ubuntu versions: Bionic and cosmic (bionic bat was on Mint 19, cosmic bat is Ubuntu 18.10)
Bacula versions 9.0.6 and 9.0.8
Repeatable: Yes,every time
From Bat (bacula-console-qt) select clients, right-click on the client for selene and choose Status Client.
Within seconds the bacula-fd crashes, bat shows a could not connect error message in the console page.
This only happens to the bacula-fd on the armhf host, which also has the bacula server running. All the other clients (a mix of Windows & Linux 32 and 64bit) from version 5.2.10 onwards) work fine.
I've just found that running status client for selene-fd in bconsole on cosmic/bacula 9.0.8 works properly, don't know if worked on bionic/bacula 9.0.6 or not. Too late to test now without reverting the upgrade.
It did not fail on xenial/bacula 7.0.5
Journalctl -xe shows
Oct 25 22:22:10 selene bacula-fd[1634]: Bacula interrupted by signal 11: Segmentation violation
Oct 25 22:22:10 selene bacula-fd[1634]: Kaboom! bacula-fd, selene-fd got signal 11 - Segmentation violation at 25-Oct-2018 22:22:09. Attempting traceback.
Oct 25 22:22:10 selene bacula-fd[1634]: Kaboom! exepath=/usr/sbin/
Oct 25 22:22:09 selene bacula-fd[1634]: Bacula interrupted by signal 11: Segmentation violation
Oct 25 22:22:10 selene bacula-fd[1634]: Calling: /usr/sbin/
Oct 25 22:22:11 selene bacula-fd[1634]: It looks like the traceback worked...
Oct 25 22:22:11 selene bacula-fd[1634]: LockDump: /var/lib/
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: lockmgr.c:1179-0 lockmgr disabled
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene bacula-fd[1634]: selene-fd: smartall.
Oct 25 22:22:11 selene systemd[1]: bacula-fd.service: Main process exited, code=exited, status=11/n/a
Oct 25 22:22:11 selene systemd[1]: bacula-fd.service: Failed with result 'exit-code'.
Changed in bacula (Ubuntu): | |
status: | Incomplete → New |
Changed in bacula (Ubuntu): | |
importance: | Undecided → Low |
status: | New → Triaged |
Hi,
I tried to do the same from "bat" but it just happened to work for me. See attached screenshot (I waited a bit, no fail later).
I had bacula just configured by installing it and pressing enter at every question (config for local pgsql DB essentially). I have not changed any other config and I ran on x86 (in a bionic container called "b").
I now wonder if this is either armhf specific or to your bacula config.
Could you:
- try to reproduce on armhf with the least steps to configue (like my install, enter enter ..., start bat, check status) if it fails as well?
- try to reproduce the same on x86?
- clarify - do you use remove clients in any way (so that x86 vlient vs armhf host might be a reason)?