If the crash is because of changing schedules and reloading, or reloading and
scheduled jobs start, then it crashes, there is no need to debug it. I
understand what the problem is for bug #375, but it is a non-trivial fix that
is going to have to wait a bit ...
On Wednesday 09 November 2005 16:24, Stephan Ebelt wrote:
> Stephan Ebelt wrote:
>
> [...]
>
> > The job didn't run because bacula seems to have crashed. I've got no
> > glue why yet. All I found till now is
> >
> > - no director process was running this morning
> > - none of the scheduled jobs did run as I've got not a single e-mail
> > - the message below appears in the .conmsg file as well as in the last
> > written .mail file in /var/bacula. (both files are timestamped in the
> > same second)
> >
> > 08-Nov 19:00 dd-lx-backup.dd.net-linx: Fatal Error because: Bacula
> > interrupted by signal 11: Segmentation violation
>
> all right, after browsing the devel list and bug system I would suspect
> this is the same as reported as bug #0000375 'Resched failure after
> configuration change and reload'.
>
> I've done plenty of reloads yesterday while testing the FileSet.
>
> > Unfortunately I do not have any trace. Or I can't find it. It is an rpm
> > installation were debugging is probably disabled?
>
> gdb was not installed. It is now and I should be able to produce another
> trace if needed.
>
> best regards,
> Stephan
--
Best regards,
Kern
(">
/\
V_V
-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php
_______________________________________________
Bacula-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bacula-users
