[dev.icinga.com #7046] service icinga2 stop - sometimes doesn't terminate icinga2 completely #1943
Comments
|
Updated by mfriedrich on 2014-09-01 13:41:43 +00:00 Is this reproducible with 2.1.0? |
|
Updated by mhoyer on 2014-09-01 13:49:18 +00:00 Not yet, I'm not sure how to reproduce this in a reproducible way ;-). Will test this for 2.1.0 next days. |
|
Updated by gbeutner on 2014-09-05 13:05:18 +00:00
|
|
Updated by gbeutner on 2014-09-08 13:47:00 +00:00
I don't see how that could possibly happen. Right now we're sending a SIGINT signal and wait up to at least 30 seconds to see if the process terminates on its own. If it doesn't we're sending a SIGKILL signal which should definitely terminate the Icinga 2 process. |
|
Updated by gbeutner on 2014-09-12 13:11:04 +00:00
|
|
Updated by mfriedrich on 2014-10-11 17:40:51 +00:00 Any feedback? |
|
Updated by mfriedrich on 2014-11-24 14:04:08 +00:00
|
This issue has been migrated from Redmine: https://dev.icinga.com/issues/7046
Created by mhoyer on 2014-09-01 13:39:31 +00:00
Assignee: (none)
Status: Rejected (closed on 2014-11-24 14:04:08 +00:00)
Target Version: (none)
Last Update: 2014-11-24 14:04:08 +00:00 (in Redmine)
I have no good idea about this but in fact there are sometimes processes left over after executing "service icinga2 stop". No errors is being reported and the pid file is also deleted afterwards. The process doesn't terminate even after some minutes of waiting.
~ $ sudo service icinga2 stop
Stopping Icinga 2: .Done
~ $ ps aux | grep icinga
icinga 30125 0.0 0.2 577772 4896 ? Ssl 11:38 0:00 /usr/sbin/icinga2 --no-stack-rlimit -c /etc/icinga2/icinga2.conf -d -e /var/log/icinga2/error.log -u icinga -g icinga
The text was updated successfully, but these errors were encountered: