Nut upsuser - Jun 2022 - something messed up ttyUSB*

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

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
 
Done, nut-server restarted, log still spitting out:
Jun  1 13:33:11 coyote upsmon[802]: Poll UPS [myups at localhost] failed - 
Driver not connected

at 5 second intervals. beeping at 5 minute intervals

This is a fresh install from the debian repos. So its a "from square
one"
startup. I lost it all back in December 21 when 2 new 2T seagate drives 
puked in the night about 1 week apart, so I'm building a bullseye system 
from scratch. And I'm done with spinning rust, its all SSD's now 
including a raid10 for /home. And its quicker than stink on a striped 
kitty's tail. ;o)> But my memory for all this is fading from oldtimers at
87. I hope you are takeing care and staying well.
> Nut-upsuser mailing list
> Nut-upsuser at alioth-lists.debian.net
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
> .

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

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