Nagios CRASHING - Passive External Commands

[Fred Reimers]

Jim,

Good idea.  I would also have to do my own status checking to see if the results are a change in status between ok,warning,critical, which is possible.

I was hoping to use the freshness checking feature of Nagios to ensure that the background processes are working.  

I'm also wondering how this would affect the host status if a host only has passive checks associated with it that are not being updated regularly?

This worked fine for 16 hours and then stopped.  I did rewrite the routine to add some delay between writes to the command file and changed the nagios.cmd option to check the command file as often as possible.  It's worked for a couple of cycles now.

Fred


-----Original Message-----
From: Jim Mozley [mailto:jim.mozley at exponential-e.com]
Sent: Friday, January 23, 2004 11:40 AM
To: Fred Reimers
Cc: nagios-users at lists.sourceforge.net
Subject: Re: [Nagios-users] Nagios CRASHING - Passive External Commands


Fred Reimers wrote:

> I have an external script running FPING against 3200 hosts and writing the results to the Nagios external command file.  
> 
> Sometimes it works and other times Nagios crashes.
> 
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0681-Frame;PING;0;PING OK - 208.252.129.57 is alive (74.4 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0681-Server;PING;0;PING OK - 10.136.26.2 is alive (89.8 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0681-VPN;PING;0;PING OK - 10.136.26.1 is alive (90.2 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0687-Frame;PING;0;PING OK - 65.202.155.77 is alive (67.5 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0687-Server;PING;0;PING OK - 10.138.24.2 is alive (80.9 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0687-VPN;PING;0;PING OK - 10.138.24.1 is alive (83.3 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0689-V90;PING;0;PING OK - 63.110.74.154 is alive (228 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0689-Server;PING;0;PING OK - 10.133.46.2 is alive (258 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;0689-VPN;PING;0;PING OK - 10.133.46.1 is alive (266 ms)
> [1074873519] EXTERNAL COMMAND: PROCESS_SERVICE_CHECK_RESULT;
> [1074873519] Caught SIGSEGV, shutting down...
> 
> Nagios appears to be truncating the command sent to it.  I checked and there's no problem with the external command file.
> 
> I'm writing directly to the command file from the same machine.
> 
> Is there anything information on throttling passive checks through the external command file to keep Nagios from crashing??
> 
> Right now I'm just pinging the hosts and have 3200 services. This monitoring requirement is going to expand to 7200 hosts with 21000 service checks.
> 
> 
> Help!!

What about only submitting the command to Nagios in the event of an 
exception, i.e. the ping fails?

-------------------------------------------------------------------------------------------------------------------

This email and any files transmitted with it may contain confidential and/or proprietary information.  It is intended solely for the use of the individual or entity who is the intended recipient.  Unauthorized use of this information is prohibited.  If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on.


-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
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