On Thu, Jul 25, 2013 at 9:56 AM, Barak Griffis
<senor_vaquero AT glitch-cowboy DOT com> wrote:
> I restarted all 3 daemons many times, but no I didn't 'update pool from
> resource'
> What I did do was move all of my configs aside, and install the default
> configs and configure a bare-bones setup that would do auto-labelling
> correctly and then merged my customizations into the default, working
> config while testing along the way.  I think what may have been the
> culprit was defining a Storage resource within the pool definition.
> When I moved the Storage definition to the job level and leave it out of
> the pool, auto-labelling seems to work.
>
> Does that sound reasonable or was it a side-effect?

Changes in the config files like this will not get applied unless you
use the update commands (restarting does not help since the configs
need to be applied to the db).

John

------------------------------------------------------------------------------
See everything from the browser to the database with AppDynamics
Get end-to-end visibility with application monitoring from AppDynamics
Isolate bottlenecks and diagnose root cause in seconds.
Start your free trial of AppDynamics Pro today!
http://pubads.g.doubleclick.net/gampad/clk?id=48808831&iu=/4140/ostg.clktrk
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users