Pandora FMS Community

Remote ICMP network agent (latency) stopped working after update to v7.0NG.751

JonRussell · 17 dic 2020, 15:59 · 5 mensajes · 67 visitas

  1. Inicio del debate

    Hi, I updated Pandora from 750 to 751 yesterday, and since them my network latency monitor has stopped reporting. It is a server monitor on my Pandora server at AWS, that pings my home broadband connection and monitors latency. It's been working fine for over a year, but since the update, it has stopped reporting. I have tried pinging the IP directly from the server in a terminal and that works fine. I cant see anything obvious in the logs on the server. Very odd. Any pointers where to start looking ? [root@pandora pandora]# ping 93.xx.xx.xx PING 93.xx.xx.xx (93.xx.xx.xx) 56(84) bytes of data. 64 bytes from 93.xx.xx.xx: icmp_seq=1 ttl=45 time=16.1 ms 64 bytes from 93.xx.xx.xx: icmp_seq=2 ttl=45 time=16.2 ms (Link not available anymore) (Link not available anymore) Thanks! Jon.

  2. I have the same issue - host latency (icmp_data) module for all agents has stopped working I've tried deleting and recreating but the new module will not initialize Basic Host Alive (icmp_proc) module is working

  3. Same here - upgraded from 750 to 751 and all host latency modules (icmp_data) are now in Unknown status for the last 20 days (ever since upgrade). During the upgrade, I was prompted to install the fping package so I do think that has something to do with it.

  4. Hello, We are working on the problem you mention. At the moment we don't know what is causing it, but I hope you will hear from us soon and that we will be able to fix this bug as soon as possible. We are very sorry for the inconvenience. Regards Diego

  5. Hello First of all, sorry for the wait. We have found the error specifically in the server of the open version of pandora. It is already reported, located and will be fixed for version 752. Sorry for the inconvenience Diego

Entra en tu cuenta para publicar.