Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Segmentation\s+fault\s+of\s+Storage\s+Daemon\s+when\s+client\s+is\s+not\s+available\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[Bacula\-users\]\s+Segmentation\s+fault\s+of\s+Storage\s+Daemon\s+when\s+client\s+is\s+not\s+available\s*$/: 6 ]

Total 6 documents matching your query.

1. [Bacula-users] Segmentation fault of Storage Daemon when client is not available (score: 1): Author: Thomas Lohman <thomasl AT mtl.mit DOT edu>; Date: Fri, 02 Sep 2011 10:19:40 -0400; Hi, We've been seeing our Bacula Storage Daemon die with a segmentation fault when a client can't be reached for backup. We have two servers and have observed this behavior on both of them. Some sear; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-09/msg00030.html (13,610 bytes)
2. Re: [Bacula-users] Segmentation fault of Storage Daemon when client is not available (score: 1): Author: Martin Simmons <martin AT lispworks DOT com>; Date: Fri, 2 Sep 2011 15:42:28 +0100; That looks similar to some existing bacula bug reports: http://bugs.bacula.org/view.php?id=1568 http://bugs.bacula.org/view.php?id=1343 I suggest you run the storage daemon under gdb and get a backt; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-09/msg00031.html (14,589 bytes)
3. Re: [Bacula-users] Segmentation fault of Storage Daemon when client is not available (score: 1): Author: John Drescher <drescherjm AT gmail DOT com>; Date: Fri, 2 Sep 2011 10:50:23 -0400; I have 5 to 10 clients that are not connected when the backup is scheduled each night with 5.0.3 and I have not experienced this issue 1 time since I installed 5.0.3 last year. John -- Special Offer; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-09/msg00032.html (12,952 bytes)
4. Re: [Bacula-users] Segmentation fault of Storage Daemon when client is not available (score: 1): Author: Josh Fisher <jfisher AT pvct DOT com>; Date: Fri, 02 Sep 2011 11:11:13 -0400; I concur. I have laptops that are fairly regularly not connected when scheduled and have never seen a hard crash of of the 5.0.3 SD on x86_64 Centos 5.4 (or, more recently, Centos 6.0). -- Special Of; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-09/msg00033.html (13,286 bytes)
5. Re: [Bacula-users] Segmentation fault of Storage Daemon when client is not available (score: 1): Author: John Drescher <drescherjm AT gmail DOT com>; Date: Fri, 2 Sep 2011 11:13:54 -0400; No. I do not use any encryption at all. Yes the jobs fail after a few minutes (30 minutes?). Other jobs run concurrently so it really does not slow down the process that much. -- John M. Drescher --; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-09/msg00034.html (13,249 bytes)
6. Re: [Bacula-users] Segmentation fault of Storage Daemon when client is not available (score: 1): Author: Thomas Lohman <thomasl AT mtl.mit DOT edu>; Date: Wed, 21 Sep 2011 11:23:17 -0400; Just to followup on this in case others have this issue. I was able to rebuild bacula with the -g compiler option to get some debugging information. The scenario that causes the SD to crash with a SE; /usr/local/webapp/mharc-adsm.org/html/Bacula-users/2011-09/msg00208.html (15,345 bytes)

Current List: 1 - 6
Page: [1]