[Nut-upsuser] something messed up ttyUSB*

[Jim Klimov]

Another "moderately worst case" scenario is to run the NUT driver as root
(with the option in its ups.conf section), at least that helps for ruling
out this permissions sort of issues vs. other moving parts.

Note that generally USB device numbers are not "bolted" and depend on
enumeration order as you boot or hot-plug things, so a ttyUSB1 of today
might be another number after some reboots. That's why NUT has "port=auto"
for USB connections, does not rely on devfs path names, and uses other
identifiers (vendor, product, serial number...) to see a specific device.
Vendors whose serial is always empty or zeroes seem very helpful in that
endeavour when you have more than one UPS ;)

Jim

On Thu, Jun 2, 2022, 05:29 Tim Dawson <tadawson at tpcsvc.com> wrote:

> Either adjust the udev rules to create the tty devices with the desired
> owner/perm, or add the nut user to the appropriate group to have access to
> the device . . .Worst case, you can "brute force" by putting your chmod in
> rc.local so it resets at boot (but that is pretty gross as solutions go . .
> .)
>
> - Tim
>
> On June 1, 2022 9:36:51 PM CDT, gene heskett <gheskett at shentel.net> wrote:
>>
>> On Wednesday, 1 June 2022 13:25:06 EDT Manuel Wolfshant wrote:
>>
>>> On 6/1/22 20:16, gene heskett wrote:
>>>
>>>> Charles;
>>>>
>>>> debian bullseye, all up to date.
>>>>
>>>> I was forced to reboot, x crashed.
>>>>
>>>> When I had rebooted, no ttyUSB stuff worked. I see a reference to
>>>> nut-
>>>> scanner in the doc but the link to its page is busted, typical of the
>>>> nut-doc pages and when I find it, it spits out this:
>>>> [nutdev1]
>>>>
>>>>          driver = "usbhid-ups"
>>>>          port = "auto"
>>>>          vendorid = "051D"
>>>>          productid = "0003"
>>>>          bus = "001"
>>>>
>>>> where do I put what to make it work again?
>>>>
>>>> Cheers, Gene Heskett.
>>>>
>>>
>>> /etc/ups/ups.conf
>>>
>>> I got a more detailed answer from a root session of nut-scanner, and
>> fixed ups.conf with it, and restarted nut, but it made little if any diff
>> that I can see.
>>
>> So I did a sudo lsof|grep "nut " -
>> and got this, more no permissions junk:
>> gene at coyote:/usr/lib$ lsof |grep "nut "  -
>> upsd 78510 nut cwd unknown /proc/78510/cwd (readlink: Permission denied)
>> upsd 78510 nut rtd unknown /proc/78510/root (readlink: Permission denied)
>> upsd 78510 nut txt unknown /proc/78510/exe (readlink: Permission denied)
>> upsd 78510 nut NOFD /proc/78510/fd (opendir: Permission denied)
>> upsmon 78535 nut cwd unknown /proc/78535/cwd (readlink: Permission
>> denied)
>> upsmon 78535 nut rtd unknown /proc/78535/root (readlink: Permission
>> denied)
>> upsmon 78535 nut txt unknown /proc/78535/exe (readlink: Permission
>> denied)
>> upsmon 78535 nut NOFD /proc/78535/fd (opendir: Permission denied)
>>
>> And I just now used a root session of mc to set both /dev/ttyUSB*
>> perm to 777. That lt boty heyu and nut strt throwing errors that made
>> sense, so I fixed those errors and both are now working with one
>> exception, the APC display is saying its due for a fresh battery, but nut
>> isn't saying that from a upsc report:
>> gene at coyote:/etc/nut$ upsc myups
>> Init SSL without certificate database
>> battery.charge: 100
>> battery.charge.low: 10
>> battery.charge.warning: 50
>> battery.runtime: -1
>> battery.runtime.low: 150
>> battery.type: PbAc
>> battery.voltage: 26.1
>> battery.voltage.nominal: 24.0
>> device.mfr: American Power Conversion
>> device.model: Smart-UPS_1500
>> device.serial: 3S1906X11389
>> device.type: ups
>> driver.name: usbhid-ups
>> driver.parameter.bus: 001
>> driver.parameter.pollfreq: 30
>> driver.parameter.pollinterval: 2
>> driver.parameter.port: /dev/ttyUSB1
>> driver.parameter.product: Smart-UPS_1500 FW:UPS 03.5 / ID=1015
>> driver.parameter.productid: 0003
>> driver.parameter.serial: 3S1906X11389
>> driver.parameter.synchronous: no
>> driver.parameter.vendor: American Power Conversion
>> driver.parameter.vendorid: 051D
>> driver.version: 2.7.4
>> driver.version.data: APC HID 0.96
>> driver.version.internal: 0.41
>> ups.beeper.status: enabled
>> ups.delay.shutdown: 20
>> ups.firmware: UPS 03.5 / ID=1015
>> ups.mfr: American Power Conversion
>> ups.mfr.date: 2019/02/06
>> ups.model: Smart-UPS_1500
>> ups.productid: 0003
>> ups.serial: 3S1906X11389
>> ups.status: OL
>> ups.timer.reboot: -1
>> ups.timer.shutdown: 65535
>> ups.vendorid: 051d
>>
>> But what happens when I have to reboot in a few days and /dev gets
>> repopulated with 0600 devices?
>>
>> Thanks Manuel.
>>
>> Take care & stay well
>>
>> Cheers, Gene Heskett.
>> --
>> "There are four boxes to be used in defense of liberty:
>>  soap, ballot, jury, and ammo. Please use in that order."
>> -Ed Howdershelt (Author, 1940)
>> If we desire respect for the law, we must first make the law respectable.
>>  - Louis D. Brandeis
>> ------------------------------
>> Nut-upsuser mailing list
>> Nut-upsuser at alioth-lists.debian.net
>> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>>
>> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
> _______________________________________________
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://alioth-lists.debian.net/pipermail/nut-upsuser/attachments/20220602/ed02713e/attachment-0001.htm>