Nagios Support Forum

Posted as Fixed in 4.0.2. ..yeah!

steve.gregory wrote:Update: fwiw guys, I've just downloaded the last release of stable v3 and installed this. All is back to normal again. I'll leave v4 for now but i'll follow this stream here still. Thanks, Steve.

I did also and all is working. I am going to have to try 4.0 in test.

define service{ use generic-service host_name pal service_description pal Security Panel ; check_command trace!10.22.16.90!4000.0,80%!5000.0,100% normal_check_interval 30 retry_check_interval 3 notification_interval 0 first_notification_delay 0 max_check_attempts 2 }

From the command line I have always had the correct output as posted before.

[root@plctpapp9 libexec]# ./check_ping -H 10.22.116.2 -w 1000,80% -c 2000,100% -p 5
PING OK - Packet loss = 0%, RTA = 28.24 ms|rta=28.237000ms;1000.000000;2000.000000;0.000000 pl=0%;80;100;0

Yes, this is a check_ping as posted above. The services under each host have a mix of the proper output and not. It is hit or miss as to what one will have the proper output I have 100 host with the 5 or 6 services under them ether a ping or snmp call.

sample of a screen Default route OK 10-04-2013 10:57:17 1d 7h 48m 18s 1/1 10.22.116.1 PING OK 10-04-2013 10:57:31 1d 6h 55m 29s 1/2 OK - 10.22.116.2: rta 14.241ms, lost 0% pal Security Panel OK 10-04-2013 10:50:33 8d 0h 7m 47s 1/2 (No output on stdout) stderr: pal UpTime OK 10-04-2013 10:48:53 39d 6...

Hello,

Does anyone elso have an idea or question that may help?

I have only needed to exclude if I have wild card (*) included in front of my selections.

Also I meant to post this in the general Nagios core not he student. How can I get this moved?

Also this now seems to be hit or miss without any changes some of the status info is being populated.

This is correct.
OK - 10.23.110.2: rta 17.983ms, lost 0%

On some other statuses I still get.
(No output on stdout) stderr

I have not seen any pattern as to what will work and what will not.