Hello Ben,
Thanks, this confirms what I wrote in my previous email.
Best regards,
Kern
On 10/19/2015 11:47 PM, Roberts, Ben wrote:
>
> > On a particular customer system, we find that the new job resource
> has not been loaded after the `reload` command has completed.
>
>
>
> My workflow relies
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,
Hello,
I recommend that you move up to Ubuntu 14.04 (maybe not so easy from a
QA stand point), but more importantly move up to Bacula 7.2.0 (or 7.2.1
which will be out within the next month). Sinc version 5.2.x, we have
done some major rewrites of the reload command including a new directive
so,
; To: "Roberts, Ben"
> Cc: bacula-users@lists.sourceforge.net
> Sent: Tuesday, October 20, 2015 11:24:54 AM
> Subject: Re: [Bacula-users] Bconsole Reload Sometimes Doesn't Load New Job
> Resource Definitions
> Ben, thanks for the input. We used to have that problem too:
Ben, thanks for the input. We used to have that problem too: We had a bug
in our code that would result in a lot of old bconsoles being left open and
we would hit the concurrent jobs limit. We fixed that some time ago, but
your message and someone else's yesterday are directing me to the message.
I
> On a particular customer system, we find that the new job resource has not
> been loaded after the `reload` command has completed.
My workflow relies on the reload command heavily (puppet drops in updated
config files and executes the reload command afterwards; this normally works
very well.
> 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 t
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
`