You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Because in this image the PID1 is merely a startup process (it doesn't exec keepalived), it is the one that receives the signals. It ignores those signals completely, causing it to fail. I believe fixing it might require allowing containers to register custom signal handlers here: https://github.com/osixia/docker-light-baseimage/blob/master/image/tool/run#L892-L894
TL;DR:
I'd expect running docker kill -s 12 keepalived to cause it to create /tmp/keepalived.stats.
The text was updated successfully, but these errors were encountered:
[...]
Fri Apr 21 06:51:48 2023: Printing parent data for process(1) on signal
Fri Apr 21 06:51:48 2023: Printing VRRP data for process(7) on signal
[...]
Monitoring exporters, like this one: https://github.com/cafebazaar/keepalived-exporter rely on being able to send signal to docker container in order for keepalived to dump its stats/data files.
Because in this image the PID1 is merely a startup process (it doesn't
exec keepalived
), it is the one that receives the signals. It ignores those signals completely, causing it to fail. I believe fixing it might require allowing containers to register custom signal handlers here: https://github.com/osixia/docker-light-baseimage/blob/master/image/tool/run#L892-L894TL;DR:
I'd expect running
docker kill -s 12 keepalived
to cause it to create/tmp/keepalived.stats
.The text was updated successfully, but these errors were encountered: