[Nut-upsuser] Confusing Generic USB UPS cannot be matched

Charles Lepple clepple at gmail.com
Wed Nov 23 00:42:55 UTC 2011

On Nov 22, 2011, at 2:47 PM, R. G. Newbury wrote:

> [root at tor2 ups]# ps -ae | grep upsmon
> 3841 ?        00:00:00 upsmon
> 3842 ?        00:00:00 upsmon
> 4695 ?        00:00:00 upsmon
> 4696 ?        00:00:00 upsmon


> [root at tor2 ups]# upscmd -u nut -p nutpass nexxtech beeper.toggle
> Unexpected response from upsd: ERR ACCESS-DENIED
> And using nut at or nut at localhost gives the same result (even though upsd reports to syslog that nut at is logged into UPS [nexxtech]
> And here I am stuck. THe user and password are correct for the 'nut' user on the system, and in the conf file. upsdrvctl and upsd start as does upsmon. But I cannot seem to actually control the unit with upscmd. upsc returns all sorts of nice info however!!

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.)

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.

Unfortunately, you can't rely on the service command in this case. After trying to shut NUT down normally ("service ups stop"?), try running "killall upsd upsmon blazer_usb", then try starting it up again.

More information about the Nut-upsuser mailing list