Re: Keepalived loses contact with snmpd when snmpd restarts
Vincent Bernat <[email protected]>
| Newsgroups | gmane.linux.keepalived.devel |
|---|---|
| Message-ID | <[email protected]> |
❦ 23 avril 2015 21:54 -0400, Tom Limoncelli <[email protected]> : >> Rather than waiting 2 minutes, would it be possible to start by trying to >> connect then, if that fails, wait 2 minutes to re-try? It is usual for a >> program to take a little bit of time to start up, but having some features >> fail for the first few minutes is surprising. > > I take that back. I reversed my logic. keepalived does this > already. Right? It's quite buried inside NetSNMP. The only thing that can be controlled from keepalived is how much time should be between each "ping". But, yes, on start, it tries to connect immediately. However, when snmpd is restarted, even when using a reliable transport like a Unix socket, for some reason, libsnmp doesn't detect the failure right now and must wait for the next ping to detect the problem. -- Use library functions. - The Elements of Programming Style (Kernighan & Plauger) ------------------------------------------------------------------------------ One dashboard for servers and applications across Physical-Virtual-Cloud Widest out-of-the-box monitoring support with 50+ applications Performance metrics, stats and reports that give you Actionable Insights Deep dive visibility with transaction tracing using APM Insight. http://ad.doubleclick.net/ddm/clk/290420510;117567292;y _______________________________________________ Keepalived-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/keepalived-devel