|
Re: [Bacula-users] Bconsole Reload Sometimes Doesn't Load New Job Resource Definitions
2015-10-20 13:47:34
|
Oh, I forgot to mention that when you
start the console, if I am not mistaken (to be verified), it
"locks onto" the most recent bacula-dir.conf file as if it were a
regular job, and consequently, if you want bconsole to show a more
recent bacula-dir.conf I reccommend restarting bconsole. In fact,
keeping old bconsoles connected to the Director can block a given
bacula-dir.conf in memory, and at some point, the Director will
not be able to do a "reload" command. So if you are doing a lot
of reloads, be sure to kill off old bconsole sessions.
Best regards,
Kern
On 10/19/2015 03:29 PM, Rich Otero wrote:
Hello,
We make a backup product that uses Bacula as the backend.
Our systems run Ubuntu v12.04 (kernel v3.12.17) with Bacula
v5.2.12. Our product sets up the job resource definitions
based on the user's choices, it validates the configuration
with `bacula-dir -t`, and then it issues the bconsole `reload`
command to load the new job resource. On a particular customer
system, we find that the new job resource has not been loaded
after the `reload` command has completed. If we give the `run`
command, the new job is not in the list of jobs that can be
executed. If we restart bacula-dir, then the job resource is
loaded and it can be run. We haven't been able to figure out
why `reload` isn't doing what we expect, so I hope that you
can offer some advice. I have attached the Director
configuration file from the affected system (bacula-dir.conf)
and the file where we put the job resource definitions
(jobs.conf), which is imported by the main configuration file.
I've found a few relevant points in researching this
problem online. The bconsole documentation seems to discourage
you from using `reload`:
"While it is possible to reload the Director's
configuration on the fly, even while jobs are executing, this
is a complex operation and not without side effects.
Accordingly, if you have to reload the Director's
configuration while Bacula is running, it is advisable to
restart the Director at the next convenient opportunity."
Indeed, I have found that restarting the Director causes
the new job resource to be loaded, but this is not a good
solution for us because we often have many Bacula jobs
running simultaneously; the "convenient" times when the
Director could be restarted will be too infrequent.
I also found a closed bug ticket from a user who
describes practically the same problem:
Thank you in advance for your help.
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
------------------------------------------------------------------------------
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
|
|
