[Pkg-bareos-devel] Bug#856459: bareos-director: Director segfaults on backup start

[Nikita Kipriyanov]

Package: bareos-director
Version: 14.2.1+20141017gitc6c5b56-3+deb8u2
Severity: important

Dear Maintainer,

I am using the BareOS version included with current stable Jessie. The policy is to use stable packages in production systems, when these packages exist and have all needed functionality, which is the case for this BareOS installition.

It failed at night with obscure conditions, when it should start a backup. The part of the Bacula log file regarding this fault (obtained with systemctl):

Feb 28 09:17:36 backup-test bareos-dir[17566]: Checking Configuration and Database connection ...
Feb 28 09:17:36 backup-test su[17569]: Successful su for bareos by root
Feb 28 09:17:36 backup-test su[17569]: + ??? root:bareos
Feb 28 09:17:36 backup-test su[17569]: pam_unix(su:session): session opened for user bareos by (uid=0)
Feb 28 09:17:36 backup-test su[17569]: pam_unix(su:session): session closed for user bareos
Feb 28 09:17:37 backup-test systemd[1]: Started LSB: Bareos Director.
Feb 28 23:11:01 backup-test bareos-dir[17576]: backup-dir: ABORTING due to ERROR in smartall.c:209
                                                  Overrun buffer: len=654 addr=7f865800cee8 allocated: lib/mem_pool.h:90 called from mem_pool.c:655
Feb 28 23:11:06 backup-test bareos-dir[17576]: BAREOS interrupted by signal 11: Segmentation violation

The way to reproduce: unknown. This is scheduled time, nodoby did anything by hand.

I've googled this and found some very old (2004) messages in Bacula mailing list, with similar problem in another source line, something about old-style FileSets and Exludes. This particular setup is brand new, there are no old-style FileSets, and all configured FileSets don't have any Excludes at all. The solution suggested there is not applicable to my case.

This package is essential for data availability, as it is doing backups, and failing backups are a disaster. I don't know ways to debug and gather further information on this, but if somebody will suggest anyhting appropriate I will try.

-- System Information:
Debian Release: 8.7
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 3.16.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=ru_RU.UTF-8, LC_CTYPE=ru_RU.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages bareos-director depends on:
ii  adduser                 3.113+nmu3
ii  bareos-common           14.2.1+20141017gitc6c5b56-3+deb8u2
ii  bareos-database-common  14.2.1+20141017gitc6c5b56-3+deb8u2
ii  bareos-database-tools   14.2.1+20141017gitc6c5b56-3+deb8u2
ii  bsd-mailx [mailx]       8.1.2-0.20141216cvs-2
ii  debconf [debconf-2.0]   1.5.56
ii  libacl1                 2.2.52-2
ii  libc6                   2.19-18+deb8u7
ii  libcap2                 1:2.24-8
ii  libgcc1                 1:4.9.2-10
ii  libgnutls-deb0-28       3.3.8-6+deb8u4
ii  liblzo2-2               2.08-1.2
ii  libstdc++6              4.9.2-10
ii  libwrap0                7.6.q-25
ii  lsb-base                4.1+Debian13+nmu1
ii  zlib1g                  1:1.2.8.dfsg-2+b1

Versions of packages bareos-director recommends:
ii  logrotate  3.8.7-1+b1

bareos-director suggests no packages.

-- no debconf information