>>>>> On Wed, 26 Sep 2018 00:06:48 -0400, Gary Dale said: > > On 2018-09-20 06:09 AM, Kern Sibbald wrote: > > Hello, > > > > The output produced by Bacula seems unusually short. Normally Bacula > > displays a reason for the failure. > > > > I recommend trying your label command again, but turn on debug with > > something link > > > > setdebug level=150 Storage > > > > prior to doing the label command. It should give you a more detailed > > reason for > > the failure. > > It gives me the exact same output. It took the setdebug command but > continues to complain when I try to label a new volume. After a reboot I > was able to label a volume however. After a while I lose that ability > once more.
The debug output goes to /dev/null unless the daemon is run in the foreground using the -f option. Try setdebug level=150 trace=1 Storage and look for a file matching *.trace (probably in the SD's WorkingDirectory). __Martin _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
