However, what still bothers me are the error notifications when powering up the windows client. Here is the log:
Code: Select all
Level INFO 10/10/2013 17:25:27 Detected OS as Windows NT
Level NOTICE 10/10/2013 17:25:27 Network UPS Tools upsmon 2.0.0b
Level INFO 10/10/2013 17:25:27 Config Load: MINSUPPLIES set to 1
Level INFO 10/10/2013 17:25:27 Config Load: NOTIFYCMD set to c:\Program Files (x86)\WinNUT\alertPopup.exe
Level INFO 10/10/2013 17:25:27 Config Load: POLLFREQ set to 10
Level INFO 10/10/2013 17:25:27 Config Load: POLLFREQALERT set to 5
Level INFO 10/10/2013 17:25:27 Config Load: HOSTSYNC set to 15
Level INFO 10/10/2013 17:25:27 Config Load: DEADTIME set to 20
Level INFO 10/10/2013 17:25:27 Config Load: RBWARNTIME set to 43200
Level INFO 10/10/2013 17:25:27 Config Load: NOCOMMWARNTIME set to 300
Level INFO 10/10/2013 17:25:27 Config Load: FINALDELAY set to 5
Level INFO 10/10/2013 17:25:27 UPS: asustor@192.168.2.111 (slave) (power value 1)
Level ERROR 10/10/2013 17:25:48 UPS [asustor@192.168.2.111]: connect failed: Connection failure: Unknown error
Level NOTICE 10/10/2013 17:25:48 Communications with UPS asustor@192.168.2.111 lost
Level ERROR 10/10/2013 17:26:21 UPS [asustor@192.168.2.111]: connect failed: Connection failure: Unknown error
Level NOTICE 10/10/2013 17:26:21 UPS asustor@192.168.2.111 is unavailable
Level ERROR 10/10/2013 17:26:32 Can't login to UPS [asustor@192.168.2.111]: Access denied
Level NOTICE 10/10/2013 17:26:43 Communications with UPS asustor@192.168.2.111 established
Code: Select all
MONITOR asustor@192.168.2.111 1 admin password slave
And just to be complete - I don't think this has anything to do with the issue - within ADM the UPS is not getting recognized correctly even though according to the compatibility list it is considered compatible: