Nut upsuser - Jan 2021 - New User Questions (again) - With Belkin USB

An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210122/5abbdd5d/attachment.html>

On 1/23/21 12:38 AM, David White via Nut-upsuser wrote:
> Hello. I am having troubles with using nut on my new system (Ubuntu 
> 1.4 on kernel 4.9 chroot'ed on Android). I have this working on an 
> earlier system (Ubuntu 1.4 on kernel 3.x also chroot'ed on Android). 
> My UPS is a Belkin with USB interface. As a newbie, I have no idea 
> what is wrong here. I have supplied all the info I can get my hands on 
> right now below.
>
> Thanks for any help/tips you can supply.
>
> 1. sudo upsdrvctl start yields:
>
>     Network UPS Tools - UPS driver controller 2.7.1
>     Network UPS Tools - Megatec/Q1 protocol USB driver 0.10 (2.7.1)
>     No supported devices found. Please check your device availability
>     with 'lsusb'
>
[...]
>
>
>     Driver failed to start (exit status=1)
>     root at localhost:~#
>
these lines here tell us that the driver cannot find the UPS and by 
matter the consequence, the driver does not start


> 2. upsc belkinusb (or uspc belkinusb at localhost) yields:
>
>     Error: Connection failure: Connection refused
>
this  error is normal and due to the previously reported problem ( 
driver not started )

>
>         ########### Operating system ###########
> 4.9.113 GNU/Linux
> NAME="Ubuntu"
> PRETTY_NAME="Ubuntu 14.04 LTS"
that's quite old, it reached end of life almost 2 years ago. I suggest 
using a newer OS if possible.

>
>         ########### Ownership and permissions of configuration files 
> ###########
> -rwxrwxrwx. 1 root nut  1544 Jan 21 11:52 /etc/nut/nut.conf*
> -rwxrwxrwx. 1 root nut  4653 Jan 21 18:29 /etc/nut/ups.conf*
> -rwxrwxrwx. 1 root nut  4572 Jan 21 11:52 /etc/nut/upsd.conf*
> -rwxrwxrwx. 1 root nut  2206 Jan 21 11:52 /etc/nut/upsd.users*
> -rwxrwxrwx. 1 root nut 15274 Jan 21 12:23 /etc/nut/upsmon.conf*
> -rwxrwxrwx. 1 root nut  3887 Jan 21 11:52 /etc/nut/upssched.conf*
777 is never a good idea. never ever, except for limited testing 
environments. correct mode for all these files is 640


>
>         ########### nut-journal ###########
> root at localhost:/storage/emulated/0#
>
> 4. lsusb shows the UPS on Bus 001, Device 003 (cypress USB to Serial)
>
>     Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc.
>     Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>     Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
>     Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics HL-340
>     USB-Serial adapter
>     Bus 001 Device 003: ID 0665:5161 Cypress Semiconductor USB to Serial
>     Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub
>     Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>     root at localhost:/storage#
>
Check in the system logs ( |/var/log/messages* ||) if a /dev/*USB* gets 
created by the usb-to-serial interface. You should see something similar to
|

|/var/log/messages.1:Jan 12 02:17:18 pi kernel: [ 20.554591] usbserial: 
USB Serial support registered for generic
/var/log/messages.1:Jan 12 02:17:18 pi kernel: [   20.671305] usbserial: 
USB Serial support registered for pl2303
/var/log/messages.1:Jan 12 02:17:18 pi kernel: [   20.729145] usb 1-1.2: 
pl2303 converter now attached to ttyUSB0

|

|
|

|If there is no such message, try disconnecting and reconnecting the 
adapter. If still not, you have a problem with the drivers for the 
adapter, the kernel does not create the interface needed to access it 
and you will have too resolve this issue first.|

|If /dev/ttyUSB0 or similar exists, you have permission problems - 
blazer_usb is not allowed to access it|


wolfy

-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20210123/2d5790b8/attachment-0001.html>

On Jan 22, 2021, at 5:38 PM, David White via Nut-upsuser <nut-upsuser at
alioth-lists.debian.net> wrote:
> 
> 4. lsusb shows the UPS on Bus 001, Device 003 (cypress USB to Serial)
> Bus 002 Device 002: ID 05e3:0612 Genesys Logic, Inc.
> Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
> Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver
> Bus 001 Device 004: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial
adapter
> Bus 001 Device 003: ID 0665:5161 Cypress Semiconductor USB to Serial
David,

is this the same system as mentioned in this thread?
https://alioth-lists.debian.net/pipermail/nut-upsuser/2020-January/011619.html

While wolfy's suggestions are applicable for a serial UPS with an external
USB-to-serial adapter, it sounds like your Belkin UPS has the Cypress chip
built-in, and the blazer_usb driver expects to talk directly to that chip
(bypassing any kernel drivers that create /dev/ttyUSB* nodes).

Changing the config file modes from 777 to 640 is likely orthogonal to the
problem, but something I'd want to fix sooner than later.

What does `ls -l /dev/bus/usb/001/003` show?

You can also try starting the driver manually. There are easier ways to do this
in newer versions of NUT, but with 2.7.1 and an Ubuntu-like filesystem layout,
it would be something like this (assuming the UPS name is still belkinusb in
/etc/nut/ups.conf):

/lib/nut/blazer_usb -a belkinusb -DD

-- 
Charles Lepple
clepple at gmail