>>>>> On Tue, 4 Feb 2014 10:25:39 -0500, Mingus Dew said: > > Dear All, > I'm running bacula-5.2.13 on Solaris 10 x86. Recently the bacula-dir > has begun segfaulting and crashing on my server, but I have no idea why. > I realize this is a pretty general question and I'll respond with as > much additional information as I can, but need a starting point. > > Please someone suggest how I might debug this. The time of crash > doesn't seem to be predictable, but I do notice that before the crash, the > director becomes unresponsive to bconsole connection requests, suggesting > that Max Concurrent Jobs has been reached. Increasing that number would be > an obvious solution, but I'm not sure what the correct upper limit for that > would be as I've already had issues in the past on Solaris with a "too many > open files" issue that would crash the Storage Daemon
I suggest attaching a debugger (e.g. gdb or dbx) to the process before it crashes and leave that session open in a terminal somewhere. It will break back to the debugger when it crashes allowing you to get a backtrace (using the "where" command in gdb or dbx). __Martin ------------------------------------------------------------------------------ Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
