Re: [Bacula-users] Concurrency - did I forget something?

2017-08-07 Thread Bill Arlofski
On 08/07/2017 10:09 PM, Phil Stracchino wrote:
> On 08/08/17 00:03, Bill Arlofski wrote:
>> On 08/05/2017 04:08 PM, Phil Stracchino wrote:
>>> 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'.
> 
> 
> Huh.  I guess I was too hasty in deleting the Client resource for my
> *OLD* NAS box...   :)

That is why we have backups.  (and mailing lists)

:)

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


Re: [Bacula-users] Concurrency - did I forget something?

2017-08-07 Thread Bill Arlofski
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, I have to amend my previous comment.

After showing you what the "status dir" output shows for a job where the FD's
MCJ was the limiting factor, when the job finally failed (after default 10
mins for the SD to wait on the FD), this is what the log showed:

8<
07-Aug 22:02 bacula-dir JobId 15737: Fatal error: Unable to authenticate with
File daemon at "client-fd.example.com:9102". Possible causes:
Passwords or names not the same or

Maximum Concurrent Jobs exceeded on the FD or
FD networking messed up (restart daemon).
For help, please see:
http://www.bacula.org/rel-manual/en/problems/Bacula_Frequently_Asked_Que.html
07-Aug 22:02 bacula-dir JobId 15737: Fatal error: Network error with FD during
Backup: ERR=Interrupted system call
8<


Notice that one of the possible reasons given for this failed job is:

"Maximum Concurrent Jobs exceeded on the FD"

Which in my test case was the actual 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


Re: [Bacula-users] Concurrency - did I forget something?

2017-08-07 Thread Phil Stracchino
On 08/08/17 00:03, Bill Arlofski wrote:
> On 08/05/2017 04:08 PM, Phil Stracchino wrote:
>> 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'.


Huh.  I guess I was too hasty in deleting the Client resource for my
*OLD* NAS box...   :)


-- 
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958

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


Re: [Bacula-users] Concurrency - did I forget something?

2017-08-07 Thread Bill Arlofski
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 x-fd to connect to Storage yy"

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


[Bacula-users] Concurrency - did I forget something?

2017-08-05 Thread Phil Stracchino
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?



-- 
  Phil Stracchino
  Babylon Communications
  ph...@caerllewys.net
  p...@co.ordinate.org
  Landline: +1.603.293.8485
  Mobile:   +1.603.998.6958

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