[Nut-upsuser] new nut install from debian bullseye repo doesn't run

[gene heskett]

Greetings nut-users;

I had an interesting 8 past months, loseing my amandatapes drive,
then my boot drive 2 weeks later.

Identical 2T Seacrate drives. I have a good idea what caused it,
but suffice to say, all 6 drives in this machine are now Samsung
SSD's 4 of them split between a huge raid10 /home, and 65G as
swap as that is 2x the memory. This a maddening situation for me.
I lost 23 years of history when those drives puked.

And as I have no backups I haven't a clue how to configure nut
from scratch. And at 87 yo, I'm not as sharp as I was 65 years
ago. I've survived a pulmonary embolism, somethings less than 2%
of us do.

So, since there are no man pages installed, where can I find the
docs that will guide me in configuring it from a blank slate?

The ups is an apc which ID's itself via lsusb -v as:

   iManufacturer           1 American Power Conversion
   iProduct                2 Smart-UPS_1500 FW:UPS 03.5 / ID=1015
   iSerial                 3 3S1906X11389

And about all I can recall is that its "myups" using the
driver usbhid-ups.

I have added nut to group:dialout, and changed /dev/ttyUSB1's grp
to nut. Restarting both looks like the server is ok, but the client
is not according to the syslog:
Jun 17 17:23:57 coyote systemd[1]: Starting Network UPS Tools - power 
device driver controller...
Jun 17 17:23:59 coyote upsdrvctl[118382]: interrupt pipe disabled (add 
'pollonly' flag to 'ups.conf' to get rid of this message)
Jun 17 17:23:59 coyote upsdrvctl[118382]: Using subdriver: APC HID 0.96
Jun 17 17:23:59 coyote upsdrvctl[118382]: Network UPS Tools - Generic 
HID driver 0.41 (2.7.4)
Jun 17 17:23:59 coyote upsdrvctl[118382]: USB communication driver 0.33
Jun 17 17:23:59 coyote usbhid-ups[118386]: Startup successful
Jun 17 17:23:59 coyote upsdrvctl[118381]: Network UPS Tools - UPS driver 
controller 2.7.4
Jun 17 17:23:59 coyote systemd[1]: Started Network UPS Tools - power 
device driver controller.
Jun 17 17:23:59 coyote systemd[1]: Starting Network UPS Tools - power 
devices information server...
Jun 17 17:23:59 coyote upsd[118387]: fopen /run/nut/upsd.pid: No such 
file or directory
Jun 17 17:23:59 coyote upsd[118387]: listening on 127.0.0.1 port 3493
Jun 17 17:23:59 coyote upsd[118387]: listening on 127.0.0.1 port 3493
Jun 17 17:23:59 coyote upsd[118387]: Connected to UPS [myups]: 
usbhid-ups-myups
Jun 17 17:23:59 coyote upsd[118387]: Connected to UPS [myups]: 
usbhid-ups-myups
Jun 17 17:23:59 coyote upsd[118388]: Startup successful
Jun 17 17:23:59 coyote systemd[1]: Started Network UPS Tools - power 
devices information server.
Jun 17 17:25:32 coyote systemd[1]: Starting Network UPS Tools - power 
device monitor and shutdown controller...
Jun 17 17:25:32 coyote upsmon[118447]: Startup successful
Jun 17 17:25:32 coyote systemd[1]: nut-monitor.service: Can't open PID 
file /run/nut/upsmon.pid (yet?) after start: Operation not permitted
Jun 17 17:25:32 coyote upsmon[118446]: fopen /run/nut/upsmon.pid: No 
such file or directory
Jun 17 17:25:32 coyote upsmon[118446]: UPS: myups at localhost (master) 
(power value 1)
Jun 17 17:25:32 coyote upsmon[118446]: Using power down flag file 
/etc/killpower
Jun 17 17:25:32 coyote upsmon[118446]: /etc/nut/upsmon.conf line 234: 
invalid directive REPLBATT : The UPS battery is bad and needs to be replaced
Jun 17 17:25:32 coyote upsmon[118446]: /etc/nut/upsmon.conf line 260: 
invalid directive WALL - Write the message to all users on the system
Jun 17 17:25:32 coyote systemd[1]: nut-monitor.service: Supervising 
process 118448 which is not our child. We'll most likely not notice when 
it exits.
Jun 17 17:25:32 coyote systemd[1]: Started Network UPS Tools - power 
device monitor and shutdown controller.
Jun 17 17:25:32 coyote upsmon[118448]: Init SSL without certificate database
Jun 17 17:25:32 coyote upsmon[118448]: Login on UPS [myups at localhost] 
failed - got [ERR ACCESS-DENIED]

However, going to a shell as me, and calling upsc myups, does get me data:
gene at coyote:~$ 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.5
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

I have a 20kw standby whose time from failure to usable power is around 
17 seconds,
but the front panel of this ups is now telling me it needs a fresh 
battery, and it
is about 3 years old. But all it has to do is run me for 20 seconds. 
Pointer to
config docs would be most appreciated.

What else do I need to do?

Take care & stay well everybody.

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