Nagios not writing to nagios.log

[Marc Powell]

> -----Original Message-----
> From: nagios-users-admin at lists.sourceforge.net [mailto:nagios-users-
> admin at lists.sourceforge.net] On Behalf Of Fred Janssen
> Sent: Sunday, March 26, 2006 11:14 AM
> To: nagios-users at lists.sourceforge.net
> Subject: [Nagios-users] Nagios not writing to nagios.log
> 
> A few days ago we started testing Nagios as a monitoring tool.
> 
> At this moment we are recording a number of PureTest scripts to enable
us
> to
> monitor advanced use cases when checking our web applications.
> 
> The Nagios/PureTest integration works rather well. We have only one
(in
> our
> perception) strange problem:
> 
> When running the scripts as user NAGIOS we get all the necessary
entries
> in
> the
> nagios.log file.
> 
> When running the scripts from NAGIOS no entries are written to this
file
> (but
> the status in the console is correct). Other http_checks do generate
> log-entries
> and the permissions seem OK.
> 
> Your advice & comments are very much appreciated.

Are the http checks done in exactly the same way as the PureTest scripts
(i.e. active/passive, same plugin, etc)? Check the log_* entries in
nagios.cfg to make sure they meet your expectations. Each check is
normally not logged, only state changes and retries if you have that
enabled.

Also verify that you don't have multiple nagios daemons running
concurrently.

--
Marc




-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0944&bid$1720&dat1642
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null