NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
APC 1200 via USB not working
I have a ReadyNAS Pro 4 (4.2.31) connected to an APC XS 1200 via USB with no issues. I moved that USB to this my other ReadyNAS 426 (6.10.4) and I get the following errors (I removed the serial n...
I have the same problem with an APC BackUPS RS 1000 - I get
New USB UPS detected. Manufacturer: , Model: , Serial: <xxxxxxxxxxx>
Error communicating with UPS 'UPS' ()
Cannot communicate with UPS 'UPS' ()
This looks like a supported UPS as per Network UPS Tools.
To follow up further on the UPS not recognised, the systemd-journal log shows the following:
Apr 19 19:30:21 readynas systemd[1]: nut-driver.service: Service hold-off time over, scheduling restart. Apr 19 19:30:21 readynas systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked. Apr 19 19:30:21 readynas systemd[1]: Stopped Network UPS Tools - power device driver controller. Apr 19 19:30:21 readynas systemd[1]: Starting Network UPS Tools - power device driver controller... Apr 19 19:30:21 readynas upsdrvctl[12644]: Network UPS Tools - Generic HID driver 0.41 (2.7.4) Apr 19 19:30:21 readynas upsdrvctl[12644]: USB communication driver 0.33 Apr 19 19:30:21 readynas upsdrvctl[12644]: No matching HID UPS found Apr 19 19:30:21 readynas upsdrvctl[12644]: Driver failed to start (exit status=1) Apr 19 19:30:21 readynas upsdrvctl[12644]: Network UPS Tools - UPS driver controller 2.7.4 Apr 19 19:30:21 readynas systemd[1]: nut-driver.service: Control process exited, code=exited status=1 Apr 19 19:30:21 readynas systemd[1]: Failed to start Network UPS Tools - power device driver controller. Apr 19 19:30:21 readynas systemd[1]: nut-driver.service: Unit entered failed state. Apr 19 19:30:21 readynas systemd[1]: nut-driver.service: Failed with result 'exit-code'. Apr 19 19:30:22 readynas upsmon[9182]: Poll UPS [UPS@localhost] failed - Driver not connected Apr 19 19:30:23 readynas systemd[1]: nut-driver.service: Service hold-off time over, scheduling restart. Apr 19 19:30:23 readynas systemd[1]: systemd-journald-audit.socket: Cannot add dependency job, ignoring: Unit systemd-journald-audit.socket is masked. Apr 19 19:30:23 readynas systemd[1]: Stopped Network UPS Tools - power device driver controller. Apr 19 19:30:23 readynas systemd[1]: Starting Network UPS Tools - power device driver controller... Apr 19 19:30:23 readynas upsdrvctl[12648]: Network UPS Tools - Generic HID driver 0.41 (2.7.4) Apr 19 19:30:23 readynas upsdrvctl[12648]: USB communication driver 0.33 Apr 19 19:30:23 readynas upsdrvctl[12648]: No matching HID UPS found Apr 19 19:30:23 readynas upsdrvctl[12648]: Driver failed to start (exit status=1) Apr 19 19:30:23 readynas upsdrvctl[12648]: Network UPS Tools - UPS driver controller 2.7.4 Apr 19 19:30:23 readynas systemd[1]: nut-driver.service: Control process exited, code=exited status=1 Apr 19 19:30:23 readynas systemd[1]: Failed to start Network UPS Tools - power device driver controller. Apr 19 19:30:23 readynas systemd[1]: nut-driver.service: Unit entered failed state. Apr 19 19:30:23 readynas systemd[1]: nut-driver.service: Failed with result 'exit-code'.
And the usb-devices.log shows
1-0:1.0 1-1 product=Back-UPS RS 1000 FW:7.g9a.I USB FW:g9a idProduct=0002 idVendor=051d devnum=6 speed=1.5 1-1:1.0 2-0:1.0
The ups.log shows no sign of this UPS at all.
Hopefully this helps us to find a solution? Or do I really have to file a ticket for warranty "replacement"?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
