You forgot to say what the errors are! Were the daemons all running as root before the upgrade? If so, then you probably need to change the permissions on some files.
__Martin >>>>> On Mon, 18 May 2020 17:25:44 +0100, Chris Wilkinson said: > > I upgraded my server to Debian Buster (10) and took the opportunity to > upgrade Bacula to the repo version (9.4.2). I retained my existing > /etc/bacula/*.conf files. > > I had no luck getting the services to start (exited with error) using the > /etc/init.d scripts but did get them to run manually (sudo > /usr/sbin/bacula-xxx -c bacula-xxx.conf) starting them as root after having > checked that the -t and -f options produced no errors. > > This set me looking into the init scripts that the repo provided. The > ownerships set in the scripts are different to root:root. The installer > installed new scripts in /etc/init.d and /lib/systemd/system as I chose to > allow the installer to install the package maintainers versions over what I > had. > > The ownerships set in the scripts are different to root:root. > > 1) /etc/init.d/bacula-director is configured to run as user:group = > bacula:bacula (BUSER/BGROUP) > 2) /etc/init.d/bacula-fd is configured to run as root:root and > /etc/init.d/bacula-sd as bacula:tape > 3) /lib/systemd/system/bacula-director.service unit file was installed and > also runs as bacula:bacula > 4) /lib/systemd/system/bacula-sd.service unit runs as bacula:tape > 5) /lib/systemd/system/bacula-fd.service unit runs as root:root > > Has anyone used these successfully with these ownerships? > > Best > -Chris- _______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
