 |
If I stop Bareos properly, I notice that pid file for bareos-dir does not get removed. If the PID file were removed on process exit, my issue would still exist. |
|
|
I think that on CentOS, at least on CentOS7, the pidfile should move to /run This directory is a temporary filesystem that is recreated at each reboot. I've had a hard reboot of several machines and the following occured: - After the hard reboot and another process is running with the process id that is listed in the pidfile - Bareos-fd is not started as systemd thinks that bareos-fd is already running - When restarting bareos-fd (with the command systemctl restart bareos-fd), systemd actually kills the other process and then starts bareos-fd. On machines running eg haproxy, we've had on multiple servers the case that haproxy was killed during restart of bareos-fd. I think this also applies to other bareos components, like bareos-dir and bareos-sd. |
|
|
Please use current version of bareos. We don't use anymore PID file. |
- Anonymous
