<div dir="auto">One thing I'd check are the two lines in upsmon.conf it complains about - seems like you had uncommented descriptions of key words instead of setting them up.<div dir="auto"><br></div><div dir="auto">The access denial, that one seems to be a mismatch of login/pass specified in upsmon.conf client and that for the server in upsd.users (may be required to protect on FS to 640 or 600 and proper ownership), possibly some in upsd.conf.</div><div dir="auto"><br></div><div dir="auto">My condolences on the loss of data... can only suggest having occasional offline backups rotated on a shelf, and using different-make (vendor, month) devices in a mirror so their HW flaws do not overlap hopefully. 2T drives surely are under a decade old, so maybe the original older storage you copied from some time back is still out there?</div><div dir="auto"><br></div><div dir="auto">Jim</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Fri, Jun 17, 2022, 23:49 gene heskett <<a href="mailto:gheskett@shentel.net">gheskett@shentel.net</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Greetings nut-users;<br>
<br>
I had an interesting 8 past months, loseing my amandatapes drive,<br>
then my boot drive 2 weeks later.<br>
<br>
Identical 2T Seacrate drives. I have a good idea what caused it,<br>
but suffice to say, all 6 drives in this machine are now Samsung<br>
SSD's 4 of them split between a huge raid10 /home, and 65G as<br>
swap as that is 2x the memory. This a maddening situation for me.<br>
I lost 23 years of history when those drives puked.<br>
<br>
And as I have no backups I haven't a clue how to configure nut<br>
from scratch. And at 87 yo, I'm not as sharp as I was 65 years<br>
ago. I've survived a pulmonary embolism, somethings less than 2%<br>
of us do.<br>
<br>
So, since there are no man pages installed, where can I find the<br>
docs that will guide me in configuring it from a blank slate?<br>
<br>
The ups is an apc which ID's itself via lsusb -v as:<br>
<br>
iManufacturer 1 American Power Conversion<br>
iProduct 2 Smart-UPS_1500 FW:UPS 03.5 / ID=1015<br>
iSerial 3 3S1906X11389<br>
<br>
And about all I can recall is that its "myups" using the<br>
driver usbhid-ups.<br>
<br>
I have added nut to group:dialout, and changed /dev/ttyUSB1's grp<br>
to nut. Restarting both looks like the server is ok, but the client<br>
is not according to the syslog:<br>
Jun 17 17:23:57 coyote systemd[1]: Starting Network UPS Tools - power <br>
device driver controller...<br>
Jun 17 17:23:59 coyote upsdrvctl[118382]: interrupt pipe disabled (add <br>
'pollonly' flag to 'ups.conf' to get rid of this message)<br>
Jun 17 17:23:59 coyote upsdrvctl[118382]: Using subdriver: APC HID 0.96<br>
Jun 17 17:23:59 coyote upsdrvctl[118382]: Network UPS Tools - Generic <br>
HID driver 0.41 (2.7.4)<br>
Jun 17 17:23:59 coyote upsdrvctl[118382]: USB communication driver 0.33<br>
Jun 17 17:23:59 coyote usbhid-ups[118386]: Startup successful<br>
Jun 17 17:23:59 coyote upsdrvctl[118381]: Network UPS Tools - UPS driver <br>
controller 2.7.4<br>
Jun 17 17:23:59 coyote systemd[1]: Started Network UPS Tools - power <br>
device driver controller.<br>
Jun 17 17:23:59 coyote systemd[1]: Starting Network UPS Tools - power <br>
devices information server...<br>
Jun 17 17:23:59 coyote upsd[118387]: fopen /run/nut/upsd.pid: No such <br>
file or directory<br>
Jun 17 17:23:59 coyote upsd[118387]: listening on 127.0.0.1 port 3493<br>
Jun 17 17:23:59 coyote upsd[118387]: listening on 127.0.0.1 port 3493<br>
Jun 17 17:23:59 coyote upsd[118387]: Connected to UPS [myups]: <br>
usbhid-ups-myups<br>
Jun 17 17:23:59 coyote upsd[118387]: Connected to UPS [myups]: <br>
usbhid-ups-myups<br>
Jun 17 17:23:59 coyote upsd[118388]: Startup successful<br>
Jun 17 17:23:59 coyote systemd[1]: Started Network UPS Tools - power <br>
devices information server.<br>
Jun 17 17:25:32 coyote systemd[1]: Starting Network UPS Tools - power <br>
device monitor and shutdown controller...<br>
Jun 17 17:25:32 coyote upsmon[118447]: Startup successful<br>
Jun 17 17:25:32 coyote systemd[1]: nut-monitor.service: Can't open PID <br>
file /run/nut/upsmon.pid (yet?) after start: Operation not permitted<br>
Jun 17 17:25:32 coyote upsmon[118446]: fopen /run/nut/upsmon.pid: No <br>
such file or directory<br>
Jun 17 17:25:32 coyote upsmon[118446]: UPS: myups@localhost (master) <br>
(power value 1)<br>
Jun 17 17:25:32 coyote upsmon[118446]: Using power down flag file <br>
/etc/killpower<br>
Jun 17 17:25:32 coyote upsmon[118446]: /etc/nut/upsmon.conf line 234: <br>
invalid directive REPLBATT : The UPS battery is bad and needs to be replaced<br>
Jun 17 17:25:32 coyote upsmon[118446]: /etc/nut/upsmon.conf line 260: <br>
invalid directive WALL - Write the message to all users on the system<br>
Jun 17 17:25:32 coyote systemd[1]: nut-monitor.service: Supervising <br>
process 118448 which is not our child. We'll most likely not notice when <br>
it exits.<br>
Jun 17 17:25:32 coyote systemd[1]: Started Network UPS Tools - power <br>
device monitor and shutdown controller.<br>
Jun 17 17:25:32 coyote upsmon[118448]: Init SSL without certificate database<br>
Jun 17 17:25:32 coyote upsmon[118448]: Login on UPS [myups@localhost] <br>
failed - got [ERR ACCESS-DENIED]<br>
<br>
However, going to a shell as me, and calling upsc myups, does get me data:<br>
gene@coyote:~$ upsc myups<br>
Init SSL without certificate database<br>
battery.charge: 100<br>
battery.charge.low: 10<br>
battery.charge.warning: 50<br>
battery.runtime: -1<br>
battery.runtime.low: 150<br>
battery.type: PbAc<br>
battery.voltage: 26.5<br>
battery.voltage.nominal: 24.0<br>
device.mfr: American Power Conversion<br>
device.model: Smart-UPS_1500<br>
device.serial: 3S1906X11389<br>
device.type: ups<br>
<a href="http://driver.name" rel="noreferrer noreferrer" target="_blank">driver.name</a>: usbhid-ups<br>
driver.parameter.bus: 001<br>
driver.parameter.pollfreq: 30<br>
driver.parameter.pollinterval: 2<br>
driver.parameter.port: /dev/ttyUSB1<br>
driver.parameter.product: Smart-UPS_1500 FW:UPS 03.5 / ID=1015<br>
driver.parameter.productid: 0003<br>
driver.parameter.serial: 3S1906X11389<br>
driver.parameter.synchronous: no<br>
driver.parameter.vendor: American Power Conversion<br>
driver.parameter.vendorid: 051D<br>
driver.version: 2.7.4<br>
driver.version.data: APC HID 0.96<br>
driver.version.internal: 0.41<br>
ups.beeper.status: enabled<br>
ups.delay.shutdown: 20<br>
ups.firmware: UPS 03.5 / ID=1015<br>
ups.mfr: American Power Conversion<br>
ups.mfr.date: 2019/02/06<br>
ups.model: Smart-UPS_1500<br>
ups.productid: 0003<br>
ups.serial: 3S1906X11389<br>
ups.status: OL<br>
ups.timer.reboot: -1<br>
ups.timer.shutdown: 65535<br>
ups.vendorid: 051d<br>
<br>
I have a 20kw standby whose time from failure to usable power is around <br>
17 seconds,<br>
but the front panel of this ups is now telling me it needs a fresh <br>
battery, and it<br>
is about 3 years old. But all it has to do is run me for 20 seconds. <br>
Pointer to<br>
config docs would be most appreciated.<br>
<br>
What else do I need to do?<br>
<br>
Take care & stay well everybody.<br>
<br>
Cheers, Gene Heskett.<br>
-- <br>
"There are four boxes to be used in defense of liberty:<br>
soap, ballot, jury, and ammo. Please use in that order."<br>
-Ed Howdershelt (Author, 1940)<br>
If we desire respect for the law, we must first make the law respectable.<br>
- Louis D. Brandeis<br>
<br>
<br>
_______________________________________________<br>
Nut-upsuser mailing list<br>
<a href="mailto:Nut-upsuser@alioth-lists.debian.net" target="_blank" rel="noreferrer">Nut-upsuser@alioth-lists.debian.net</a><br>
<a href="https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser" rel="noreferrer noreferrer" target="_blank">https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser</a><br>
</blockquote></div>