[dev.icinga.com #249] init script should not only depend on lockfile #108
Comments
Updated by mfriedrich on 2010-01-09 23:45:07 +00:00
|
Updated by Meier on 2010-01-10 09:46:43 +00:00 In ido2db init-script i used this
To check against /proc if the process with a given pid is still running. |
Updated by mfriedrich on 2010-01-10 21:46:13 +00:00 jep but in *bsd there is no /proc so ps -o pid -p $pid would be nice instead |
Updated by hbaecker on 2010-01-20 20:47:34 +00:00
Following Note was added by Hiren on icinga-devel list: Could someone give it a try?
|
Updated by mfriedrich on 2010-01-31 19:24:55 +00:00
it behaves rather strange:
lock file is not there, but for some reason icinga is detected running (only ido2db and postgres match on ps aux | grep icinga). any ideas? |
Updated by Meier on 2010-02-05 12:25:53 +00:00 dnsmichi wrote:
As I mentioned long time ago, we really might want different initscripts for different platforms:
I'm not a bsd user but iirc they do not use SysV init so at least there we should go for a seperate implementation matching their startup framework. |
Updated by Meier on 2010-02-05 12:53:02 +00:00 I added a redhat/fedora specific init script. Currently is uses --user in the startup so only works if all necessary files belong to nagios, that avoids the "reload problem". |
Updated by mfriedrich on 2010-02-12 02:17:05 +00:00
needs more investigations, postponed. |
Updated by mfriedrich on 2010-04-21 10:58:27 +00:00 during the show-errors feature from wolfang and now in git, i also changed the behavior when icinga daemon cannot be stopped in a timely manner. before, the 10 times retry loop failed, and an error msg was the output. afterwards, the pid/lock was removed automatically. but icinga daemon was running - so everyone needed to killall imho that's a better solution regarding usability. on large environments it will happen, that stopping icinga will no be possible and doing it manually everytime is not a prefered solution. |
Updated by mfriedrich on 2010-05-16 16:50:22 +00:00
|
Updated by Meier on 2010-05-19 09:21:53 +00:00 for redhatish systems this is fixed in daemon-init-redhat.in |
Updated by Meier on 2010-05-21 10:25:07 +00:00
Applied in changeset commit:"4e99d936674173cfc5673c2c9121f8a5d1386b36". |
This issue has been migrated from Redmine: https://dev.icinga.com/issues/249
Created by mfriedrich on 2010-01-09 23:39:41 +00:00
Assignee: (none)
Status: Resolved (closed on 2010-05-21 10:25:07 +00:00)
Target Version: (none)
Last Update: 2010-05-21 10:25:06 +00:00 (in Redmine)
there are several states and action which lead into wrong information or don't do what they should in special cases.
state: icinga running
=> correct
state: icinga not running, icinga.lock file there
#icinga status
=> show faulty icinga running => should check against ps
state: icinga stopped, lock file already there
=> icinga already running => that is wrong!
state: icinga running
=> icinga stops not in timely manner, leaves icinga.lock there, starting again fails
=> wrong output, better would be icinga did not stop in a timely manner for restarting, please try icinga stop\nicinga start\n
state: icinga running, lockfile removed
=> Stopping icinga: No lock file found in /opt/icinga/var/icinga.lock
=> should check against ps -C icinga and issue a killall -9
Attachments
Changesets
2010-05-19 09:19:17 +00:00 by Meier 4e99d93
2010-05-19 09:46:36 +00:00 by Meier e290d8d
Relations:
The text was updated successfully, but these errors were encountered: