22.02.2019 10:14 tarihinde Sven Hartge yazdı:
Why not try the Debian packages? bacula-9.4.2 is available via
stretch-backports.
Thank you Sven. This way seems more reliable to me.
Best regards.
___
Bacula-users mailing list
Bacula-users@lists.sour
22.02.2019 20:26 tarihinde Greg Woods yazdı:
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
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
Hello Sven,
bacula-* systemd unit scripts sometimes fail to start on machine boot depending
on the time required to mount _netdev disks (confirm it with service bacula-sd
status after boot).
Perhaps, adding this option would make it more resilient:
After=network.target mnt-wibble.mount
I opene
Just in time: I just read you still uses init.d scripts. Refer to:
https://askubuntu.com/questions/90982/how-to-make-a-script-in-init-d-run-later
https://serverfault.com/questions/550382/how-to-detect-if-mount-point-exists-from-init-d-script
Regards,
Sent from TypeApp
On Feb 22, 2019, at 7:44 AM,
On 22.02.19 10:06, Yılmaz Bilgili via Bacula-users wrote:
> 22.02.2019 10:14 tarihinde Sven Hartge yazdı:
>> Why not try the Debian packages? bacula-9.4.2 is available via
>> stretch-backports.
>
> I thought packages in the script are official Debian packages too. I
> never used backports but wil
22.02.2019 10:14 tarihinde Sven Hartge yazdı:
Unfortunately, your systems uses the legacy SysVinit-scripts to start
the SD. That way you don't get a whole lot of debugging output in the
journal.
Did you compile the SD yourself? Maybe you forgot to add
"--with-systemd=/lib/systemd/system" to ena
