On 03/07/2012 09:58 AM, Phil Stracchino wrote:
> It appears I can connect as many consoles as I want, up to the
> Director's configured concurrency limit, with no problem ... until I
> start scheduling jobs.
> 
> So, then I opened a bconsole and left it open, then scheduled two jobs
> from BAT successfully.  Then I tried to schedule a third.  No go.
> 
> At this point, I tried to open an additional new bconsole.  No go, and
> the trace *did not log anything* for the connection attempt.  I could
> continue to schedule more manual jobs from the existing open bconsole,
> but could start no new consoles, and BAT became completely unresponsive.
>  It appears that once two or three jobs were scheduled, the Director
> *stopped listening* for new console connections, but continued to
> service existing open consoles.

I forgot to add:  Jobs started by the Director automatically according
to a Schedule do not affect console connections.  Only manually started
jobs, or jobs manually scheduled via a console for a future start time,
result in console connection failures.


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

------------------------------------------------------------------------------
Virtualization & Cloud Management Using Capacity Planning
Cloud computing makes use of virtualization - but cloud computing 
also focuses on allowing computing to be delivered as a service.
http://www.accelacomm.com/jaw/sfnl/114/51521223/
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users