<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> <META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2654.45"> <TITLE>RE: [Nagios-users] NSCA Distributed Server</TITLE> </HEAD> <BODY> I found it!! On a whim I deleted the status.sav file and wha-la I began to receive updates to the central server! Thanks for you help again Marc. :) -Jeff -----Original Message----- From: Marc Powell [<A HREF="mailto:marc@ena.com">mailto:marc@ena.com</A>] Sent: Wednesday, December 17, 2003 1:18 PM To: Jeff Engstrom; nagios-users@lists.sourceforge.net Subject: RE: [Nagios-users] NSCA Distributed Server See inline comments marked with <MARC>: ________________________________________ From: Jeff Engstrom [<A HREF="mailto:Jeff.Engstrom@fortix.net">mailto:Jeff.Engstrom@fortix.net</A>] Sent: Wednesday, December 17, 2003 2:44 PM To: 'nagios-users@lists.sourceforge.net' Subject: [Nagios-users] NSCA Distributed Server Greetings, For some reason the script that updates the central server is not executing but all other external commands seem to work fine. I was hoping that someone might be able to help? Here is the configuration (sorry about the length)... <MARC> - Is there any error message in /var/log/messages on either machine? You might try enabling the debug option in nsca.cfg to get more detailed information. You should also try submitting a check result by calling send_nsca manually. That might spit out some errors. I'd also verify that nsca is listening on the IP/Port you expect it to be via netstat -aelp. Central Server (10.1.1.4) NSCA running in daemon mode with the following config... server_port=5667 [snip] <MARC> NSCA config looks fine at first glance. nagios.cfg has the following.. [snip] command_check_interval=30s <MARC> - This isn't valid for a 1.1 or below config AFAIK (it may be for a 2.0 config though). This should be an integer value specifying a multiple of the interval_length. For example, if you have your interval length set at 60 (seconds), then a 1 here would cause nagios to check for external commands every 60 seconds. 2 would mean every 120 seconds. The only odd value you could have here would be -1 which would cause nagios to check for external commands as often as possible. This could very well be your problem. A simple test would be to do an ls -l on rw/nagios.cmd and see if it's anything other than 0 length. If it's not then NSCA is successfully appending new results to the file but nagios may not be reading them. Distributed Server (10.1.1.3) [snip] <MARC> Distributed server information looked fine. It is interesting to note that your had the command_check_interval set to -1 here where I would expect the least number of external commands (if any) to be received. That's more of a work-flow thing anyway I would suspect. -- Marc </BODY> </HTML>