On Thu, Feb 21, 2019 at 11:32 AM Yılmaz Bilgili via Bacula-users < bacula-users@lists.sourceforge.net> wrote:
> > > If I stop the system service and start it manually from command line > with "bacula-sd -d 200 -c /opt/bacula/etc/bacula-sd.conf" command then I > can get status of storage daemon and the backups are working as > expected. > I had the same symptom on a Fedora system. It turned out that the storage daemon was being started before the network interface was fully up. This is common with systemd-based systems when something is either compiled from source, or installed from a package that was not built by someone with a systemd-based system. For me, I fixed it by writing my own service override file. I put this in /etc/systemd/system/bacula-sd.service.d/override.conf : [Unit] After=network.target nss-lookup.target NetworkManger-wait-online.service autofs.service I put autofs.service in there because I am using autofs to mount USB-attached disks that contain my Bacula volumes; you may not need that. NetworkManager-wait-online.service is the critical piece (and of course you may need to use systemctl to enable the NetworkManager-wait-online service). There is also an easier but kludgy fix that usually works, which is to put a sleep into the startup script to get it to wait a while for the network to come up before starting bacula-sd. Not guaranteed to work every time, but in practice this may be good enough. It does introduce a few seconds delay in getting the system fully booted, but perhaps that's not a big deal for you. --Greg
_______________________________________________ Bacula-users mailing list Bacula-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bacula-users
