I recently upgraded to app-backup/bacula-9.4.2. Ever since updating, my Director keeps randomly dying at intervals of typically a few days. I am trying to troubleshoot the problem, but I cannot get a traceback because FEATURE nostrip (per https://wiki.gentoo.org/wiki/Debugging) does not work in this ebuild.
(In reply to Phil Stracchino (Unix Ronin) from comment #0) > I recently upgraded to app-backup/bacula-9.4.2. Ever since updating, my > Director keeps randomly dying at intervals of typically a few days. I am > trying to troubleshoot the problem, but I cannot get a traceback because > FEATURE nostrip (per https://wiki.gentoo.org/wiki/Debugging) does not work > in this ebuild. I can not reproduce the problem here. Building with FEATURS=nostrip produces a binary with embedded symbols. You can verify it by running 'nm bacula-dir'. It should list all symbols for the file. Can you please give some background about what you are trying to do?
(In reply to Thomas Beierlein from comment #1) > I can not reproduce the problem here. Building with FEATURS=nostrip produces > a binary with embedded symbols. > > You can verify it by running 'nm bacula-dir'. It should list all symbols for > the file. > > Can you please give some background about what you are trying to do? Tom, I was trying to diagnose a bug in which the Director keeps silently dying. This APPEARS to be possibly related to running the dbcheck script weekly from the Director as an admin job. It's been working fine for years prior to 9.4.2.
(In reply to Phil Stracchino (Unix Ronin) from comment #2) > (In reply to Thomas Beierlein from comment #1) > > > I can not reproduce the problem here. Building with FEATURS=nostrip produces > > a binary with embedded symbols. > > > > You can verify it by running 'nm bacula-dir'. It should list all symbols for > > the file. > > > > Can you please give some background about what you are trying to do? > > Tom, > I was trying to diagnose a bug in which the Director keeps silently dying. > This APPEARS to be possibly related to running the dbcheck script weekly > from the Director as an admin job. It's been working fine for years prior > to 9.4.2. Ok, so I assume you tried to run bacula-dir under gdb control. Be aware that it forks itself into background as daemon. So you either have to command it to stay in forground before a 'run' command in gdb or to start it out of gdb and attach gdb afterwards to the process.
(In reply to Thomas Beierlein from comment #3) > > Ok, so I assume you tried to run bacula-dir under gdb control. > Be aware that it forks itself into background as daemon. > So you either have to command it to stay in forground before a 'run' command > in gdb or to start it out of gdb and attach gdb afterwards to the process. Debugging steps like this are exactly why I'm trying to build an unstripped installation.
(In reply to Phil Stracchino (Unix Ronin) from comment #4) > (In reply to Thomas Beierlein from comment #3) > > > > Ok, so I assume you tried to run bacula-dir under gdb control. > > Be aware that it forks itself into background as daemon. > > So you either have to command it to stay in forground before a 'run' command > > in gdb or to start it out of gdb and attach gdb afterwards to the process. > > Debugging steps like this are exactly why I'm trying to build an unstripped > installation. So, please what gives the 'nm /usr/sbin/bacula-dir' command mentioned in #c 1 at your side? If there are no symbols shown, please provide your emerge --info output. Maybe we can spot the reason. As I said before, FEATURES=nostrip produces a file with embedded symbol infos here. As an additional test you can have a look at the file size before and after doing a 'strip bacula-dir'.
