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
We're invoking a number of check commands via sudo as they require privileges not given to the standard user for Icinga. Depending on the command the target user may be root or another dedicated user. We're using a configuration using this layout:
When the command, check_docker_daemon in this case, runs for more than a minute Icinga is supposed to kill the command. Unfortunately that fails as sudo is setuid and the Icinga user can't send signals.
(4294955659 is 2**32 - 11637 as an unsigned integer with 11637 being the group leader PID)
Now, all of this is obvious. Unfortunately Icinga and Icingaweb do not give any indication of this happening. Instead the check's “last check” keeps growing and no alert is ever sent.
Could you please extend Icinga to produce an UNKNOWN status when killing a check command fails?
The text was updated successfully, but these errors were encountered:
hansmi
changed the title
Errors when killing check command after timeout are invisible
Failure to kill check command after exceeding timeout is not reported
Feb 7, 2017
We're invoking a number of check commands via
sudo
as they require privileges not given to the standard user for Icinga. Depending on the command the target user may beroot
or another dedicated user. We're using a configuration using this layout:When the command,
check_docker_daemon
in this case, runs for more than a minute Icinga is supposed to kill the command. Unfortunately that fails assudo
is setuid and the Icinga user can't send signals.(4294955659 is
2**32 - 11637
as an unsigned integer with 11637 being the group leader PID)Now, all of this is obvious. Unfortunately Icinga and Icingaweb do not give any indication of this happening. Instead the check's “last check” keeps growing and no alert is ever sent.
Could you please extend Icinga to produce an UNKNOWN status when killing a check command fails?
The text was updated successfully, but these errors were encountered: