On 03/06/12 09:40, Phil Stracchino wrote:
> 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, I could be wrong, but I think I remember that the maximum concurrent
jobs option might have something to do with this and that perhaps the bconsole
connections count as a "job".

This "theory" seems to correlate nicely with the fact that when no jobs are
running you are able to connect once a gain?

-- 
Bill Arlofski
Reverse Polarity, LLC
http://www.revpol.com/


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