<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <meta name=Generator content="Microsoft Word 11 (filtered medium)"> <style>  </style> </head> <body lang=ES link=blue vlink=purple> <div class=Section1> Hello everyone.<o:p></o:p> <o:p> </o:p> I was having problems with “segmentation fault” using check_ping command, and I found some info on this list regarding that and suggesting to use check_icmp instead.<o:p></o:p> Check_icmp is great… it’s faster, and don’t consume much resources, but I’m having this problem:<o:p></o:p> <o:p> </o:p> It works fine for some hours, but suddenly all hosts are reported as “DOWN” with packet loss of 100%<o:p></o:p> I get the net interface down with ifconfig, and then back up again, and nothing. I have to restart the server and then it works fine again.<o:p></o:p> The hosts I’m monitoring are up, and if I use a normal “ping” command to reach them, I get reply.<o:p></o:p> Also if I use “check_ping” from shell, I get PING OK - Packet loss = 0%, RTA = 109.81 ms<o:p></o:p> <o:p> </o:p> If I issue a “check_icmp” from shell I get this:<o:p></o:p> <o:p> </o:p> setsockopt failed<o:p></o:p> Setting alarm timeout to 10 seconds<o:p></o:p> packets: 5, targets: 1<o:p></o:p> target_interval: 0.000, pkt_interval 80.000<o:p></o:p> crit.rta: 500.000<o:p></o:p> max_completion_time: 3400.000<o:p></o:p> crit = {500000, 80%}, warn = {200000, 40%}<o:p></o:p> pkt_interval: 80000 target_interval: 0 retry_interval: 0<o:p></o:p> icmp_pkt_size: 64 timeout: 10<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> time_passed: 437412 final_wait: 2962588 max_completion_time: 3400000<o:p></o:p> Waiting for 2962588 micro-seconds (2962.588 msecs)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> handle_random_icmp(0x804ce74, 0xbfbfeb70)<o:p></o:p> icmp_sent: 5 icmp_recv: 0 icmp_lost: 0<o:p></o:p> targets: 1 targets_alive: 1<o:p></o:p> CRITICAL -<o:p></o:p> 168.234.205.12: rta nan, lost 100%|<o:p></o:p> rta=0.000ms;200.000;500.000;0; pl=100%;40;80;;<o:p></o:p> targets: 1, targets_alive: 0<o:p></o:p> <o:p> </o:p> Has anyone experienced the same problem. Any ideas suggestions ?<o:p></o:p> <o:p> </o:p> If it helps:<o:p></o:p> I’m using FreeBSD 6.0 Stable and installed nagios from ports.<o:p></o:p> <o:p> </o:p> Thanks in advance for your help.<o:p></o:p> <o:p> </o:p> Alejandro Mejía Evertsz<o:p></o:p> </div> </body> </html>