On dimanche, 17 décembre 2017 18.19:37 h CET Douglas K. Rand wrote: > I have a virtual full job that runs fine by the schedule but I can't run > by hand. Whey I try to kick of the job via bconsole, it simply doesn't run: > > *run job=agena-offsite > Using Catalog "catalog" > Job not run. > > I get an un-helpful error in the log: > > JobId 0: Fatal error: No Next Pool specification found in Pool > "consolidated". > > After digging around a bit, the error was correct. My always incremental > jobs normally use the pool "always-incr" and that pool as a next pool > setting of "consolidated". And this was probably not right. In fact, > this command works fine: > > *run job=agena-offsite pool=always-incr > > So, I changed the Job Def for my offsites to use the right pool setting > of "always-incr" instead of "consolidated". > > But my question, and kind of a bug report, is why did those jobs work > just fine before (when the pool was set to "consolidated") when they are > kicked off by the schedule? We've been using that previous, and wrong, > configuration for several months. > > Why did it work via the schedule and not via bconsole?
Give a check to your schedule, you perhaps have an overriding pool= in the run line ;-) -- Bruno Friedmann Ioda-Net Sàrl www.ioda-net.ch Bareos Partner, openSUSE Member, fsfe fellowship GPG KEY : D5C9B751C4653227 irc: tigerfoot openSUSE Tumbleweed Linux 4.14.6-1-default x86_64 GNU/Linux, nvidia: 384.98 Qt: 5.9.3, KDE Frameworks: 5.40.0, Plasma: 5.11.4, kmail2 5.6.3 -- You received this message because you are subscribed to the Google Groups "bareos-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. For more options, visit https://groups.google.com/d/optout.
