[Nut-upsuser] driver error
Hi, I'm trying to install NUT on Ubuntu. All is good until I try to start the driver, then I get this error: $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 This APC device (051d:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0003' option. Please report your results to the NUT user's mailing list nut-upsuser@lists.alioth.debian.org. No matching HID UPS found Driver failed to start (exit status=1) I'm using an APC SmartUPS 1500 VA 120V RM2U, it is connected via USB. I would appreciate any suggestions from the list. Looks like apt-get install gave me version 2.4.3, apt also claims this is the latest version. Thanks, Steve Boyle ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver error
On Sep 14, 2011, at 6:03 PM, Steve Boyle wrote: Hi, I’m trying to install NUT on Ubuntu. All is good until I try to start the driver, then I get this error: $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 This APC device (051d:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0003' option. Please report your results to the NUT user's mailing list nut-upsuser@lists.alioth.debian.org. No matching HID UPS found Driver failed to start (exit status=1) I’m using an APC SmartUPS 1500 VA 120V RM2U, it is connected via USB. I would appreciate any suggestions from the list. Looks like apt-get install gave me version 2.4.3, apt also claims this is the latest version. APC 5G units with that product ID are supported as of NUT 2.6.0, which is available in Ubuntu natty and later. Usually we would encourage you to follow the advice in the error message, and add -x productid=0003 to the command line of the driver, but judging from the changes necessary to support these units, I think you would have better luck bugging the Ubuntu LTS folks for a backport of the latest version of NUT.___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver error
Hi, Actually, I just got it working. I found this thread: http://comments.gmane.org/gmane.comp.monitoring.nut.user/6546 I downloaded the 2.6.1 source and found the entry I needed to add to 52-nut-usbups.rules. I also had to add productid = 0003 to the ups.conf file. Seems to be working now. Are there new features for this the APC SmartUPS G5 that I would benefit from by upgrading to 2.6.x? Thanks, Steve Boyle From: Charles Lepple [mailto:clep...@gmail.com] Sent: Wednesday, September 14, 2011 4:48 PM To: Steve Boyle Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] driver error On Sep 14, 2011, at 6:03 PM, Steve Boyle wrote: Hi, I'm trying to install NUT on Ubuntu. All is good until I try to start the driver, then I get this error: $ sudo upsdrvctl start Network UPS Tools - UPS driver controller 2.4.3 Network UPS Tools - Generic HID driver 0.34 (2.4.3) USB communication driver 0.31 This APC device (051d:0003) is not (or perhaps not yet) supported by usbhid-ups. Please make sure you have an up-to-date version of NUT. If this does not fix the problem, try running the driver with the '-x productid=0003' option. Please report your results to the NUT user's mailing list nut-upsuser@lists.alioth.debian.orgmailto:nut-upsuser@lists.alioth.debian.org. No matching HID UPS found Driver failed to start (exit status=1) I'm using an APC SmartUPS 1500 VA 120V RM2U, it is connected via USB. I would appreciate any suggestions from the list. Looks like apt-get install gave me version 2.4.3, apt also claims this is the latest version. APC 5G units with that product ID are supported as of NUT 2.6.0, which is available in Ubuntu natty and later. Usually we would encourage you to follow the advice in the error message, and add -x productid=0003 to the command line of the driver, but judging from the changes necessary to support these units, I think you would have better luck bugging the Ubuntu LTS folks for a backport of the latest version of NUT. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver error
On Wed, Sep 14, 2011 at 7:53 PM, Steve Boyle steve.bo...@connexity.com wrote: Hi, Actually, I just got it working. I found this thread: http://comments.gmane.org/gmane.comp.monitoring.nut.user/6546 I downloaded the 2.6.1 source and found the entry I needed to add to 52-nut-usbups.rules. I also had to add productid = 0003 to the ups.conf file. Seems to be working now. Adding productid = 0003 is equivalent to the -x option mentioned. Are there new features for this the APC SmartUPS G5 that I would benefit from by upgrading to 2.6.x? Not so much a feature as preventing problems down the road, you may want to add the pollonly flag per this discussion from an APC employee: http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-June/004847.html (I didn't check that before; for some reason I thought pollonly wasn't available in 2.4.3 yet) -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] driver error
Cool, thanks for the tip. Most appreciated. Regards, Steve -Original Message- From: Charles Lepple [mailto:clep...@gmail.com] Sent: Wednesday, September 14, 2011 5:07 PM To: Steve Boyle Cc: nut-upsuser@lists.alioth.debian.org Subject: Re: [Nut-upsuser] driver error On Wed, Sep 14, 2011 at 7:53 PM, Steve Boyle steve.bo...@connexity.com wrote: Hi, Actually, I just got it working. I found this thread: http://comments.gmane.org/gmane.comp.monitoring.nut.user/6546 I downloaded the 2.6.1 source and found the entry I needed to add to 52-nut-usbups.rules. I also had to add productid = 0003 to the ups.conf file. Seems to be working now. Adding productid = 0003 is equivalent to the -x option mentioned. Are there new features for this the APC SmartUPS G5 that I would benefit from by upgrading to 2.6.x? Not so much a feature as preventing problems down the road, you may want to add the pollonly flag per this discussion from an APC employee: http://lists.alioth.debian.org/pipermail/nut-upsdev/2010-June/004847.html (I didn't check that before; for some reason I thought pollonly wasn't available in 2.4.3 yet) -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Slaves under Squeeze
On Wed, Sep 14, 2011 at 7:57 PM, Rob Donovan hikerman2005-...@yahoo.com wrote: hi, I recently upgraded my Debian Lenny system to Squeeze, and have been happily running nut as a MODE=standalone system talking to my Cyberpower 1500 avr lcd via the usbhid-ups driver for a couple of weeks or so. No problems. Now I'm trying to hang another machine off the same ups as a slave, and it isn't working. The problem I'm getting is best illustrated by what happens when I run this on the server: upsd -D Network UPS Tools upsd 2.4.3 0.00 listen_add: added 127.0.0.1:3493 0.70 listen_add: added 192.168.1.104:3493 0.000117 setuptcp: try to bind to 192.168.1.104 port 3493 0.000204 setuptcp: bind: Cannot assign requested address 0.000226 not listening on 192.168.1.104 port 3493 The short answer is that the listen directive specifies the address on the *server* that will be used for listening. I think you're trying to specify that the server should only listen to that one slave. Those rules are best handled by the system firewall (and/or by tcp_wrappers), which is why we dropped the ACL syntax from NUT. Your choices for the listen directive are basically any of the addresses shown in 'ifconfig', or 0.0.0.0 to listen on all IPv4 interfaces. -- - Charles Lepple ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Slaves under Squeeze
Thanks - that brought me more progress than I've seen all day :) Changing to the following on the server : upsd.conf: LISTEN 0.0.0.0 with no other changes from what I posted on the previous page got both the server and slave nuts starting up ok. For the record ifconfig on the server returns the following: eth0Link encap:Ethernet HWaddr 00:26:b9:8d:18:b5 inet addr:192.168.1.102 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::226:b9ff:fe8d:18b5/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:7078694 errors:0 dropped:0 overruns:0 frame:0 TX packets:7756421 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:973255191 (928.1 MiB) TX bytes:1064820280 (1015.4 MiB) Interrupt:16 loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:16436 Metric:1 RX packets:12697367 errors:0 dropped:0 overruns:0 frame:0 TX packets:12697367 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:1351490194 (1.2 GiB) TX bytes:1351490194 (1.2 GiB) Instead of LISTENing to 0.0.0.0 I tried LISTENing to 192.168.1.102 or 00:26:b9:8d:18:b5 or fe80::226:b9ff:fe8d:18b5/64 but none worked when running /etc/init.d/nut start on the server (all gave immediate Communications with UPS cp1500avr1@localhost lost errors). ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Slaves under Squeeze
Changing to the following on the server : upsd.conf: LISTEN 127.0.0.1 LISTEN 192.168.1.102 also works :) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] Slaves under Squeeze
On Sep 14, 2011, at 9:19 PM, Rob Donovan wrote: Changing to the following on the server : upsd.conf: LISTEN 127.0.0.1 LISTEN 192.168.1.102 also works :) :-) The typical application for listening on just a subset of the interfaces is on a gateway machine, where you want to allow access from the inside network, but not from the outside. That usually means more than one physical network interface (not counting loopback). Again, it is best backed up by firewall rules. ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
