>>>>> On Tue, 06 Mar 2012 12:00:28 -0500, Phil Stracchino said: > > On 03/06/2012 11:21 AM, Martin Simmons wrote: > >>> Try it with -d 100 on both bconsole and bacula-dir (connect when > >>> bacula-dir is > >>> idle so the connection messages aren't mixed with other job messages)? > >> > >> The problem never occurs when the Director is idle. > > > > The debug output would still be useful. You can see what output it prints > > when connecting to an idle Director to get an idea of what to look for in > > the > > busy output. > > > > If you set the Director's debug level using > > > > setdebug director level=100 trace=1 > > > > then it will be written to a .trace file (rather than being dumped to the > > console). > > Tried that. I'll have to create some test traffic now to see if I can > reproduce the problem deliberately... > > > Where should that log to?
It will be $workingdirectory/$name.trace based on the director configuration. __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@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
