On Oct 26, 2016, at 4:56 AM, Tomasz Przychodzień wrote: > > Level INFO 10/26/2016 10:46:17 Detected OS as Windows NT > Level NOTICE 10/26/2016 10:46:17 Network UPS Tools upsmon 2.0.0.4 > Level INFO 10/26/2016 10:46:17 Config Load: MINSUPPLIES set to 1 > Level INFO 10/26/2016 10:46:17 Config Load: NOTIFYCMD set to > "c:\Program Files\WinNUT\alertPopup.exe" > Level INFO 10/26/2016 10:46:17 Config Load: POLLFREQ set to 5 > Level INFO 10/26/2016 10:46:17 Config Load: POLLFREQALERT set to 5 > Level INFO 10/26/2016 10:46:17 Config Load: HOSTSYNC set to 15 > Level INFO 10/26/2016 10:46:17 Config Load: DEADTIME set to 15 > Level INFO 10/26/2016 10:46:17 Config Load: RBWARNTIME set to 43200 > Level INFO 10/26/2016 10:46:17 Config Load: NOCOMMWARNTIME set to > 300 > Level INFO 10/26/2016 10:46:17 Config Load: FINALDELAY set to 5
I'm not as familiar with WinNUT, but I assume that your MONITOR line should be listed here. If any of the parameters have spaces in them (i.e. the password), make sure they are in quotes. > Level CRITICAL 10/26/2016 10:46:17 Fatal error: insufficient power > configured! > Level CRITICAL 10/26/2016 10:46:17 Sum of power values........: 0 > Level CRITICAL 10/26/2016 10:46:17 Minimum value (MINSUPPLIES): 1 > Level CRITICAL 10/26/2016 10:46:17 > Edit your upsmon.conf and change the values. > > Should I change MINSUPPLIES to 0? (WinNUT runs then - has "Running as > Application" status - how can I test if it's really working?). Does it make > any sense to have MINSUPPLIES at 0? Given your original description (send a signal to the PC to shut it dow during a power outage), MINSUPPLIES should be 1. The upsmon.conf documentation describes the case where you might set MINSUPPLIES to 0 in order to monitor an UPS that is not powering the computer: http://networkupstools.org/docs/man/upsmon.conf.html _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
