Hi Larry, [please use reply-all to include the list - the NUT lists do not add a reply-to header.]
On Oct 21, 2015, at 3:23 PM, Larry Baker <[email protected]> wrote: > > I use the NUT RPM package for CentOS 6.7, which is version 2.6.5-2. I admit I am not too familiar with the RH/CentOS family these days. Is there a CentOS site for keeping tabs on the NUT RPMs, or is it sufficient to use rpmfind.net? (I'm assuming you were able to grab a SRPM file and rebuild with your patch - this procedure is something that we really should have in the distro-specific documentation for NUT.) > I am testing implementation of NUT features with APC and Tripp-Lite USB UPS > interfaces. Things are going reasonably well. However, I'm seeing many more > messages than I would like in /var/log/messages when I boot the system > without the UPS connected (testing a failure scenario). I have configured > NOCOMMWARNTIME 3600, which takes care to only broadcast to logged in > terminals and send me emails once an hour. However, /var/log/messages is > being filled with "upsmon[2391]: Poll UPS [tripplite@localhost] failed - > Driver not connected" messages every five seconds. I cannot seem to find a > way to reduce that chatter. I saw your email on nut-upsuser, and started poking around in that code. I agree - there does not seem to be a set of configuration options to reduce the logging in this case. (As you can imagine, this logging code was written with the intent of providing feedback during setup, under the assumption that an UPS would always be connected afterwards, and the "Poll failed" log messages would go away. The unreliability of many inexpensive USB UPSes has invalidated that assumption, IMHO, but that's a different rant.) > I found the "Driver not connected" condition can refer to either the TCP > connection down between the client and the server (fd < 0), or between the > server and the device driver or the device driver and the UPS (commstate <> > 1). The attached patch to pullups() in clients/upsmon.c suppresses the > messages sent to /var/log/messages every five seconds when commstate <> 1, > since DRVNOTCONN is actually expected in that case. > > There is another place in try_connect() in clients/upsmon.c that causes > messages to be written to /var/log/message every five seconds when a TCP > connection cannot be made from the client to the server. (I test this > failure scenario by killing the server upsd.) I changed that to a debugging > message (matching the debugging message earlier in try_connect() logging the > attempt), since the normal message stream and email notifications will still > occur. I think we can make the log messages a bit more specific about what is going on (in particular, making it clearer which connection attempt failed). > The chatter from upsmon writing to /var/log/messages every five seconds > clutters the system log file so much it is hard to deal with. Especially, as > in our case, remotely over very slow Internet connections. With these two > changes, /var/log/messages contains a message, and an email is sent, when the > error condition first occurs and thereafter every NOCOMMWARNTIME seconds. > This is as I expect, and desire. I would still like to keep the functionality of NOCOMMWARNTIME separate from the logging interval for polling failures for individual UPSes, but I think this should be possible with your second patch (which I admit I won't be able to look at in depth until this weekend). > Please consider these changes. > > Larry Baker > US Geological Survey > 650-329-5608 > [email protected] > > > <nut-2.6.5-upsmon.patch>_______________________________________________ > Nut-upsdev mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev -- Charles Lepple clepple@gmail _______________________________________________ Nut-upsdev mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsdev
