>>>>> On Tue, 14 Feb 2012 10:34:31 -0500, John Drescher said:
> 
> > I've been running the SD using the following command (I know the combination
> > of options I have used may be excessive, but I wanted as much chance of
> > catching the error as I could!) since yesterday afternoon:
> >    sudo bacula-sd -c /etc/bacula/bacula-sd.conf -d 100 -dt -f -u bacula -g
> > tape -m -v | tee -a /mnt/array/bacula-sd.screen.log
> >
> > However, (as luck would have it) I've not seen the behaviour I originally
> > reported whilst running with debug options.
> >
> > Is there any way in which running the SD with the combination of options I
> > have used above, could cause any different behaviour of the SD? Or interfere
> > in any way with it? I'm asking, becuase I have re-enabled all of the backups
> > jobs I have on the server, and I have still not seen it crash again.
> >
> 
> Could be a timing issue that the delay in writing the log causes the
> bad behavior to not happen.. Those types of problems are hard to
> debug.

Running it under gdb without the debug options is better approach in that
case.

http://www.bacula.org/5.2.x-manuals/en/problems/problems/What_Do_When_Bacula.html#SECTION00640000000000000000

When it 'crashes' (though it sounds more like 'hangs' is a better word),
interrupt gdb with Ctrl-c to get back to the gdb shell window (as in step 8).

__Martin

------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users