It turns out that this problem was caused because the update recreated the following file:
/etc/bareos/bareos-sd.d/storage/bareos-sd.conf I had renamed all my config files to match the design of my configuration. Having two .conf files in this directory causes bareos-sd to not start. 1) Would it be possible to give Bareos some intelligence to no recreate this file on upgrade, or to not do so if another file is in the directory? 2) If not, would it be possible for Bareos to produce a decent error message indicating the problem? If renaming these .conf files causes issues, there should probably be some documentation to that effect somewhere. -- Soren Stoutner 623-262-6169 so...@stoutner.com
