‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Friday, May 28, 2021 2:09 AM, Diogo Neves <diogo.g.n...@gmail.com> wrote:
> I Have raised and commented the maximum concurrent jobs in the copy job
> resource and I still couldn't connect to bconsole.
Hello Diogo,
You need to make sure the MaximumConcurrentJobs is also set in the "Director{}"
section of the bacuila-dir.conf file.
Additionally, each of the other daemons (FD and SD) have this setting. If not
specified, then it is "1", and I am pretty sure most recent versions of Bacula
community ship configurations with this set to "20" for each of the daemons.
So, keep in mind that if you have an SD where 20 copy jobs were triggered, and
the MaximumConcurrentJobs is set to 20, then you will not even be able to get a
"status storage" output from this SD because the connection from the Director
to make this request counts a s a job, and there are 20 slots already used.
There are quite a few places where MaximumConcurrentJobs can be set (Client,
SD, DIR, Job, Storage/Autochanger in the Director, each Device in an SD) and
keep in mind that if it is not set, the default is always 1.
A "status director" can help you to determine where the bottleneck is when jobs
are sitting when you think they should be running. For example, you might see:
- waiting on maximum Job Jobs
- waiting on maximum Client Jobs
- waiting on maximum Storage Jobs
...and so on to give you a hint as to what is holding up a job.
Hope this helps,
Bill_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
