Menu
▾
▴
[Bacula-bugs] [bacula 0001861]: local fd crashes with 'Segmentation violation'
|
From: Mantis B. T. <no...@bu...> - 2012-04-24 18:07:04
|
A NOTE has been added to this issue. ====================================================================== http://bugs.bacula.org/view.php?id=1861 ====================================================================== Reported By: macx Assigned To: kern ====================================================================== Project: bacula Issue ID: 1861 Category: fd-plugin Reproducibility: random Severity: crash Priority: low Status: assigned ====================================================================== Date Submitted: 2012-04-19 13:39 BST Last Modified: 2012-04-24 19:06 BST ====================================================================== Summary: local fd crashes with 'Segmentation violation' Description: The bacula-fd process ends with a 'Segmentation violation' about once/wk. I haven't been able to establish a pattern yet. Apr 18 13:07:31 localhost bacula-fd: Bacula interrupted by signal 11: Segmentation violation is the complete message from the most recent instance. Otherwise bacula works just fine. Steps to Reproduce: Leave bacula running for a week. Additional Information: Please let me know what information you need. ====================================================================== ---------------------------------------------------------------------- (0006299) macx (reporter) - 2012-04-19 13:58 http://bugs.bacula.org/view.php?id=1861#c6299 ---------------------------------------------------------------------- The last time it happened was: Apr 5 15:00:04 localhost bacula-fd: Bacula interrupted by signal 11: Segmentation violation ---------------------------------------------------------------------- (0006300) kern (administrator) - 2012-04-19 15:18 http://bugs.bacula.org/view.php?id=1861#c6300 ---------------------------------------------------------------------- Please get us a traceback. If the FD were installed correctly, it would be emailed to you, and it will be in your FD's working directory. It will have an extension .traceback and a second file will have extension .bactrace. The first is the most important, the second can often be useful too. The manual documents how to setup the traceback file capture. If you are unable to get that working, then please read the Kaboom chapter of the manual and obtain a traceback manually. ---------------------------------------------------------------------- (0006301) macx (reporter) - 2012-04-19 16:12 http://bugs.bacula.org/view.php?id=1861#c6301 ---------------------------------------------------------------------- I've installed gdb - sorry, it wasn't installed before. I'll have to wait until it crashes again (I'm assuming that I can't get debug info. after the fact). ---------------------------------------------------------------------- (0006302) kern (administrator) - 2012-04-19 19:28 http://bugs.bacula.org/view.php?id=1861#c6302 ---------------------------------------------------------------------- No, you cannot get the traceback after the fact. However, when your FD is idle sometime, I would recommend testing that you get a proper dump by forcing it to crash, otherwise you may wait a week only to find it still doesn't dump. To force it to crash, you must find its PID with something like: ps -fax | grep bacula-fd the do: kill -SEGV <pid> where <pid> is the process id found with the ps fax. If it doesn't at least write the .traceback file, there is a problem. ---------------------------------------------------------------------- (0006303) kern (administrator) - 2012-04-19 19:30 http://bugs.bacula.org/view.php?id=1861#c6303 ---------------------------------------------------------------------- Oh, please don't forget to restart the FD if you kill it. ---------------------------------------------------------------------- (0006304) macx (reporter) - 2012-04-24 18:38 http://bugs.bacula.org/view.php?id=1861#c6304 ---------------------------------------------------------------------- OK. More info. I don't seem to be able to get a traceback. I've installed gdb. Is there anything else I need to do? Where should I be looking for a .traceback file. I can't find one anywhere. I've noticed that when the fd crashes, it does so after a certain job every time and then the rest of the jobs fail. I'm not sure, but I think that maybe this only happens the night after I get status info. from the fd in BAT. ---------------------------------------------------------------------- (0006305) macx (reporter) - 2012-04-24 19:06 http://bugs.bacula.org/view.php?id=1861#c6305 ---------------------------------------------------------------------- OK. I got postfix set up now. I'd never bothered before. Now I get this: [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/libthread_db.so.1". [New Thread 0xb7018b40 (LWP 822)] 0xb77a8416 in __kernel_vsyscall () $1 = 1768121699 $2 = 147488840 $3 = 147488880 /etc/bacula/scripts/btraceback.gdb:4: Error in sourced command file: No symbol table is loaded. Use the "file" command. Issue History Date Modified Username Field Change ====================================================================== 2012-04-19 13:39 macx New Issue 2012-04-19 13:58 macx Note Added: 0006299 2012-04-19 15:18 kern Note Added: 0006300 2012-04-19 15:18 kern Assigned To => kern 2012-04-19 15:18 kern Priority high => low 2012-04-19 15:18 kern Status new => feedback 2012-04-19 16:12 macx Note Added: 0006301 2012-04-19 16:12 macx Status feedback => assigned 2012-04-19 19:28 kern Note Added: 0006302 2012-04-19 19:29 kern Status assigned => feedback 2012-04-19 19:30 kern Note Added: 0006303 2012-04-24 18:38 macx Note Added: 0006304 2012-04-24 18:38 macx Status feedback => assigned 2012-04-24 19:06 macx Note Added: 0006305 ====================================================================== |