NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
UPS issues in 6.2 -- still not fixed
So I've been expecting that at some point the UPS stuff might finally get fixed. It's still busted in 6.2 so it's time to get serious about debugging it.
I am using OS6 on Legacy hardware, so I can't go through official netgear channels. I'm pretty sure this is a failure in Infrant's integration of UPSmon et al, because it works fine on my linux box.
USB is clearly recognizing the APS device, so it's not a kernel driver issue, I think it's just a config failure. Has anyone else looked at this? Is it a problem with nut, or the integration into systemd.
I am using OS6 on Legacy hardware, so I can't go through official netgear channels. I'm pretty sure this is a failure in Infrant's integration of UPSmon et al, because it works fine on my linux box.
USB is clearly recognizing the APS device, so it's not a kernel driver issue, I think it's just a config failure. Has anyone else looked at this? Is it a problem with nut, or the integration into systemd.
Nov 27 12:09:08 waystation kernel: usb 6-1: new low-speed USB device number 2 using uhci_hcd
Nov 27 12:09:13 waystation kernel: generic-usb 0003:051D:0002.0001: hiddev0: USB HID v1.10 Device [American Power Conversion Back-UPS RS 1000 FW:7.g9 .D USB FW:g9 ] on usb-0000:00:1d.1-1/input0
Nov 27 12:09:16 waystation upsdrvctl[14587]: Network UPS Tools - Generic HID driver 0.38 (2.7.2)
Nov 27 12:09:16 waystation upsdrvctl[14587]: USB communication driver 0.32
Nov 27 12:09:16 waystation upsdrvctl[14587]: No matching HID UPS found
Nov 27 12:09:16 waystation upsdrvctl[14587]: Driver failed to start (exit status=1)
Nov 27 12:09:16 waystation upsdrvctl[14587]: Network UPS Tools - UPS driver controller 2.7.2
Nov 27 12:09:16 waystation systemd[1]: nut-driver.service: control process exited, code=exited status=1
Nov 27 12:09:16 waystation systemd[1]: Job nut-server.service/start failed with result 'dependency'.
Nov 27 12:09:16 waystation systemd[1]: Unit nut-driver.service entered failed state.
Nov 27 12:09:16 waystation readynasd[3564]: Error in 'ststemctl start nut-driver
Nov 27 12:09:16 waystation readynasd[3564]: A dependency job failed. See system journal for details.
Nov 27 12:09:17 waystation upsmon[14592]: fopen /var/run/nut/upsmon.pid: No such file or directory
Nov 27 12:09:17 waystation upsmon[14592]: UPS: UPS@localhost (master) (power value 1)
Nov 27 12:09:17 waystation systemd[1]: PID file /var/run/nut/upsmon.pid not readable (yet?) after start.
Nov 27 12:09:17 waystation upsmon[14593]: Startup successful
Nov 27 12:09:17 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Nov 27 12:09:17 waystation systemd[1]: nut-monitor.service: Supervising process 14594 which is not our child. We'll most likely not notice when it exits.
Nov 27 12:09:18 waystation readynasd[3564]: Error: Connection failure: Connection refused
Nov 27 12:09:18 waystation readynasd[3564]: Error: Connection failure: Connection refused
Nov 27 12:09:21 waystation readynasd[3564]: New UPS on Port:USB detected. Manufacturer: , Model: , Serial: BB0100009999.
Nov 27 12:09:22 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Nov 27 12:09:27 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Nov 27 12:09:32 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Nov 27 12:09:37 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Nov 27 12:09:42 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Nov 27 12:09:47 waystation upsmon[14594]: UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
14 Replies
Replies have been turned off for this discussion
- I don't work for Infrant/Netgear, and I don't have access to the source. I was asking mdgm to peek if able.
That said, the data stale error upon initial startup is normal... it should go away in 10-30 seconds usually. That's a bug in the subsystem they integrated.
In this case, -my- bug is that it appears that something in frontview doesn't know how to read properly what the UPS is, and is writing out bogus configuration information to the open source code they are running. - its been going on since I loaded 6.2 on my Ultra 4 plus every 5 seconds which leads me to believe its a usb support issue since I am also having problems with a external drive connected to the front usb port
- Just to follow up on one more thing... since mdgm asked if my change survived a reboot, I *made* it survive a reboot, and now everything is limping along (not fixed, but at least working).
My change was to comment out the serial number for the APC SmartUPS, then I made the file read only to all users, and for good measure, made it immutable (chattr +i ups.conf).
That survives the frontview software trying to write bogus crap into the file. - Weirdest thing... now it works properly, finding the info, and generating it.
Dec 04 19:02:52 waystation kernel: generic-usb 0003:051D:0002.0001: hiddev0: USB HID v1.10 Device [American Power Conversion Back-UPS RS 1000 FW:7.g9 .D USB FW:g9 ] on usb-0000:00:1d.0-2/input0
Dec 04 19:06:41 waystation upsdrvctl[4285]: Using subdriver: APC HID 0.95
Dec 04 19:06:41 waystation upsdrvctl[4285]: Network UPS Tools - Generic HID driver 0.38 (2.7.2)
Dec 04 19:06:41 waystation upsdrvctl[4285]: USB communication driver 0.32
Dec 04 19:06:42 waystation upsdrvctl[4285]: Network UPS Tools - UPS driver controller 2.7.2
Dec 04 19:06:42 waystation usbhid-ups[4305]: Startup successful
Dec 04 19:06:42 waystation upsd[4306]: fopen /var/run/nut/upsd.pid: No such file or directory
Dec 04 19:06:42 waystation upsd[4306]: /etc/nut/upsd.conf is world readable
Dec 04 19:06:42 waystation upsd[4306]: listening on 0.0.0.0 port 3493
Dec 04 19:06:42 waystation upsd[4306]: listening on ::1 port 3493
Dec 04 19:06:42 waystation upsd[4306]: not listening on 127.0.0.1 port 3493
Dec 04 19:06:42 waystation upsd[4306]: Connected to UPS [UPS1]: usbhid-ups-UPS1
Dec 04 19:06:42 waystation upsd[4306]: /etc/nut/upsd.conf is world readable
Dec 04 19:06:42 waystation upsd[4306]: listening on 0.0.0.0 port 3493
Dec 04 19:06:42 waystation upsd[4306]: listening on ::1 port 3493
Dec 04 19:06:42 waystation upsd[4306]: not listening on 127.0.0.1 port 3493
Dec 04 19:06:42 waystation upsd[4306]: Connected to UPS [UPS1]: usbhid-ups-UPS1
Dec 04 19:06:42 waystation upsd[4306]: /etc/nut/upsd.users is world readable
Dec 04 19:06:42 waystation upsd[4306]: /etc/nut/upsd.users is world readable
Dec 04 19:06:42 waystation upsd[4308]: Startup successful
Dec 04 19:06:43 waystation upsmon[4311]: fopen /var/run/nut/upsmon.pid: No such file or directory
Dec 04 19:06:43 waystation upsmon[4311]: UPS: UPS1@localhost (master) (power value 1)
Dec 04 19:06:43 waystation upsmon[4312]: Startup successful
Dec 04 19:06:43 waystation systemd[1]: PID file /var/run/nut/upsmon.pid not readable (yet?) after start.
Dec 04 19:06:43 waystation upsd[4308]: User monuser@::1 logged into UPS [UPS1]
# cat /etc/nut/ups.conf
[UPS1]
driver = usbhid-ups
port = auto
#dashboard: ups_model = Back-UPS RS 1000
#dashboard: ups_mfr = American Power Conversion
#dashboard: ups_mfr_date = 2005/02/09
serial = JB0507020589
vendorid = 051d
productid = 0002
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
