On 03/06/2012 06:34 AM, Martin Simmons wrote:
>>>>>> On Mon, 05 Mar 2012 21:53:37 -0500, Phil Stracchino said:
>> After starting the Director, all connections will succeed initially.
>> All passwords are known good.  As a general rule, once one connection
>> attempt fails, all subsequent connection attempts will also fail.
>> Connections are more likely to fail if one or more jobs is running at
>> the time.
>>
>> Has anyone else encountered this or similar behavior?
> 
> Not on FreeBSD.
> 
> 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 one datum i forgot to add (having forgotten it myself, since I
seldom have to interact with the Director manually) is that after all
running jobs complete, it FREQUENTLY (but not always, I think) becomes
possible to connect again.  (It did last night, for example.)  So there
appears to be some kind of factor of load involved.  It could even be
related to network utilization.


-- 
  Phil Stracchino, CDK#2     DoD#299792458     ICBM: 43.5607, -71.355
  alaric AT caerllewys DOT net   alaric AT metrocast DOT net   phil AT 
co.ordinate DOT org
  Renaissance Man, Unix ronin, Perl hacker, SQL wrangler, Free Stater
                 It's not the years, it's the mileage.

------------------------------------------------------------------------------
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