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
- If you download the logs, what is the date in bios_ver.log ?
Which legacy ReadyNAS model is this?
Does your UPS have a USB port on the back (must have USB port, serial to USB cable won't work)? - It's an original beta professional pioneer model, and yes, it's using USB on the back.
bios_date=07/26/2010
bios_vendor=American Megatrends Inc.
bios_version=080014
board_asset_tag=To Be Filled By O.E.M.
board_name=To be filled by O.E.M.
board_serial=To be filled by O.E.M.
board_vendor=To be filled by O.E.M.
board_version=To be filled by O.E.M.
chassis_asset_tag=To Be Filled By O.E.M.
chassis_serial=To Be Filled By O.E.M.
chassis_type=3
chassis_vendor=To Be Filled By O.E.M.
chassis_version=To Be Filled By O.E.M.
modalias=dmi:bvnAmericanMegatrendsInc.:bvr080014:bd07/26/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvr07/26/2010FLAME6-MBV2.0:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
product_name=To Be Filled By O.E.M.
product_serial=To Be Filled By O.E.M.
product_sku=To Be Filled By O.E.M.
product_uuid=00020003-0004-0005-0006-000700080009
product_version=07/26/2010 FLAME6-MB V2.0
sys_vendor=To Be Filled By O.E.M.
uevent=MODALIAS=dmi:bvnAmericanMegatrendsInc.:bvr080014:bd07/26/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvr07/26/2010FLAME6-MBV2.0:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
I'm happy to hack and debug, thank you mdgm, I am linux, but less so systemd clufeful. Also, I will PM you with a link of the downloaded logs zip file. - So the UPS has a USB port on it? Good.
Does it make any difference whether you connect the UPS to the front USB port on the NAS or one of the rear ones? - No. Finds it on the front port in the same fashion. UPS is there but is no match to mfg.
Nov 27 13:15:11 waystation upsdrvctl[9112]: Network UPS Tools - Generic HID driver 0.38 (2.7.2)
Nov 27 13:15:11 waystation upsdrvctl[9112]: USB communication driver 0.32
Nov 27 13:15:11 waystation upsdrvctl[9112]: No matching HID UPS found
Nov 27 13:15:11 waystation upsdrvctl[9112]: Driver failed to start (exit status=1)
Nov 27 13:15:11 waystation upsdrvctl[9112]: Network UPS Tools - UPS driver controller 2.7.2
when plugged in back:
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
when plugged in front:
generic-usb 0003:051D:0002.0002: hiddev0: USB HID v1.10 Device [American Power Conversion Back-UPS RS 1000 FW:7.g9 .D USB FW:g9 ] on usb-0000:00:1a.1-2/input0
I'm surprised that it doesn't match in upsdrvctrl....Nov 27 13:15:11 waystation upsdrvctl[9112]: Network UPS Tools - Generic HID driver 0.38 (2.7.2)
Nov 27 13:15:11 waystation upsdrvctl[9112]: USB communication driver 0.32
Nov 27 13:15:11 waystation upsdrvctl[9112]: No matching HID UPS found
Nov 27 13:15:11 waystation upsdrvctl[9112]: Driver failed to start (exit status=1)
Could it be missing an entry for the APC? You guys are running NUT 2.7.2, so I doubt it's this problem, but I'm not sure how to start it in debug mode (that whole systemd thing).
http://comments.gmane.org/gmane.comp.mo ... .user/6719 - I see there is a compatibility issue: https://www.readynas.com/forum/viewtopic.php?p=408218#p408218
- Just one more follow-up. If I edit /etc/nut/ups.conf to comment out the serial number of the UPS, at least the driver comes up now. It looks like the S/N detection code for the UPS serial number that was written in the configuration is broken, which makes quite a bit of sense given that it only appears to be a netgear problem and works fine on my local linux box (where there is no s/n, vendor id, or product id in the config file at all).
root@waystation:/lib/nut# ./usbhid-ups -a UPS
Network UPS Tools - Generic HID driver 0.38 (2.7.2)
USB communication driver 0.32
Using subdriver: APC HID 0.95
root@waystation:/lib/nut# cat /etc/nut/ups.conf
[UPS]
driver = usbhid-ups
port = auto
#dashboard: ups_model =
#dashboard: ups_mfr =
#dashboard: ups_mfr_date =
# serial = BB0100009999
vendorid = 051d
productid = 0002
I cannot speak to the rest of the UPS code working yet, but at least the driver is working properly. Hope this helps! - Given that this is a known issue with the standard software, how do I submit a bug report for this particular instance? I'm not covered by support because this isn't a supported platform?
This has been a bug since 6.0 beta timeframes and worked perfectly in 4.x - Does your change survive a reboot?
- No, neither a reboot or a plug/unplug event keeps the change, and while my edit brings up the ups driver properly, frontview doesn't see it because the ups found doesn't necessarily match the one it's looking for.
Frontview seems to be writing the .conf file, I'm pretty sure whatever it is using for detection/identification code is bad. I didn't strings(1) your netgear binaries yet to find the bad code writing the conf file, as I don't know the structure of frontview.
If you can peek at the source, I might be able to further isolate the problem code. - Hey pst, can take a look at the usb code? I think there is a problem with the support for usb too. I am having issues with my UPS communication with the NAS drive.
Dec 04 12:17:30 NAS upsmon[2541]: Poll UPS [UPS@localhost] failed - Data stale
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
