bacula-fd 13.0.3 produces high CPU load if ConnectToDirector = yes and director unreachable
Summary
Reproducibility | Platform | OS | OS Version | Product Version |
---|---|---|---|---|
always | AMD64 | Debian | 11 | 13.0.3 |
also on macOS 10.15
Description
if you have the FD connect to the director (ConnectToDirector = yes), and the director is not there, the FD will produce high CPU load
I think this problem was also there in early 13.0.x versions, but not in 13.0.2, but I am not 100% sure
Steps to Reproduce
- configure FD to connect to director and allow in director that the client connects
- stop director
- observe the client cpu load
Additional Information
config files:
# cat /opt/bacula/etc/bacula-fd.conf
Director {
Name = bacula-dir
Password = "...
DirPort = 9101
Address = bacula-dir.bla.com
ConnectToDirector = yes
# Schedule = Daily
# Schedule = Test
ReconnectionTime = 15 minutes
}