* Rajko M. [06-14-08 19:23]:

On Saturday 14 June 2008 05:52:02 pm Patrick Shanahan wrote:

...

I have a new UPS device replacing one recently died during a lightning storm and cannot decipher the device location. ... Any help in configuring this device will be appreciated.

hwinfo --usb should give you devices

yes, but not the port, at least that I understand: 22: USB 00.0: 0000 Unclassified device [Created at usb.123] UDI: /org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial Unique ID: hSuP.bXrDS5pQNf9 Parent ID: pBe4.S0BVqOw+Bb6 SysFS ID: /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0 SysFS BusID: 2-2:1.0 Hardware Class: unknown Model: "American Power Conversion Back-UPS Pro 500" Hotplug: USB Vendor: usb 0x051d "American Power Conversion" Device: usb 0x0002 "Back-UPS Pro 500" Revision: "1.01" Serial ID: "3B0808X06916" Driver: "usbhid" Speed: 1.5 Mbps Module Alias: "usb:v051Dp0002d0101dc00dsc00dp00ic03isc00ip00" Driver Info #0: Driver Status: usbhid is active Driver Activation Cmd: "modprobe usbhid" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #21 (Hub) tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Carlos E. R. [06-14-08 19:52]:

The Saturday 2008-06-14 at 19:36 -0400, Patrick Shanahan wrote:

...

...

hwinfo --usb should give you devices

yes, but not the port, at least that I understand:

Then try lsusb

Bus 002 Device 004: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 ?? I still do not understand /dev/????? which is requested by uspd in /etc/ups/ups.conf tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Joe Morris [06-14-08 20:06]:

On 06/15/2008 07:57 AM, Patrick Shanahan wrote:

...

Bus 002 Device 004: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 ?? I still do not understand /dev/????? which is requested by uspd in /etc/ups/ups.conf

/dev/bus/usb/002/004

/etc/usb/usb.conf [myups] driver = apcsmart port = /dev/bus/usb/002/004 desc = "Local UPS" 21:06 wahoo:~ # upsd -D Network UPS Tools upsd 2.0.4 Can't connect to UPS [myups] (apcsmart-004): No such file or directory Synchronizing........ giving up ??? 21:08 wahoo:~ # lsusb Bus 002 Device 004: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500 21:09 wahoo:~ # hwinfo --usb 22: USB 00.0: 0000 Unclassified device [Created at usb.123] UDI: /org/freedesktop/Hal/devices/usb_device_ffffffff_ffffffff_noserial Unique ID: hSuP.bXrDS5pQNf9 Parent ID: pBe4.S0BVqOw+Bb6 SysFS ID: /devices/pci0000:00/0000:00:02.0/usb2/2-2/2-2:1.0 SysFS BusID: 2-2:1.0 Hardware Class: unknown Model: "American Power Conversion Back-UPS Pro 500" Hotplug: USB Vendor: usb 0x051d "American Power Conversion" Device: usb 0x0002 "Back-UPS Pro 500" Revision: "1.01" Serial ID: "3B0808X06916" Driver: "usbhid" Speed: 1.5 Mbps Module Alias: "usb:v051Dp0002d0101dc00dsc00dp00ic03isc00ip00" Driver Info #0: Driver Status: usbhid is active Driver Activation Cmd: "modprobe usbhid" Config Status: cfg=no, avail=yes, need=no, active=unknown Attached to: #21 (Hub) still not there ?? tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Carlos E. R. [06-14-08 21:54]:

See if module "usbhid" is loaded (lsmod), if not load it.

usbhid 70048 1 usbcore 163880 6 usb_storage,usbhid,ohci_hcd,ehci_hcd

Watch the kernel log (probably /var/log/messages, if not try dmesg), and see if some device node is been activated.

USBHID USB Human Interface Device support is enabled.

usb 2-2: USB disconnect, address 4 usb 2-2: new low speed USB device using ohci_hcd and address 5 usb 2-2: new device found, idVendor=051d, idProduct=0002 usb 2-2: new device strings: Mfr=3, Product=1, SerialNumber=2 usb 2-2: Product: Back-UPS ES 750 FW:841.I2 .D USB FW:I2 usb 2-2: Manufacturer: American Power Conversion usb 2-2: SerialNumber: 3B0808X06916 usb 2-2: configuration #1 chosen from 1 choice 22:17 wahoo:~ # grep -i USBHID /var/log/* /var/log/boot.msg:<6>usbcore: registered new driver usbhid /var/log/boot.omsg:<6>usbcore: registered new driver usbhid

There is some documentation in /usr/src/linux-2.6.22.17-0.1/Documentation/input/input.txt. For instance, I'm seeing there how it goes about activating a mouse through that interface.

See:

3.1.1 usbhid ~~~~~~~~~~~~ usbhid is the largest and most complex driver of the whole suite. It handles all HID devices, and because there is a very wide variety of them, and because the USB HID specification isn't simple, it needs to be this big.

Currently, it handles USB mice, joysticks, gamepads, steering wheels keyboards, trackballs and digitizers.

However, USB uses HID also for monitor controls, speaker controls, UPSs, LCDs and many other purposes.

The monitor and speaker controls should be easy to add to the hid/input interface, but for the UPSs and LCDs it doesn't make much sense. For this, the hiddev interface was designed. See Documentation/usb/hiddev.txt for more information about it.

Looking at it now, tks, -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

* Joe Morris [06-14-08 23:39]:

...

What says getfacl /dev/bus/usb/002/004? Does upsd have permissions to that "file"?

23:40 wahoo:~ > getfacl /dev/bus/usb/002/005 getfacl: Removing leading '/' from absolute path names # file: dev/bus/usb/002/005 # owner: root # group: root user::rw- group::r-- other::r-- upsd is running as root

My guess is usbhid-ups does not need the port, as it could change depending on which USB port you plugged into.

with the port line commented in /etc/ups/ups.conf 23:43 wahoo:../eol.svn/trunk # upsd Network UPS Tools upsd 2.0.4 Warning: ignoring incomplete configuration for UPS [myups] Fatal error: at least one UPS must be defined in ups.conf -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/15/2008 11:44 AM, Patrick Shanahan wrote:

with the port line commented in /etc/ups/ups.conf

23:43 wahoo:../eol.svn/trunk # upsd Network UPS Tools upsd 2.0.4 Warning: ignoring incomplete configuration for UPS [myups]

Fatal error: at least one UPS must be defined in ups.conf

man page for usbhid-ups says the port can be set to auto, but it looks like you need to give it the vendorid. Yours looks like it is 051d. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/15/2008 12:47 PM, Patrick Shanahan wrote:

* Joe Morris [06-15-08 00:11]:

...

...

man page for usbhid-ups says the port can be set to auto, but it looks like you need to give it the vendorid. Yours looks like it is 051d.

I do not have any luck with any of them:

00:20 wahoo:../eol.svn/trunk # upsd Network UPS Tools upsd 2.0.4 Can't connect to UPS [myups] (apcsmart-hiddev0): No such file or directory Synchronizing........ giving up

Your UPS is supported by the usbhid-ups driver. You are running 2.0.4. Mine is newer, so I am not sure what the driver was called in 2.0.4. joe@jmorris:~> rpm -q nut nut-2.2.1-1.1 Is your UPS listed in /usr/share/nut/driver.list? Which usb hid driver is listed in /usr/lib/ups/driver? -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/15/2008 01:48 PM, Patrick Shanahan wrote:

00:53 wahoo:../eol.svn/trunk # /usr/lib/ups/driver/upsdrvctl start myups Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0

Unable to open /dev/bus/usb/002/005: Permission denied

Current user id: upsd (105) Serial port owner: root (0) Serial port group: root (0) Mode of port: 0644

Things to try:

- Use another port (with the right permissions)

- Fix the port owner/group or permissions on this port

- Run this driver as another user (upsdrvctl -u or 'user=...' in ups.conf). See upsdrvctl(8) and ups.conf(5).

Fatal error: unusable configuration Driver failed to start (exit status=1)

00:58 wahoo:../eol.svn/trunk # /usr/lib/ups/driver/upsdrvctl -u root start myups Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools (version 2.0.4) - APC Smart protocol driver Driver version 1.99.8, command table version 2.0 tcgetattr(/dev/bus/usb/002/005): Inappropriate ioctl for device Driver failed to start (exit status=1)

Was this with apcsmart still as the driver?

01:03 wahoo:../eol.svn/trunk # /usr/lib/ups/driver/upsdrvctl -u root start myups Network UPS Tools - UPS driver controller 2.0.4 Network UPS Tools: New USB/HID UPS driver 0.28 (2.0.4)

This was with newhidups?

Detected a UPS: American Power Conversion/Back-UPS ES 750 FW:841.I2 .D USB FW:I2 Using subdriver: APC/CyberPower HID 0.9

01:05 wahoo:../eol.svn/trunk # upsc myups@localhost battery.charge: 100 battery.charge.low: 10 battery.charge.warning: 50 battery.date: 2001/09/25 battery.mfr.date: 2008/02/19 battery.runtime: 510 battery.runtime.low: 120 battery.type: PbAc battery.voltage: 13.7 battery.voltage.nominal: 12.0 driver.name: newhidups driver.parameter.port: auto driver.version: 2.0.4 driver.version.data: APC/CyberPower HID 0.9 driver.version.internal: 0.28 input.transfer.high: 139 input.transfer.low: 92 input.voltage: 117.0 input.voltage.nominal: 120 ups.beeper.status: enabled ups.delay.shutdown: -1 ups.firmware: 841.I2 .D ups.firmware.aux: I2 ups.load: 47 ups.mfr: American Power Conversion ups.mfr.date: 2008/02/19 ups.model: Back-UPS ES 750 ups.serial: 3B0808X06916 ups.status: OL ups.test.result: No test initiated

/etc/ups/ups.conf [myups] driver = newhidups port = auto desc = "Local UPS"

Check man newhidups and see if it needs the vendorid like the present one does. That would seem to me to help it find the device easier.

what do I do to give user 'ups' access to port 'auto' rather than starting as user 'root'? /usr/lib/ups/driver/upsdrvctl -u root

since I want to auto start via init.d.

Since you mentioned you are running 10.1 still, that is harder to help with. I would say you should create a udev rule file to find your ups and give the appropriate permission to the port for ups user. In the startup script upsd in my /etc/init.d, it has a listed variable UPSD_USER, which is set by default to upsd, but it also has a UPS_OWNER variable to control ups port permissions (default is $UPSD_USER:root). In the 2.2.1 package, it has a udev rule file, to help you perhaps though the udev has changed quite a bit since 10.1, it contains: 52_nut-usbups.rules ---------------------- # udev rules for the NUT USB drivers ACTION!="add", GOTO="nut-usbups_rules_end" SUBSYSTEM=="usb_device", GOTO="nut-usbups_rules_real" SUBSYSTEM=="usb", GOTO="nut-usbups_rules_real" BUS!="usb", GOTO="nut-usbups_rules_end" LABEL="nut-usbups_rules_real" # MGE UPS SYSTEMS - usbhid-ups SYSFS{idVendor}=="0463", SYSFS{idProduct}=="ffff", MODE="664", GROUP="daemon" SYSFS{idVendor}=="0463", SYSFS{idProduct}=="0001", MODE="664", GROUP="daemon" # APC - usbhid-ups SYSFS{idVendor}=="051d", SYSFS{idProduct}=="0002", MODE="664", GROUP="daemon" # CyberPower - usbhid-ups SYSFS{idVendor}=="0764", SYSFS{idProduct}=="0005", MODE="664", GROUP="daemon" SYSFS{idVendor}=="0764", SYSFS{idProduct}=="0501", MODE="664", GROUP="daemon" # Mustek Powermust 600USB (OMRON/87XXUPS) SYSFS{idVendor}=="06da", SYSFS{idProduct}=="0003", MODE="664", GROUP="daemon" # LIEBERT/PowerSure Personal XT SYSFS{idVendor}=="06da", SYSFS{idProduct}=="ffff", MODE="664", GROUP="daemon" # Cypress Semiconductor USB to Serial SYSFS{idVendor}=="0665", SYSFS{idProduct}=="5161", MODE="664", GROUP="daemon" # Powercom - unknown driver SYSFS{idVendor}=="0d9f", SYSFS{idProduct}=="0001", MODE="664", GROUP="daemon" SYSFS{idVendor}=="0d9f", SYSFS{idProduct}=="0002", MODE="664", GROUP="daemon" # Agiler - megatec_usb SYSFS{idVendor}=="05b8", SYSFS{idProduct}=="0000", MODE="664", GROUP="daemon" # Krauler - megatec_usb SYSFS{idVendor}=="0001", SYSFS{idProduct}=="0000", MODE="664", GROUP="daemon" # Ablerex - megatec_usb SYSFS{idVendor}=="ffff", SYSFS{idProduct}=="0000", MODE="664", GROUP="daemon" # Powerware - bcmxcp_usb SYSFS{idVendor}=="0592", SYSFS{idProduct}=="0002", MODE="664", GROUP="daemon" # Tripp Lite - tripplite_usb SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="0001", MODE="664", GROUP="daemon" # Tripp Lite - usbhid-ups SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="1003", MODE="664", GROUP="daemon" SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="2005", MODE="664", GROUP="daemon" SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="2007", MODE="664", GROUP="daemon" SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="3012", MODE="664", GROUP="daemon" SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="4002", MODE="664", GROUP="daemon" SYSFS{idVendor}=="09ae", SYSFS{idProduct}=="4003", MODE="664", GROUP="daemon" # Belkin - usbhid-ups SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0980", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0900", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0910", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0912", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0551", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0751", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="0375", MODE="664", GROUP="daemon" SYSFS{idVendor}=="050d", SYSFS{idProduct}=="1100", MODE="664", GROUP="daemon" # Kebo - unsupported SYSFS{idVendor}=="0925", SYSFS{idProduct}=="1234", MODE="664", GROUP="daemon" LABEL="nut-usbups_rules_end" Of course, you would only HAVE to have the APC lines.

also, I'm having problems setting the password for upscmd ??

thanks much,

If it would work, I would see if the 10.2 package from http://download.opensuse.org/repositories/home:/sbrabec:/backports/openSUSE_... would work in your 10.1, as nut has improved quite a bit over the last few years. -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On 06/16/2008 09:33 PM, Patrick Shanahan wrote:

Thanks again for your assistance and any enlightenment you might have about the password issue.

tks

Not sure what problem you are having with the password, but here are a few things to check, though versions are different so things may not match. upsd.conf handles Access Control. You need ACL localhost 127.0.0.1/32 Accept localhost (before Reject all) upsd.users should have [upsmaster] password = (your password) allowfrom = localhost upsmon master upsmon.conf should have a line MONITOR myups@localhost 1 upsmaster (your password from upsd.users) master HTH -- Joe Morris Registered Linux user 231871 running openSUSE 10.3 x86_64 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

On Saturday 14 June 2008 06:57:53 pm Patrick Shanahan wrote:

* Carlos E. R. [06-14-08 19:52]:

...

The Saturday 2008-06-14 at 19:36 -0400, Patrick Shanahan wrote:

...

...

hwinfo --usb should give you devices

yes, but not the port, at least that I understand:

Then try lsusb

Bus 002 Device 004: ID 051d:0002 American Power Conversion Back-UPS Pro 500/1000/1500

?? I still do not understand /dev/????? which is requested by uspd in /etc/ups/ups.conf

The device is not yet configured, that is why 'hwinfo' is missing /dev/ part. Check udev rules, is there any word about UPS. See the web has anyone created such rules. -- Regards, Rajko http://en.opensuse.org/Portal needs helpful hands. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-06-17 at 08:51 +0200, Koenraad Lelong wrote:

I have been following this tread and I was wondering why you are not using apcupsd. I have installed it recently and it works fine. I used a serial port though. I had troubles before with USB-ups'es and NUT : when there was a longer power-outage the PC's went down OK, but the last step is signalling the UPS to shutdown also, but at that moment there was no USB-functionality on the controlling PC. So the UPS stayed up, completely draining the battery, which is not so good for it. Or the server didn't know the power was back if it came back before the UPS was spent. This was a few years ago though. Maybe NUT is better now. Just some thoughts.

Maybe what you describe is a hardware design fault. The UPS has to be programmed to poweroff by itself perhaps a minute after the PC has powered off. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIV5WMtTMYHG2NR9URAu42AJ4hRabQne8A0goC8RqUXtf68fxasgCfbbKs HQUcSBk+Pva6TCL5xfF4ywQ= =fsyX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org