Re: [Nut-upsuser] problem starting upsd
Citeren James bjloc...@lockie.ca: $ sudo /usr/sbin/upsd - Network UPS Tools upsd 2.4.3 0.00 listen_add: added ::1:3493 0.84 listen_add: added 127.0.0.1:3493 0.000102 setuptcp: try to bind to 127.0.0.1 port 3493 0.000185 listening on 127.0.0.1 port 3493 0.000204 setuptcp: try to bind to ::1 port 3493 0.001328 setuptcp: socket: Address family not supported by protocol 0.001381 not listening on ::1 port 3493 Apparently the version of NUT you're using was built on a system that had IPv6 enabled and yours doesn't. Adding LISTEN 127.0.0.1 to 'upsd.conf' should fix this. See also 'man 5 upsd.conf'. Best regards, Arjen -- Please keep list traffic on the list (off-list replies will be rejected) ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] NUT, USB, OpenIndiana
I'm about to deploy en OpenIndiana (the heir of OpenSolaris) box as my main iSCSI backend. However, all attempts at getting NUT 2.6 to work with my usbhid-ups cyberpower has resulted in the driver going down with a segmentation fault. Is there a known problem with nut+usb+openindiana (opensolaris), or am I just doing something wrong? //Svein -- +---+--- /\ |Svein Skogen | sv...@d80.iso100.no \ / |Solberg Østli 9| PGP Key: 0xE5E76831 X|2020 Skedsmokorset | sv...@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | sv...@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listm...@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +---+--- |msn messenger: | Mobile Phone: +47 907 03 575 |sv...@jernhuset.no | RIPE handle:SS16503-RIPE +---+--- A: Because it fouls the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail? Picture Gallery: https://gallery.stillbilde.net/v/svein/ signature.asc Description: OpenPGP digital signature ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
Re: [Nut-upsuser] NUT, USB, OpenIndiana
On Mar 13, 2011, at 6:39 AM, Svein Skogen (Listmail account) wrote: I'm about to deploy en OpenIndiana (the heir of OpenSolaris) box as my main iSCSI backend. However, all attempts at getting NUT 2.6 to work with my usbhid-ups cyberpower has resulted in the driver going down with a segmentation fault. Have you been able to get a core dump, or any other indication of where the segfault is occurring? Is there a known problem with nut+usb+openindiana (opensolaris), or am I just doing something wrong? A few years ago, I think Arnaud worked with some of the Solaris engineers to get NUT to work with their libusb port, but I don't know how much has changed between that and the USB stack in OpenIndiana. -- Charles Lepple clepple@gmail ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
[Nut-upsuser] Problems with usbhid-ups and CyberPower CP1500 on 2.6.0
I've been running the Debian packaged 2.4.3 for a while, working find. When 2.6.0-1 just pushed through to debian, things have stopped working :( I checked what had been the usual suspects in past problems, namely permissions problems in /dev/bus/usb, but all seems in order: $ lsusb ... Bus 009 Device 002: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS $ ls -l /dev/bus/usb/009/002 crw-rw-r-- 1 root nut 189, 1025 Mar 14 00:50 /dev/bus/usb/009/002 But if I run the driver with debugging enabled, it gives this: $ sudo /lib/nut/usbhid-ups -a cp1500 -D -D -D ... 0.135837 Checking device (0764/0501) (009/002) 0.158857 - VendorID: 0764 0.158870 - ProductID: 0501 0.158876 - Manufacturer: CPS 0.158882 - Product: CP 1500C 0.158887 - Serial Number: unknown 0.158891 - Bus: 009 0.158896 Trying to match device 0.158933 Device matches 0.166875 HID descriptor, method 1: (9 bytes) = 09 21 10 01 21 01 22 83 01 0.166892 HID descriptor, method 2: (9 bytes) = 09 21 10 01 21 01 22 83 01 0.166899 HID descriptor length 387 0.21 Report Descriptor size = 387 0.218907 Report Descriptor: (387 bytes) = ... ... 0.219118 Using subdriver: CyberPower HID 0.3 0.223871 libusb_get_report: error sending control message: Operation not permitted 0.223890 Can't retrieve Report 01: Operation not permitted 0.223902 Path: UPS.PowerSummary.iProduct, Type: Feature, ReportID: 0x01, Offset: 0, Size: 8 0.228837 libusb_get_report: error sending control message: Operation not permitted 0.228860 Can't retrieve Report 02: Operation not permitted ... much repeating of stuff like this for many Paths ... 0.448872 Report descriptor retrieved (Reportlen = 387) 0.448878 Found HID device 0.448882 Detected a UPS: CPS/ CP 1500C 0.453873 libusb_get_report: error sending control message: Operation not permitted 0.453890 Can't retrieve Report 03: Operation not permitted 0.453898 Can't initialize data from HID UPS exits with return code 1 If I run it under strace, the ioctls on the /dev/bus/usb file descriptor preceeding each operation not permitted error return 0, not an error code such as EPERM. If I run it with -u root so that it doesn't drop permissions, it seems to work OK. That doesn't work from ups.conf, though, and running the driver as root changes the permissions for the socket in /var/run such that the rest of nut can't talk to the driver! I can fix that by manually chmod'ing the socket after startup, but that leaves things in a bit of a mess. Exact versions of related packages: nut 2.6.0-1 libupsclient1 2.6.0-1 libusb-0.1-4 2:0.1.12-17 ___ Nut-upsuser mailing list Nut-upsuser@lists.alioth.debian.org http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
