Jonathan Borg
2011-Nov-13 19:58 UTC
[Nut-upsuser] Installing Powercom BNT-2000AP on CentOS 5.6
Hi Guys, Am a Linux newbie and need some help setting up this UPS with NUT on Cent OS 5.6. So basically I have the following packages installed with yum: libusb-devel-0.1.12-5.1.x86_64 libusb-devel-0.1.12-5.1.i386 libusb-0.1.12-5.1.x86_64 libusb-0.1.12-5.1.i386 nut-2.2.2-1.el5.x86_64 When I run service ups start I get the following: Starting UPS driver controller: [FAILED] Starting upsd: [ OK ] Starting UPS monitor (master): [ OK ] Broadcast message from nut (Sun Nov 13 20:47:31 2011): Communications with UPS pcom at localhost lost When I run /sbin/upsdrvctl start pcom I get the following: Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) No matching HID UPS found Driver failed to start (exit status=1) and when I run lsusb I can see the UPS that it is hooked up Bus 005 Device 002: ID 0d9f:0004 Powercom Co., Ltd I am outputting the directory /etc/ups using ls -l total 32 -rwxrwxrwx 1 root root 18 Nov 13 19:46 nut.conf -rwxrwxrwx 1 root nut 3625 Nov 13 19:30 ups.conf -rwxrwxrwx 1 root nut 2009 Nov 13 19:46 upsd.conf -rwxrwxrwx 1 root nut 2250 Nov 13 19:01 upsd.users -rwxrwxrwx 1 root nut 11900 Nov 11 17:43 upsmon.conf -rwxrwxrwx 1 root nut 3891 Mar 23 2011 upssched.conf ups.conf: user = root [pcom] driver=usbhid-ups port=auto productid=0004 upsmon.conf upsdrvctl start pcom -DDDDD Network UPS Tools - UPS driver controller 2.2.2 Network UPS Tools: 0.29 USB communication driver - core 0.33 (2.2.2) No matching HID UPS found Driver failed to start (exit status=1) Am not sure how to tackle the problem... Maybe it is permissions - related. Any help please? Jon -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20111113/be0c5207/attachment.html>
Charles Lepple
2011-Nov-14 01:56 UTC
[Nut-upsuser] Installing Powercom BNT-2000AP on CentOS 5.6
On Nov 13, 2011, at 2:58 PM, Jonathan Borg wrote:> Hi Guys, > > Am a Linux newbie and need some help setting up this UPS with NUT on Cent OS 5.6. So basically I have the following packages installed with yum: > > libusb-devel-0.1.12-5.1.x86_64 > libusb-devel-0.1.12-5.1.i386 > libusb-0.1.12-5.1.x86_64 > libusb-0.1.12-5.1.i386 > nut-2.2.2-1.el5.x86_64You may want to find a newer RPM (from rawhide?) - we're on 2.6.2 now.> and when I run lsusb I can see the UPS that it is hooked up > > Bus 005 Device 002: ID 0d9f:0004 Powercom Co., LtdMake sure the nut user can write to /dev/bus/usb/005/002 (or wherever usbdevfs/usbfs is mounted). Group write permission should be sufficient.> I am outputting the directory /etc/ups using ls -l > total 32 > -rwxrwxrwx 1 root root 18 Nov 13 19:46 nut.conf > -rwxrwxrwx 1 root nut 3625 Nov 13 19:30 ups.conf > -rwxrwxrwx 1 root nut 2009 Nov 13 19:46 upsd.conf > -rwxrwxrwx 1 root nut 2250 Nov 13 19:01 upsd.users > -rwxrwxrwx 1 root nut 11900 Nov 11 17:43 upsmon.conf > -rwxrwxrwx 1 root nut 3891 Mar 23 2011 upssched.confRemember to remove read/write permission from at least upsd.users and upsmon.conf, since they contain passwords.> ups.conf: > user = root > [pcom] > driver=usbhid-ups > port=auto > productid=0004Generally speaking, if you need to specify a productid in ups.conf, then the udev rules don't know about your USB vendor/product ID combination, either. Search for 0d9f in your NUT udev rules file, and copy one of those lines (replacing the product ID with yours, 0004).