× NETGEAR will be terminating ReadyCLOUD service by July 1st, 2023. For more details click here.
Orbi WiFi 7 RBE973
Reply

Getting the UPS recognized (OS 6)

pst
Tutor
Tutor

Getting the UPS recognized (OS 6)

Hi,

I'm running 6.1.8 on a ReadyNAS Pro (unsupported configuration), and have a APC Back-UPS XS-1000 plugged into the USB port.

It is partially recognizing the UPS, but not fully. Assuming the NUT code runs the same as normal Linux, upsmon is failing because it can't find the UPS. I'm guessing some sort of dependency failure because we're missing either a database entry for the back-ups or we're missing a system utility like lsusb.

I know Infrant (oops, Netgear) has a known issue report about the UPS not coming up at first, but then it starts. This has gone on for >24 hours now, so I'm pretty sure it's a hard failure (especially given the logs included here...)

kernel messages:

usb 5-2: new low-speed USB device number 2 using uhci_hcd
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


system log:

usb 5-2: new low-speed USB device number 2 using uhci_hcd
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
Network UPS Tools - Generic HID driver 0.37 (2.6.5)
USB communication driver 0.31
No matching HID UPS found
Driver failed to start (exit status=1)
Network UPS Tools - UPS driver controller 2.6.5
nut-driver.service: control process exited, code=exited status=1
Job nut-server.service/start failed with result 'dependency'.
Unit nut-driver.service entered failed state.
Error in 'ststemctl start nut-driver
A dependency job failed. See system journal for details.
fopen /var/run/nut/upsmon.pid: No such file or directory
UPS: UPS@localhost (master) (power value 1)
PID file /var/run/nut/upsmon.pid not readable (yet?) after start.
Startup successful
UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
nut-monitor.service: Supervising process 5684 which is not our child. We'll most likely not notice when it exits.
Error: Connection failure: Connection refused
Error: Connection failure: Connection refused
New UPS on Port:USB detected. Manufacturer: , Model: , Serial: BB0100009999.
Error communicating with UPS 'UPS' ().
UPS [UPS@localhost]: connect failed: Connection failure: Connection refused
Cannot communicate with UPS 'UPS' ().
UPS [UPS@localhost]: connect failed: Connection failure: Connection refused


/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


Any thoughts? Given that this is an unsupported OS on this hardware, Netgear customer support won't support.
Message 1 of 1
Top Contributors
Discussion stats
  • 0 replies
  • 4718 views
  • 0 kudos
  • 1 in conversation
Announcements