GaiusBaltar
Explorer
- Joined
- Jan 15, 2014
- Messages
- 61
Weird issues that i'm not sure if are serious or just false positives that i can ignore.
I've got a CyberPower CTS1300AL UPS (costco rebranded CPS1350AVRLCD) connected to my server
settings under the UPS service are:
About 3o mins later i would keep getting this event in my syslog:
i'd see that pop up every 15-30 mins or so.
after doing some research, i followed the guidelines from this blog and hid the annoyingmessages by adding the below code to to the necessary devd.conf file locations:
Everything was fine until about 2-3 hrs after enabling the UPS service. then i started seeing the following syslog messages below.
These started about 3 hrs after the last reboot (which was Feb2 @ 8:30pm):
i've checked the ups conf files and everything appears in order:
I also checked to ensure i only have 1 copy of the upsmon and usbhids daemons running:
(I assume it is correct behavior to have 2 upsmon processes: 1 under root's account and one under uucp's account)
given all that, communication still looks good/normal:
Finally after all that post spam above, i tried unplugging the UPS from the wall.
I immediately got the UPS ONBATT alert email. and after 5 mins, the SHUTDOWN email (tho even tho the console message said the system was shutting down, it still took an additional 3-5 mins or so (wasn't timing it like i should have) before the shutdown actually commenced.
Sorry for this long as hell mega-post
Any ideas?
I've got a CyberPower CTS1300AL UPS (costco rebranded CPS1350AVRLCD) connected to my server
settings under the UPS service are:
- mode: Master
- port: /dev/ugen1.3
- Driver: CyberPower Systems UPS 2 CPS1350AVRLCD USB (usbhids-ups)
- shutdown mode: goes on battery
- shutdown timer: 300
About 3o mins later i would keep getting this event in my syslog:
Code:
root: Unknown USB device: vendor 0x0764 product 0x0501 bus /dev/ugen1.3
i'd see that pop up every 15-30 mins or so.
after doing some research, i followed the guidelines from this blog and hid the annoyingmessages by adding the below code to to the necessary devd.conf file locations:
Code:
nomatch 10 { match "bus" "uhub[0-9]+"; match "vendor" "0x0764"; match "product" "0x0501"; };
Everything was fine until about 2-3 hrs after enabling the UPS service. then i started seeing the following syslog messages below.
These started about 3 hrs after the last reboot (which was Feb2 @ 8:30pm):
Code:
Feb 3 23:01:20 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 3 23:01:23 freeNAS upsmon[2725]: Poll UPS [CyberPower_CTS1300AL] failed - Data stale Feb 3 23:01:23 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL lost Feb 3 23:01:24 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 3 23:01:28 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL established Feb 4 01:18:51 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 01:18:52 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 01:36:29 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 01:36:30 freeNAS upsmon[2725]: Poll UPS [CyberPower_CTS1300AL] failed - Data stale Feb 4 01:36:30 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL lost Feb 4 01:36:34 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 01:36:35 freeNAS upsmon[2725]: Communications with UPS CyberPower_CTS1300AL established Feb 4 01:38:36 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 01:38:36 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 02:59:21 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 02:59:22 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 03:15:49 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 03:15:49 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 03:19:44 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 03:19:47 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 06:32:39 freeNAS upsd[2717]: Data for UPS [CyberPower_CTS1300AL] is stale - check driver Feb 4 06:32:39 freeNAS upsd[2717]: UPS [CyberPower_CTS1300AL] data is no longer stale Feb 4 09:06:51 freeNAS usbhid-ups[2715]: Got disconnected by another driver: Device busy Feb 4 09:28:24 freeNAS usbhid-ups[2715]: Got disconnected by another driver: Device busy
i've checked the ups conf files and everything appears in order:
Code:
[root@freeNAS ~]# cat /usr/local/etc/nut/upssched.conf CMDSCRIPT /usr/local/bin/custom-upssched-cmd PIPEFN /var/db/nut/upssched.pipe LOCKFN /var/db/nut/upssched.lock AT NOCOMM * EXECUTE EMAIL AT COMMBAD * START-TIMER COMMBAD 10 AT COMMOK * CANCEL-TIMER COMMBAD COMMOK AT FSD * EXECUTE EMAIL AT LOWBATT * EXECUTE EMAIL AT ONBATT * START-TIMER ONBATT 300 AT ONBATT * EXECUTE EMAIL AT ONLINE * CANCEL-TIMER ONBATT ONLINE AT ONLINE * EXECUTE EMAIL AT REPLBATT * EXECUTE EMAIL AT SHUTDOWN * EXECUTE EMAIL _______________________________________________________ [root@freeNAS ~]# cat /usr/local/etc/nut/upsmon.conf FINALDELAY 300 MONITOR CyberPower_CTS1300AL 1 upsmon fixmepass master NOTIFYCMD "/usr/local/sbin/upssched" NOTIFYFLAG ONBATT SYSLOG+WALL+EXEC NOTIFYFLAG LOWBATT SYSLOG+WALL+EXEC NOTIFYFLAG ONLINE SYSLOG+WALL+EXEC NOTIFYFLAG COMMBAD SYSLOG+WALL+EXEC NOTIFYFLAG COMMOK SYSLOG+WALL+EXEC NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC NOTIFYFLAG NOCOMM SYSLOG+EXEC NOTIFYFLAG FSD SYSLOG+EXEC NOTIFYFLAG SHUTDOWN SYSLOG+EXEC SHUTDOWNCMD "/sbin/shutdown -p now" ________________________________________________________ [root@freeNAS ~]# cat /usr/local/etc/nut/ups.conf [CyberPower_CTS1300AL] driver = usbhid-ups port = /dev/ugen1.3 desc = "UPS"
I also checked to ensure i only have 1 copy of the upsmon and usbhids daemons running:
Code:
[root@freeNAS ~]# ps -aux | grep ups uucp 2715 0.0 0.0 14232 2480 ?? Ss 8:30PM 0:04.27 /usr/local/libexec/nut/usbhid-ups -a CyberPower_CTS1300AL uucp 2717 0.0 0.0 20356 3712 ?? Ss 8:30PM 0:00.83 /usr/local/sbin/upsd uucp 2720 0.0 0.0 20332 3676 ?? Is 8:30PM 0:00.05 /usr/local/bin/upslog -s CyberPower_CTS1300AL -l /var/log/ups. root 2723 0.0 0.0 20336 3680 ?? Is 8:30PM 0:00.00 /usr/local/sbin/upsmon localhost uucp 2725 0.0 0.0 20336 3704 ?? S 8:30PM 0:00.72 /usr/local/sbin/upsmon localhost ___________________________________________________________________________________ [root@freeNAS ~]# top | grep ups 2715 uucp 1 20 0 14232K 2436K select 6 0:04 0.00% usbhid-ups 2717 uucp 1 20 0 20356K 3712K select 0 0:01 0.00% upsd 2725 uucp 1 20 0 20336K 3704K nanslp 3 0:01 0.00% upsmon
(I assume it is correct behavior to have 2 upsmon processes: 1 under root's account and one under uucp's account)
given all that, communication still looks good/normal:
Code:
[root@freeNAS ~]# upsc CyberPower_CTS1300AL battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 20 battery.mfr.date: CPS battery.runtime: 3932 battery.runtime.low: 300 battery.type: PbAcid battery.voltage: 13.9 battery.voltage.nominal: 12 device.mfr: CPS device.model: CP 1350C device.type: ups driver.name: usbhid-ups driver.parameter.pollfreq: 30 driver.parameter.pollinterval: 2 driver.parameter.port: /dev/ugen1.3 driver.version: 2.6.5 driver.version.data: CyberPower HID 0.3 driver.version.internal: 0.37 input.transfer.high: 140 input.transfer.low: 90 input.voltage: 123.0 input.voltage.nominal: 120 output.voltage: 123.0 ups.beeper.status: enabled ups.delay.shutdown: 20 ups.delay.start: 30 ups.load: 7 ups.mfr: CPS ups.model: CP 1350C ups.productid: 0501 ups.realpower.nominal: 298 ups.status: OL ups.test.result: Done and warning ups.timer.shutdown: -60 ups.timer.start: 0 ups.vendorid: 0764
Finally after all that post spam above, i tried unplugging the UPS from the wall.
I immediately got the UPS ONBATT alert email. and after 5 mins, the SHUTDOWN email (tho even tho the console message said the system was shutting down, it still took an additional 3-5 mins or so (wasn't timing it like i should have) before the shutdown actually commenced.
Sorry for this long as hell mega-post
Any ideas?