On Feb 4, 2014, at 10:48 PM, Elliot Dierksen wrote: > NUT will complain endlessly about communication errors and never establish > SNMP communication with my APC UPS
Hmm, at first glance, I read the "complain endlessly" part as a figure of speech, and figured SNMP would get there eventually since it's UDP. But if you have to stop and restart NUT, that is a different story. What errors are you actually getting from NUT? If upsd is trying to bind to the aggregated interface before it gets an IP address, then I'm not really sure what we should do, since network comms (at least loopback) is a prerequisite for NUT. I think that should be handled by the init system, with a dependency on the network interfaces being fully started. (I haven't looked at the FreeNAS init system much.) If the comms errors are from the SNMP driver, then we should be able to tweak the retry settings in the driver itself, or get the driver to fail and rely on the maxretry/retrydelay that I mentioned earlier. Then, the question becomes "where is the driver getting stuck?" -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
