[dev.icinga.com #197] service icinga stop, doesn't work on ubuntu #90
Comments
Updated by mfriedrich on 2009-11-24 15:30:18 +00:00
|
Updated by VK7HSE on 2009-12-15 20:23:44 +00:00 Hmm... there has been many git commits since this was reported, I'm not having this issue (I'm using Ubuntu 9.10 on both server & desktop installs) Lara are you still having trouble with this? Scott... |
Updated by croft on 2009-12-15 20:51:19 +00:00 VK7HSE wrote:
mhhh, I have trouble with this every day ....but I'm just reinstalling the whole icinga-core, -web and api...please wait for update... |
Updated by hbaecker on 2010-01-09 17:24:45 +00:00 How is the status of this ticket? |
Updated by mfriedrich on 2010-01-09 17:58:15 +00:00 I get that when issuing a restart several times. I think that might be of reloading the idomod file after make install-idoutils - as written in the icinga.cfg not to restart, just stop and start then. Maybe a hint for the docs with idoutils. But regarding the other side, I'll have to test that ... one of my machines is a fresh installed kubuntu 9.10 x64 |
Updated by VK7HSE on 2010-01-09 20:31:52 +00:00 dnsmichi wrote:
Hmm... must be the way I do things that is a little different, I tend to stop/start over restart! this is most likely the reason I've not had any issue with this... |
Updated by croft on 2010-03-03 21:17:57 +00:00 root@croft:/usr/local/icinga/var# service icinga stop only the /usr/local/icinga/var/icinga.lock was removed After update to icinga-1.0.1 |
Updated by VK7HSE on 2010-03-03 21:27:41 +00:00 Hmm... well I still don't get this issue, but I wonder if it has something to do with the amount of items being monitored? as my install is only very small I'd say that's why I'm not having any trouble. I'm assuming that the restart routine is set to a 10 second wait period and if it fails to restart then its claims the service is dead? just a thought... ;-) |
Updated by croft on 2010-03-03 21:46:58 +00:00 200 Host and 1600 Services on my test server. |
Updated by mfriedrich on 2010-03-25 16:54:01 +00:00 jep it does - when shutting down, sighandler events are being generated and also forwarded to forked childs processing checks and events. depending how fast everything clears up, the daemon will exit in that timely manner or not. the init script does wait 10 loops à ~1 sec - maybe extend that a bit. |
Updated by mfriedrich on 2010-04-21 11:05:34 +00:00 now the pid file does not get removed, and an extended warning is given, if the init script fails to stop icinga. so you'll have the possibility to try again using the init script - not the best solution so far, but i think that will help a lot. we might extend the retries from 10 to 20, but i dunno if this is an expected behaviour. |
Updated by mfriedrich on 2010-05-16 16:41:55 +00:00
|
Updated by mfriedrich on 2010-05-19 12:17:34 +00:00
the daemon will exit in a timely manner or not - then you should retry. so for now, i think this bug is resolved. |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/197
Created by croft on 2009-11-23 22:28:40 +00:00
Assignee: mfriedrich
Status: Resolved (closed on 2010-05-19 12:17:34 +00:00)
Target Version: 1.0.2
Last Update: 2010-05-19 12:17:34 +00:00 (in Redmine)
root@croft:/usr/local/icinga/var# service icinga stop
Stopping icinga: ..........
Warning - icinga did not exit in a timely manner
After stopping icinga with #service icinga stop, I have nevertheless two icinga processes running...
Relations:
The text was updated successfully, but these errors were encountered: