On 08/05/2017 04:08 PM, Phil Stracchino wrote:
> A new client recently first added with 9.0.2 seems to have its maximum
> job concurrency set to 1 despite explicitly setting it to 20:
>
> FileDaemon {
> Name = asgard-fd
> FDport = 9102
> WorkingDirectory = /opt/bacula/var
> Pid Directory = /var/run
> Maximum Concurrent Jobs = 20
> Plugin Directory = /opt/bacula/lib
> }
>
> Did I forget somewhere I need to set that? The Client resource in
> bacula-dir.conf doesn't need a Maximum Concurrent Jobs directive ...
> does it?
Hi Phil,
Yes, as a matter of fact, there is a MaximumConcurrentJobs (MCJ) setting for
the Client resource in the Director's configuration. The default is '1'.
Whenever there is a possible question about MCJ, you can just do a "status
dir" in bconsole when jobs that you expect to be running are instead "Waiting
for.... ${something}"
In your case, I would suspect that the message for this (waiting) job would be
something like:
"...is waiting for maximum Client jobs"
Telling us that the Director's Client resource for this client needs to be
increased.
I just did a quick test to see the message when the FD's MCJ was the limiting
factor, and in this case, the message would be like:
"...is waiting for Client xxxxx-fd to connect to Storage yyyyyy"
Of course this one can be misleading in the case where there is a network
problem or some other thing preventing the FD from contacting the SD. If the
job finally fails due to this, the joblog will (might?) have some better clues
as to the real cause.
Best regards,
Bill
--
Bill Arlofski
http://www.revpol.com/bacula
-- Not responsible for anything below this line --
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
