Nut upsuser - Nov 2011 - Confusing Generic USB UPS cannot be matched

I was dropping off junk at the waste transfer station and scarfed a UPS 
out of the pile of old TV's and VCR's. It was in good physical condition
and as I expected, the battery was toast. A new RBC-2 battery restored 
it to working condition. Then I tried to get it to talk to some 
software. And I am having no luck.

The unit is branded as a Nexxtech Model 6118507 650VA imported into 
Canada for Orbyx Electronics LLC. Nexxtech is a house brand for 'The 
Source' ex-Radio Shack in Canada.
It has a red LCD display on the front and has the same physical layout 
as some of the smaller APC BackUPS and CyberPower units. However trying 
the powerpanel and APC specific drivers was fruitless.
The unit is 6" high x 4" wide by 12" deep. It has 3 UPS outlets
plus 3
surge protected outlets and a USB port.

I am running Fedora 14 2.6.35.14-96.fc14.x86_64 with 
nut-2.6.2-1.fc14.x86_64.rpm from the Fedora repo

I strongly suspect that this unit was made in China ( by MEC??) and 
branded in various different ways (the 'Fry's Electronics' report is
a
but of a giveaway! especially as there are no Fry's in Canada). A thread 
on this list from 2006 had the same reported data Vendor/Product id but 
a different branding. Unfortunately that thread had no resolution.

Due to the fact that this unit does not seem to report itself correctly 
there is a possibility that it cannot be made 'intelligent'. But I'd
like to try, first.

I have installed nut and done the usual things. The unit is almost 
'there', but not quite. I have trolled through the FAQ and the list but 
nothing (except that one thread) seem to deal with this.

Details:

dmesg
[   13.690421] usb 4-4: New USB device found, idVendor=0001, 
idProduct=0000             #This is clearly bogus, and is what was 
reported in the 2006 thread
[   13.690667] usb 4-4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=0
[   13.690909] usb 4-4: Product: MEC0002
[   13.691164] usb 4-4: Manufacturer: MEC
[   13.722779] generic-usb 0003:0001:0000.0003: hiddev97,hidraw2: USB 
HID v1.00 Device [MEC MEC0002] on usb-0000:00:06.0-4/input0


lsusb -vv
# not much more info than dmesg, and it fails to discover the manufacturer!

Bus 004 Device 002: ID 0001:0000 Fry's Electronics
Device Descriptor:
   bLength                18
   bDescriptorType         1
   bcdUSB               1.00
   bDeviceClass            0 (Defined at Interface level)
   bDeviceSubClass         0
   bDeviceProtocol         0
   bMaxPacketSize0         8
   idVendor           0x0001 Fry's Electronics
   idProduct          0x0000
   bcdDevice            1.00
   iManufacturer           1
   iProduct                2
   iSerial                 0
   bNumConfigurations      1
   Configuration Descriptor:
     bLength                 9
     bDescriptorType         2
     wTotalLength           34
     bNumInterfaces          1
     bConfigurationValue     1
     iConfiguration          0
     bmAttributes         0x80
       (Bus Powered)
     MaxPower              100mA
     Interface Descriptor:
       bLength                 9
       bDescriptorType         4
       bInterfaceNumber        0
       bAlternateSetting       0
       bNumEndpoints           1
       bInterfaceClass         3 Human Interface Device
       bInterfaceSubClass      0 No Subclass
       bInterfaceProtocol      0 None
       iInterface              0
         HID Device Descriptor:
           bLength                 9
           bDescriptorType        33
           bcdHID               1.00
           bCountryCode            0 Not supported
           bNumDescriptors         1
           bDescriptorType        34 Report
           wDescriptorLength     624
          Report Descriptors:
            ** UNAVAILABLE **
       Endpoint Descriptor:
         bLength                 7
         bDescriptorType         5
         bEndpointAddress     0x81  EP 1 IN
         bmAttributes            3
           Transfer Type            Interrupt
           Synch Type               None
         Package Type               Data
         wMaxPacketSize     0x0008  1x 8 bytes
         bInterval              10
Device Status:     0x0000
   (Bus Powered)


Check on the install by restarting the daemon:
It's all down to the driver.

# service ups restart
Stopping UPS monitor:                                      [  OK  ]
Stopping upsd:                                             [  OK  ]
Shutting down UPS driver controller:                       [FAILED]
Starting UPS driver controller:                            [FAILED]
Starting upsd:                                             [  OK  ]
Starting UPS monitor:                                      [  OK  ]

Using usbhid-ups  (tried others, without result)


# cat ups.conf
<snip>
  [nexxtech]
         driver = usbhid-ups
         vendorid = 0001
         productid = 0000
         port = /dev/bus/usb/004/004
#       port = AUTO 		#per the documentation these made
#       port = /dev/usb/hiddev0 # no difference
         desc = "Nexxtech UPS"



Made sure the user/group settings are correct.
# cat upsd.user
<snip>
         [nut]
                 password = nutpass
                 upsmon master

# cat upsmon.conf
<snip>
MONITOR nexxtech at localhost 1 nut nutpass master
<snip>


And this is what I get for my pains (same with user 'nut'):

# usbhid-ups -DD -u root -x vendorid=0001 -a nexxtech
Network UPS Tools - Generic HID driver 0.35 (2.6.2)
USB communication driver 0.31
    0.000000     debug level is '2'
    0.001663     upsdrv_initups...
    0.084295     Checking device (0001/0000) (004/004)
    2.088358     - VendorID: 0001
    2.088416     - ProductID: 0000
    2.088442     - Manufacturer: unknown
    2.088467     - Product: unknown
    2.088491     - Serial Number: unknown
    2.088516     - Bus: 004
    2.088541     Trying to match device
    2.088614     Device does not match - skipping

I have NO idea why the Device does not match... but then I am not sure 
what is is attempting to match. The installation is fine: upsd reports 
periodically that it cannot communicate with the unit..


So what is the driver trying to match against? And can I amend any 
settings to make it match? Can I provide any more info.

Geoff


-- 
              R. Geoffrey Newbury			
            Barrister and Solicitor
       Suite 106, 150 Lakeshore Road West
          Mississauga, Ontario, L5H 3R2

         o905-271-9600 f905-271-1638
           newbury at mandamus.org

Hi Geoff,

2011/11/21 R. G. Newbury <newbury at
mandamus.org>:
> I was dropping off junk at the waste transfer station and scarfed a UPS out
> of the pile of old TV's and VCR's. It was in good physical
condition and as
> I expected, the battery was toast. A new RBC-2 battery restored it to
> working condition. Then I tried to get it to talk to some software. And I
am
> having no luck.
>
> The unit is branded as a Nexxtech Model 6118507 650VA imported into Canada
> for Orbyx Electronics LLC. Nexxtech is a house brand for 'The
Source'
> ex-Radio Shack in Canada.
> It has a red LCD display on the front and has the same physical layout as
> some of the smaller APC BackUPS and CyberPower units. However trying the
> powerpanel and APC specific drivers was fruitless.
> The unit is 6" high x 4" wide by 12" deep. It has 3 UPS
outlets plus 3 surge
> protected outlets and a USB port.
>
> I am running Fedora 14 2.6.35.14-96.fc14.x86_64 with
> nut-2.6.2-1.fc14.x86_64.rpm from the Fedora repo
>
> I strongly suspect that this unit was made in China ( by MEC??) and branded
> in various different ways (the 'Fry's Electronics' report is a
but of a
> giveaway! especially as there are no Fry's in Canada). A thread on this
list
> from 2006 had the same reported data Vendor/Product id but a different
> branding. Unfortunately that thread had no resolution.
>
> Due to the fact that this unit does not seem to report itself correctly
> there is a possibility that it cannot be made 'intelligent'. But
I'd like to
> try, first.
>
> I have installed nut and done the usual things. The unit is almost
'there',
> but not quite. I have trolled through the FAQ and the list but nothing
> (except that one thread) seem to deal with this.
>
> Details:
>
> dmesg
> [ ? 13.690421] usb 4-4: New USB device found, idVendor=0001, idProduct=0000
> ? ? ? ? ? ? #This is clearly bogus, and is what was reported in the 2006
> thread
> [ ? 13.690667] usb 4-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [ ? 13.690909] usb 4-4: Product: MEC0002
> [ ? 13.691164] usb 4-4: Manufacturer: MEC
> [ ? 13.722779] generic-usb 0003:0001:0000.0003: hiddev97,hidraw2: USB HID
> v1.00 Device [MEC MEC0002] on usb-0000:00:06.0-4/input0
>
>
> lsusb -vv
> # not much more info than dmesg, and it fails to discover the manufacturer!
>
> Bus 004 Device 002: ID 0001:0000 Fry's Electronics
> Device Descriptor:
> ?bLength ? ? ? ? ? ? ? ?18
> ?bDescriptorType ? ? ? ? 1
> ?bcdUSB ? ? ? ? ? ? ? 1.00
> ?bDeviceClass ? ? ? ? ? ?0 (Defined at Interface level)
> ?bDeviceSubClass ? ? ? ? 0
> ?bDeviceProtocol ? ? ? ? 0
> ?bMaxPacketSize0 ? ? ? ? 8
> ?idVendor ? ? ? ? ? 0x0001 Fry's Electronics
> ?idProduct ? ? ? ? ?0x0000
> ?bcdDevice ? ? ? ? ? ?1.00
> ?iManufacturer ? ? ? ? ? 1
> ?iProduct ? ? ? ? ? ? ? ?2
> ?iSerial ? ? ? ? ? ? ? ? 0
> ?bNumConfigurations ? ? ?1
> ?Configuration Descriptor:
> ? ?bLength ? ? ? ? ? ? ? ? 9
> ? ?bDescriptorType ? ? ? ? 2
> ? ?wTotalLength ? ? ? ? ? 34
> ? ?bNumInterfaces ? ? ? ? ?1
> ? ?bConfigurationValue ? ? 1
> ? ?iConfiguration ? ? ? ? ?0
> ? ?bmAttributes ? ? ? ? 0x80
> ? ? ?(Bus Powered)
> ? ?MaxPower ? ? ? ? ? ? ?100mA
> ? ?Interface Descriptor:
> ? ? ?bLength ? ? ? ? ? ? ? ? 9
> ? ? ?bDescriptorType ? ? ? ? 4
> ? ? ?bInterfaceNumber ? ? ? ?0
> ? ? ?bAlternateSetting ? ? ? 0
> ? ? ?bNumEndpoints ? ? ? ? ? 1
> ? ? ?bInterfaceClass ? ? ? ? 3 Human Interface Device
> ? ? ?bInterfaceSubClass ? ? ?0 No Subclass
> ? ? ?bInterfaceProtocol ? ? ?0 None
> ? ? ?iInterface ? ? ? ? ? ? ?0
> ? ? ? ?HID Device Descriptor:
> ? ? ? ? ?bLength ? ? ? ? ? ? ? ? 9
> ? ? ? ? ?bDescriptorType ? ? ? ?33
> ? ? ? ? ?bcdHID ? ? ? ? ? ? ? 1.00
> ? ? ? ? ?bCountryCode ? ? ? ? ? ?0 Not supported
> ? ? ? ? ?bNumDescriptors ? ? ? ? 1
> ? ? ? ? ?bDescriptorType ? ? ? ?34 Report
> ? ? ? ? ?wDescriptorLength ? ? 624
> ? ? ? ? Report Descriptors:
> ? ? ? ? ? ** UNAVAILABLE **
> ? ? ?Endpoint Descriptor:
> ? ? ? ?bLength ? ? ? ? ? ? ? ? 7
> ? ? ? ?bDescriptorType ? ? ? ? 5
> ? ? ? ?bEndpointAddress ? ? 0x81 ?EP 1 IN
> ? ? ? ?bmAttributes ? ? ? ? ? ?3
> ? ? ? ? ?Transfer Type ? ? ? ? ? ?Interrupt
> ? ? ? ? ?Synch Type ? ? ? ? ? ? ? None
> ? ? ? ?Package Type ? ? ? ? ? ? ? Data
> ? ? ? ?wMaxPacketSize ? ? 0x0008 ?1x 8 bytes
> ? ? ? ?bInterval ? ? ? ? ? ? ?10
> Device Status: ? ? 0x0000
> ?(Bus Powered)
>
>
> Check on the install by restarting the daemon:
> It's all down to the driver.
>
> # service ups restart
> Stopping UPS monitor: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[ ?OK ?]
> Stopping upsd: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? [ ?OK ?]
> Shutting down UPS driver controller: ? ? ? ? ? ? ? ? ? ? ? [FAILED]
> Starting UPS driver controller: ? ? ? ? ? ? ? ? ? ? ? ? ? ?[FAILED]
> Starting upsd: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? [ ?OK ?]
> Starting UPS monitor: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[ ?OK ?]
>
> Using usbhid-ups ?(tried others, without result)
>
>
> # cat ups.conf
> <snip>
> ?[nexxtech]
> ? ? ? ?driver = usbhid-ups
> ? ? ? ?vendorid = 0001
> ? ? ? ?productid = 0000
> ? ? ? ?port = /dev/bus/usb/004/004
> # ? ? ? port = AUTO ? ? ? ? ? ? #per the documentation these made
> # ? ? ? port = /dev/usb/hiddev0 # no difference
> ? ? ? ?desc = "Nexxtech UPS"
>
>
>
> Made sure the user/group settings are correct.
> # cat upsd.user
> <snip>
> ? ? ? ?[nut]
> ? ? ? ? ? ? ? ?password = nutpass
> ? ? ? ? ? ? ? ?upsmon master
>
> # cat upsmon.conf
> <snip>
> MONITOR nexxtech at localhost 1 nut nutpass master
> <snip>
>
>
> And this is what I get for my pains (same with user 'nut'):
>
> # usbhid-ups -DD -u root -x vendorid=0001 -a nexxtech
> Network UPS Tools - Generic HID driver 0.35 (2.6.2)
> USB communication driver 0.31
> ? 0.000000 ? ? debug level is '2'
> ? 0.001663 ? ? upsdrv_initups...
> ? 0.084295 ? ? Checking device (0001/0000) (004/004)
> ? 2.088358 ? ? - VendorID: 0001
> ? 2.088416 ? ? - ProductID: 0000
> ? 2.088442 ? ? - Manufacturer: unknown
> ? 2.088467 ? ? - Product: unknown
> ? 2.088491 ? ? - Serial Number: unknown
> ? 2.088516 ? ? - Bus: 004
> ? 2.088541 ? ? Trying to match device
> ? 2.088614 ? ? Device does not match - skipping
>
> I have NO idea why the Device does not match... but then I am not sure what
> is is attempting to match. The installation is fine: upsd reports
> periodically that it cannot communicate with the unit..
>
>
> So what is the driver trying to match against? And can I amend any settings
> to make it match? Can I provide any more info.
as per your info (VID:PID), your device is not HID compliant and the
driver should be blazer_usb.
"port = auto" is still needed, though you can put any value you want
(field not considered).

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/

On Nov 23, 2011, at 10:13 AM, R. G. Newbury wrote:
> On 11/22/2011 07:42 PM, Charles Lepple wrote:
> 
>>> [root at tor2 ups]# upscmd -u nut -p nutpass nexxtech beeper.toggle
>>> Unexpected response from upsd: ERR ACCESS-DENIED
>>> 
>>> And using nut at 127.0.0.1 or nut at localhost gives the same
result (even though upsd reports to syslog that nut at 127.0.0.1 is logged into
UPS [nexxtech]
>>> 
> 
>> The system 'nut' user can have its password locked - upsd
won't consult /etc/passwd for passwords, just for username->uid lookups.
>> 
>> I wonder if there is an extra copy of upsd floating around that is
using an old upsd.users file. (Usually it complains that it can't bind to
the port, but stranger things have happened.)
> 
> No. I did a full system find and the only upsd is in /usr/sbin and the only
*.conf files are in /etc/ups.
I didn't mean to imply there was a second upsd binary on the filesystem -
only an extra copy of upsd in memory. It only reads the password file at
startup, or after a SIGHUP:

http://www.networkupstools.org/docs/man/upsd.html#_reloading
>> The reason I mention this is that usually there are only two copies of
upsmon: one still running as root to call the shutdown command, and one running
unprivileged to talk to upsd. They often have similar PIDs (note that the first
two differ by one, as do the last two) since upsmon forks early.
> 
> So I added killall upsd upsmon blazer_usb to the bottom of the
'stop' stanza in /etc/rc.d/init.d/ups and did a 'service restart
ups'
> 
> As expected, none of those were actually killed, having already been
removed. The four instances must have been from my playing around, running the
program from the console and (improperly) not using 'service'.
> 
> After the restart ps shows that I have blazer_sub, upsd, upsmon, upsmon as
the last threads.
> 
> But I still get the access error from upscmd.
> I tried 'root' (although there was no 'root' user in
upsd.users.
> 
> [root at tor2 init.d]# upscmd  nexxtech beeper.toggle
> Username (root):
> Password:		# No password entered
> Unexpected response from upsd: ERR PASSWORD-REQUIRED
> [root at tor2 init.d]# upscmd  nexxtech beeper.toggle
> Username (root):
> Password:		# Usual root password entered
> Unexpected response from upsd: ERR ACCESS-DENIED
Expected.
> [root at tor2 ups]# vim upsd.users
> 
> Added user [root] stanza with password nutpass
Like so?

[root]
	password = nutpass

(The equals sign is required)
> Any further thoughts? I don't (yet) have the source for upsd but it
would be interesting to see exactly *what* upsd looks at/for when it checks the
user.
http://trac.networkupstools.org/projects/nut/browser/trunk/server/upsd.c#L396

http://trac.networkupstools.org/projects/nut/browser/trunk/server/user.c#L277
> Geoff
> 
> PS. I note that upsc believes that the device manufacture is NEXXTECH not
MEC.
> 
> Maybe this unit should be listed in teh Hardware List.
Please see the "Report new devices..." section here:

http://www.networkupstools.org/stable-hcl.html#footnotes

2011/12/1 R. G. Newbury <newbury at mandamus.org>:
> On 11/30/2011 04:08 AM, Arnaud Quette wrote:
>
>>>>> Anything else in syslog? What if you enable *.debug from
syslog?
>>>>>
>>>>> Also, I am not familiar with the options that Fedora uses
to build the
>>>>> NUT RPMs. It could be something to do with tcp_wrappers,
although I would
>>>>> have expected a syslog message to that effect.
>>>>
>>>>
>>
>> check that nut udev script (nut/scripts/udev/...rules) is installed on
>> your system, to address device permissions.
>> setting manually won't work, because of device name increment.
>>
>> next, post your ups.conf, upsd.{conf,users} and upsmon.conf (trimmed
>> of password!) for analysis.
>>
>> cheers,
>> Arnaud
>
>
> Arnaud,
>
> I have spent another couple of hours messing with this...... and no great
> progress. In order to avoid any tcp_wrapper error I added ALL: ALL to
> /etc/hosts.allow ?(Yes, to be revised later!)
>
>
> Here is the information you requested. Since it is rather large I did not
> copy to the list..
it's always a bad idea to not copy the list!
> I include the steps I took along the way. FYI, the unit
> does seem to work properly, but does not seem to honour the settings. I
> pulled the wall plug, and expected a shutdown in 30 minutes. It ran (and
> BEEPED!!! throughout) for just under an hour with this computer attached.
> The computer is an Asus mini-ITX Atom/ION DualCore 330 motherboard and
pulls
> probably somewhere around 30 Watts, so an hour is good. It then shutdown
> cleanly as expected. Obviously, this will be a good UPS for my Zotac ION
> VOIP computer running Trixbox (Asterisk) on CentOS, and the routers.
> Interestingly, it did not wait when I replugged the power, and the computer
> booted instantly.
>
> But I cannot actually control it....
>
>
> Nut was installed using yum from Fedora 14 repos. There were NO udev rules
> added to /etc/udev/rules.d
> Clearly this is a problem with the SPEC file and POST-INSTALL procedures.
> This should be checked for the Fedora 15 and 16 repo rpm's as well.
> I copied the nut-usbups.rules (etc) files from the nut tarball. The unit is
> not listed obviously
>
> All testing was done as root, in an attempt to avoid problems.......
>
> Added to nut-usbups.rules
>
> # ?Added by RGNewbury ?(newbury at mandamus.org)
> # ?Fry's Electronics /Nexxtech/MEC ?- blazer_usb
> ATTR{idVendor}=="0001", ATTR{idProduct}=="0000",
MODE="664",
> GROUP="@RUN_AS_GROUP@"
if this is the actual file on your system
({/etc,/lib}/udev/rules/...), @RUN_AS_GROUP@ MUST be replaced by the
actual value of the nut group.
for you "nutty"
> **************************
> Re-triggered udev using udevadmin
>
> #output of lsusb AFTER udev-rules installation and re-trigger of udev:
> Device ID now auto-incrementing as expected
> Bus 004 Device 005: ID 0001:0000 Fry's Electronics
annotating 'Bus 004 Device 005' for latter remark...
> The following have not been changed in about a week...
>
> ***************************
> /etc/ups/ups.conf
>
> ?[nexxtech]
> ? ? ? ?driver = blazer_usb
> # ? ? ? vendorid = 0001
> # ? ? ? productid = 0000
> # ? ? ? port = /dev/bus/usb/004/002
> # ?Not used due to udev port increment rules
> ? ? ? ?port = AUTO
> ? ? ? ?desc = "Nexxtech UPS"
>
> ***************************
> /etc/ups/upsd.users
>
> ? ? ? ?[nutty]
> ? ? ? ? ? ? ? ?password = ***pass
> ? ? ? ? ? ? ? ?upsmon master
>
> ***************************
> /etc/ups/upsmon.conf
> RUN_AS_USER nutty at localhost
> MONITOR nexxtech at localhost 1 nutty at localhost ?***pass master
the user should be 'nutty' without hostname, ie:
MONITOR nexxtech at localhost 1 nutty  ***pass master
> # USER ?nutty and GROUP ?nutty are valid users on the system
don't be fooled by system Vs NUT users.
the ones in upsmon.conf are references to upsd.users.
the same goes for upsrw and upscmd
> ****************************
>
> PERMISSIONS:
> /var/run/nut ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?# Standard
> directory permissions plus group ownership
>
> drwxr-xr-x ?2 root ? ? ?nutty ? ? 1024 Dec ?1 10:26 nut
> /etc/ups
> drwxr-xr-x ? 2 root nutty ? 1024 Dec ?1 10:36 ups ? ? ? ? ? ? ? # Ditto
>
> /etc/ups/*
> drwxr-xr-x ? 2 root nutty ?1024 Dec ?1 10:36 .
> -rw-rw-rw- ? 1 root nutty ?1419 Nov 17 15:22 nut.conf
> -rw-rw-rw- ? 1 root nutty ?3809 Dec ?1 10:26 ups.conf
> -rw-rw-rw- ? 1 root nutty ?2589 Nov 29 13:40 upsd.conf
> -rw-rw-rw- ? 1 root nutty ?2181 Dec ?1 10:34 upsd.users
> -rw-rw-rw- ? 1 root nutty 11956 Dec ?1 10:36 upsmon.conf
> -rw-rw-rw- ? 1 root nutty ?3891 Sep 19 05:37 upssched.conf
>
> /dev/bus/usb/004
> drwxr-xr-x 6 root root ? ? ? 120 Nov 29 17:02 ..
> crw-rw-r-- 1 root nutty 189, 384 Dec ?1 10:25 001
> crw-rw-r-- 1 root root ?189, 388 Dec ?1 10:46 005
as per my annotation, '005' should have 'root nutty'.
'001' is problem a remainder of your manual attempt
> # ? After udev retrigger and re-plug. For later boots see below
>
> ***********************************
>
>
> # service ups start
>
> Starting UPS driver controller: ? ? ? ? ? ? ? ? ? ? ? ? ? ?[FAILED]
> Starting upsd: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? [ ?OK ?]
> Starting UPS monitor: ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?[ ?OK ?]
>
> Darn!
> #blazer_usb -a nexxtech
> Network UPS Tools - Megatec/Q1 protocol USB driver 0.03 (2.6.2)
> writepid: fopen /var/run/nut/blazer_usb-nexxtech.pid: Permission denied
> Can't claim USB device [0001:0000]: could not detach kernel driver from
> interface 0: Operation not permitted
>
> Udev retrigger apparently did not work as expected:
>
> ****************************************
> ? ? ? ? ? ? ? ? ? ? ?RE-BOOT
> ****************************************
>
> from /var/log/messages
>
> Dec ?1 10:53:49 tor2 kernel: [ ? ?3.278065] usb 4-4: new low speed USB
> device using ohci_hcd and address 2
>
> Dec ?1 10:53:49 tor2 kernel: [ ? 13.480046] usb 4-4: New USB device found,
> idVendor=0001, idProduct=0000
> Dec ?1 10:53:49 tor2 kernel: [ ? 13.480287] usb 4-4: New USB device
strings:
> Mfr=1, Product=2, SerialNumber=0
> Dec ?1 10:53:49 tor2 kernel: [ ? 13.480528] usb 4-4: Product: MEC0002
> Dec ?1 10:53:49 tor2 kernel: [ ? 13.480752] usb 4-4: Manufacturer: MEC
>
> Dec ?1 10:54:15 tor2 blazer_usb[2100]: Startup successful
> Dec ?1 10:54:15 tor2 upsd[2102]: /etc/ups/upsd.conf is world readable
> Dec ?1 10:54:15 tor2 upsd[2102]: listening on 127.0.0.1 port 3493
> Dec ?1 10:54:15 tor2 upsd[2102]: listening on ::1 port 3493
> Dec ?1 10:54:15 tor2 upsd[2102]: /var/run/nut is world readable
> Dec ?1 10:54:15 tor2 upsd[2102]: Connected to UPS [nexxtech]:
> blazer_usb-nexxtech
> Dec ?1 10:54:15 tor2 upsd[2102]: /etc/ups/upsd.users is world readable
> Dec ?1 10:54:15 tor2 upsd[2103]: Startup successful
> Dec ?1 10:54:15 tor2 upsmon[2106]: Startup successful
> Dec ?1 10:54:15 tor2 upsd[2103]: User nutty at 127.0.0.1 logged into UPS
> [nexxtech]
>
> NOTE: To ensure that the network setup is stable, the network is restarted
> in /etc/rc.d/rc.local. The services ntpd and ups are started in rc.local
and
> not by using 'chkconfig ups on'
>
>
> from /var/log/boot.log
>
> Starting UPS driver controller: [ OK ]
> Starting upsd: ? ? ? ? ? ? ? ? ?[ OK ]
> Starting UPS monitor: ? ? ? ? ? [ OK ]
>
> ***************************************
>
> # service ups status
> upsmon (pid 2107 2106) is running...
>
> BETTER!
>
>
> # upsc nexxtech
> battery.voltage:13.50
> battery.voltage.nominal:12.0
> beeper.status:disabled
> device.mfr:NEXXTECH
> device.model:6118507
> device.type:ups
> driver.name: blazer_usb
> driver.parameter.pollinterval:2
> driver.parameter.port:AUTO
> driver.version:2.6.2
> driver.version.internal: 0.03
> input.current.nominal:3.0
> input.frequency:60.1
> input.frequency.nominal: 60
> input.voltage: 121.0
> input.voltage.fault: 165.0
> input.voltage.nominal: 115
> output.voltage: 121.0
>
> ups.delay.shutdown: 30
> ups.delay.start: 180
> ups.firmware: VER 1.00UL
> ups.load: 42
>
> ups.mfr: NEXXTECH
> ups.model: 6118507
> ups.productid: 0000
> ups.status: OL
> ups.temperature: 0.0
> ups.type: offline / line interactive
> ups.vendorid: 0001
>
> ************************************
seems my udev rules remark is void...
> # upscmd -l nexxtech
> Instant commands supported on UPS [nexxtech]:
>
> beeper.toggle - Toggle the UPS beeper
> load.off - Turn off the load immediately
> load.on - Turn on the load immediately
> shutdown.return - Turn off the load and return when power is back
> shutdown.stayoff - Turn off the load and remain off
> shutdown.stop - Stop a shutdown in progress
> test.battery.start - Start a battery test
> test.battery.start.deep - Start a deep battery test
> test.battery.start.quick - Start a quick battery test
> test.battery.stop - Stop the battery test
>
>
> # upscmd -u nutty at 127.0.0.1 -p ***pass nexxtech beeper.toggle
>
> Unexpected response from upsd: ERR ACCESS-DENIED
>
> AAAAAAARRRRRGGGGGGHHHHHHH!
as per my above comment, remove "@127.0.0.1", ie:

$ upscmd -u nutty -p ***pass nexxtech beeper.toggle
> On the reboot I saw a udev message flash past about an error referring to
> @RUN_AS_GROUP@
> That message does not appear in /var/log/messages nor in dmesg....
> Strange....
>
> **********************************
>
> AMENDED nut-usbups.rules
>
> # ?Added by RGNewbury ?(newbury at mandamus.org)
> # ?Fry's Electronics /Nexxtech/MEC ?- blazer_usb
> ATTR{idVendor}=="0001", ATTR{idProduct}=="0000",
MODE="664", GROUP="nutty"
confirmed and fixed
> REBOOTED AGAIN
>
> from /var/log/messages
>
> Dec ?1 11:41:44 tor2 blazer_usb[2080]: Startup successful ? ? ? ? ? ? ?#
Yes
> I know these should NOT be world readable!
> Dec ?1 11:41:44 tor2 upsd[2082]: /etc/ups/upsd.conf is world readable
> Dec ?1 11:41:44 tor2 upsd[2082]: listening on 127.0.0.1 port 3493
> Dec ?1 11:41:44 tor2 upsd[2082]: listening on ::1 port 3493
> Dec ?1 11:41:44 tor2 upsd[2082]: /var/run/nut is world readable
> Dec ?1 11:41:44 tor2 upsd[2082]: Connected to UPS [nexxtech]:
> blazer_usb-nexxtech
> Dec ?1 11:41:44 tor2 upsd[2082]: /etc/ups/upsd.users is world readable
> Dec ?1 11:41:44 tor2 upsd[2083]: Startup successful
> Dec ?1 11:41:44 tor2 upsmon[2086]: Startup successful
> Dec ?1 11:41:44 tor2 upsd[2083]: User nutty at 127.0.0.1 logged into UPS
> [nexxtech]
>
> [root at tor2 log]# dmesg | grep udev
> [ ? ?2.127033] udev[104]: starting version 161
> [ ? ?5.286275] udev[398]: starting version 161 ? ? ? ?# No error messages
>
> [root at tor2 log]# dmesg | grep usb
> [ ? ?0.546196] usbcore: registered new interface driver usbfs
> [ ? ?0.547006] usbcore: registered new interface driver hub
> [ ? ?0.547262] usbcore: registered new device driver usb
> [ ? ?1.818882] usbcore: registered new interface driver hiddev
> [ ? ?1.819182] usbcore: registered new interface driver usbhid
> [ ? ?1.819420] usbhid: USB HID core driver
> [ ? ?8.715081] usbcore: registered new interface driver btusb
> [ ? 13.473400] usb 4-4: New USB device found, idVendor=0001, idProduct=0000
> [ ? 13.473640] usb 4-4: New USB device strings: Mfr=1, Product=2,
> SerialNumber=0
> [ ? 13.473881] usb 4-4: Product: MEC0002
> [ ? 13.474123] usb 4-4: Manufacturer: MEC
> [ ? 13.505774] generic-usb 0003:0001:0000.0003: hiddev97,hidraw2: USB HID
> v1.00 Device [MEC MEC0002] on usb-0000:00:06.0-4/input0
> [ ? 44.492226] usb 4-4: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt
> 128 rq 6 len 255 ret -110
> [ ? 45.494192] usb 4-4: usbfs: USBDEVFS_CONTROL failed cmd blazer_usb rqt
> 128 rq 6 len 255 ret -110
>
> ********************************************
>
> AND
>
>
> [root at tor2 log]# upscmd -u nutty at 127.0.0.1 -p ***pass nexxtech
> beeper.toggle
>
> Unexpected response from upsd: ERR ACCESS-DENIED
addressed
> And I am where I was.......Except we can see the usbfs error
> USBDEVFS_CONTROL .....
it happens from time to time, no harm.

cheers,
Arnaud
-- 
Linux / Unix Expert R&D - Eaton - http://powerquality.eaton.com
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://www.debian.org
Free Software Developer - http://arnaud.quette.free.fr/