Oh, thank you. I'll do that tomorrow and see what can be used here.
On Tue, Dec 8, 2009 at 7:09 PM, Marc Powell <[email protected]> wrote: > > On Dec 8, 2009, at 11:19 AM, Cedric Jeanneret wrote: > >> Hello Marc, >> >> Indeed, the "are fresh" comes from nagios.log. ok, done. >> >> NSCA is running in daemon mode, iptables is opened for nsca port, and >> connections can go through it (tcpdump shows it to me, in both directions). >> >> Setting "debug=1" in nsca.cfg seems to do nothing more in /var/log/messages >> (redhat server). I just see "down" hosts passing through (results for ... >> are stalled - forcing immedia check...). > > There will be lots of output. I'm pretty sure that NSCA logs to syslog's > 'daemon' facility using the 'debug','err', and 'info' priorities. Find out > what file those are being logged to in /etc/syslog.conf. You're not going to > get much traction on this issue until you can see that NSCA output. You could > also try grepping your log files for 'Listening for connections' to find > where it's going (if it it's currently being logged by syslog). > > -- > Marc > > > > ------------------------------------------------------------------------------ > Return on Information: > Google Enterprise Search pays you back > Get the facts. > http://p.sf.net/sfu/google-dev2dev > _______________________________________________ > Nagios-users mailing list > [email protected] > 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 > ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Nagios-users mailing list [email protected] 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
