On Saturday 03 February 2007 19:35, Leander Koornneef wrote:
> On 3-feb-2007, at 18:20, Kern Sibbald wrote:
> > On Saturday 03 February 2007 17:29, Leander Koornneef wrote:
> >> Hi,
> >>
> >> we're running Bacula 1.38.11 on Debian 3.1 (Sarge) on i686 with
> >> MySQL.
> >> It has been running stable for some time now. Last night, we
> >> encountered
> >> two bacula-dir segfaults, apparently during volume pruning:
> >
> > It is dying in /lib/tls/libc in fputs with a perfectly valid
> > argument.  Are
> > you by any chance running with a 2.4 kernel?  If so, you should not be
> > using /lib/tls ...
>
> No, it's 2.6:
>
> adm01:~# uname -a
> Linux adm01 2.6.15.1 #4 SMP Wed Jan 25 10:57:49 CET 2006 i686 GNU/Linux
>
> libc's version is 2.3.2.ds1-22sarge4

I don't know what it causing the seg fault, but from the traceback it does not 
appear to be a problem with Bacula, but rather something with libc.

>
> >> <snip>
> >> 03-Feb 00:15 adm01-dir: Pruning oldest volume "full-volume-1"
> >> 03-Feb 00:15 adm01-dir: Pruning oldest volume "full-volume-1"
> >> 03-Feb 00:15 adm01-dir: Pruning oldest volume "full-volume-1"
> >> 03-Feb 00:15 adm01-dir: Fatal Error because: Bacula interrupted by
> >> signal 11: Segmentation violation
> >> <snip>
> >>
> >> <snip>
> >> 03-Feb 01:45 adm01-dir: Pruning oldest volume "full-volume-1"
> >> 03-Feb 01:45 adm01-dir: Pruning oldest volume "full-volume-1"
> >> 03-Feb 01:45 adm01-dir: Pruning oldest volume "full-volume-1"
> >> 03-Feb 01:45 adm01-dir: Fatal Error because: Bacula interrupted by
> >> signal 11: Segmentation violation
> >> <snip>
> >>
> >> We received backtraces on both occasions; they are practically
> >> identical
> >> (see attachments).
> >>
> >> Now I'm no programmer, but this part looks suspicious to me:
> >>
> >> #10 0x0807e908 in status_cmd (ua=0x81114b8,
> >>      cmd=0x31 <Address 0x31 out of bounds>) at ua_status.c:138
> >> #11 0x080682ac in do_a_command (ua=0x81114b8,
> >>      cmd=0x31 <Address 0x31 out of bounds>) at ua_cmds.c:162
> >>
> >> Furthermore, we restarted bacula-dir after the second crash and
> >> started the
> >> remaining jobs manually and they ran without problems. The bacula-
> >> dir is
> >> still running now, several hours later.
> >>
> >> Has anybody seen this before and/or have any advice on what to do
> >> next?
> >> I'd be happy to provide more info, if needed.
> >>
> >>
> >> Leander
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier. Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Bacula-users mailing list
> Bacula-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bacula-users

-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users

Reply via email to