Bacula

btraceback utility doesn't work

Bug #590887 reported by Tomasz on 2010-06-07

This bug affects 1 person

Affects		Status	Importance	Assigned to	Milestone
	Bacula	New	Undecided	Unassigned
	bacula (Ubuntu)	Opinion	Wishlist	Unassigned

Bug Description

Binary package hint: bacula
Version: 5.0.1-1ubuntu1

The package provides btraceback utility, which sends an email with trace by mail. It is installed in /usr/sbin/btraceback. When bacula crashes, it prints to console:

# cmdline and args taken from /etc/init.d/bacula-dir
$ /usr/sbin/bacula-dir -c /etc/bacula/bacula-dir.conf -u bacula -g bacula -d 200 -dt -f -m -v
bacula-dir: dird.c:184-0 Debug level = 200
07-cze-2010 19:20:44 bacula-dir: dird.c:184-0 Debug level = 200
(...)
Bacula interrupted by signal 11: Segmentation violation
Kaboom! bacula-dir, magazyn-dir got signal 11 - Segmentation violation. Attempting traceback.
Kaboom! exepath=/usr/sbin/
Calling: /usr/sbin/btraceback /usr/sbin/bacula-dir 13467 /var/lib/bacula

and should send an email with details. Unfortunately, the email looks like this:

ptrace: Operation not permitted.
/var/lib/bacula/13467: No such file or directory.
$1 = 0
/etc/bacula/scripts/btraceback.gdb:2: Error in sourced command file:
No symbol table is loaded. Use the "file" command.

See original description

Tomasz (nowak2000) on 2010-06-07

description:

updated

Mathias Gug (mathiaz) on 2010-06-10

Changed in bacula (Ubuntu):
importance:	Undecided → Medium

Revision history for this message

Chuck Short (zulcss) wrote on 2011-03-07:

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

Changed in bacula (Ubuntu):
status:	New → Incomplete

Revision history for this message

Kern Sibbald (kern) wrote on 2011-03-07: Re: [Bug 590887] Re: btraceback utility doesn't work

On Monday 07 March 2011 16:12:51 Chuck Short wrote:
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. Please try to obtain a backtrace following the
> instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload
> the backtrace (as an attachment) to the bug report. This will greatly
> help us in tracking down your problem.
>
> ** Changed in: bacula (Ubuntu)
> Status: New => Incomplete

This kind of problem "ptrace: Operation not permitted." is common when you run
some of your daemons as non-root. The core dump is produced as root because
Bacula is started as root, but as user "bacula" gdb won't work.

One solution is for obtaining a traceback, run bacula as root. This is most
appropriate for a one-shot reproducible case. Another solution might be to
put the appropriate command (e.g. sudo) in the btraceback script so that the
debugger is able to do its job.

Regards,

Kern

Revision history for this message

Kern Sibbald (kern) wrote on 2011-03-07:

By the way, I just wanted to mention that these kinds of problems are very
clearly explained in the Kaboom chapter of the manual.

Revision history for this message

Tomasz (nowak2000) wrote on 2011-03-07:

So maybe the btraceback script should run gdb within sudo, provided that the script checks if the user is a member of the bacula group.

Please note that this bug is not about a cause of the signal 11; it is about the btraceback script not working by default.

Chuck Short (zulcss) on 2011-04-20

Changed in bacula (Ubuntu):
importance:	Medium → Wishlist
status:	Incomplete → Opinion

Report a bug

This report contains Public information

Everyone can see this information.

You are

Subscribing...

Edit bug mail

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.