On Tue, 27 Apr 2010, ad...@jack-clan.nl wrote:
well, i removed the symlinks in the runlevel directories and added mon -f
to rc.local,
and now it's working.
is there any way i can troubleshoot the functioning of the mon daemon?
what you should do is start by comparing the environment from your
working configuration with the one from the non-working configuration
to see how they differ.
if you're starting the daemon from an interactive shell then you should
do something like
env > /tmp/working
and in your alert script you should do something like
env > /tmp/not-working
then compare them.
you could also run in daemon mode and add
monerrfile = /tmp/monerrfile
to your mon.cf, and then have a look at that after a while. that should
catch stderr and stdout from your alert script. that may give you a clue.
also, if any programs you are calling from your script produce error logs,
check there.
also, does your alert script work when running it as the same user as
mon runs as when you're starting it in daemon mode via the init script?
_______________________________________________
mon mailing list
mon@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/mon
