Open pvdputte opened 7 months ago
FYI, I went back to xinetd & unixcat /var/cache/naemon/live
. systemctl reload
works fine again as xinetd is now handling the TCP socket. So I have my 17 second reload back, instead of a 30 second restart. :slightly_smiling_face:
Perhaps someday I could look into systemd socket activation for this.
I've previously commented on this livestatus issue but probably should have opened a new one here instead. Sorry.
Basically, the problem I see is that even in a fresh install without any custom configuration except for the TCP livestatus socket, after a
systemctl reload naemon
, there are two processes listening:One of them is not responding (waiting to be reaped? although
top
is not saying it's a zombie) As a result, Thruk sometimes behaves erratically, says the backend is down etc.This is the config:
This can be easily reproduced in vagrant.
Next, copy these commands into a script and execute it.
This should result in something like
Notice that process 5413 already exists when naemon is first started, but only after the reload, it also starts listening on that socket.
My current workaround is to restart instead of reload after each config change, but this takes a lot longer than reloading (rather large config). Or I should go back to xinetd.