>>>>> On Fri, 31 May 2019 11:38:55 -0600, Lloyd Brown said:
>
> On 5/31/19 10:46 AM, Martin Simmons wrote:
> >
> > The "waiting on max Storage jobs" is caused by the Maximum Concurrent Jobs
> > in
> > the Storage section of bacula-dir.conf.
> >
> > It would be useful to see the output of "show storage" while jobs are
> > waiting.
> >
> > __Martin
>
>
> Martin,
>
> I'm not entirely certain that this is a good test case, but I tried to
> re-create the symptoms, and captured the output of both "status dir" and
> "status storage", along with some config extracts, all of which are
> attached here. I was only able to get one job ("fslhome_c9") to be in
> the "waiting on max Storage jobs" state, and it resolved a few minutes
> later. Thus why I'm not sure it is the best test case. But it did have
> that same error, and there were only 9-10 jobs running on that FD and SD
> at the time, AFAICT.
You have probably reached the Maximum Concurrent Jobs in the Director resource
of bacula-dir.conf (hence the jobs marked as "waiting execution" in status
director). This defaults to 20 (the 16 "running" and 4 "waiting for Client
... to connect to Storage...").
__Martin
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
