[Nut-upsuser] upsmon fails to start

[Mick]

On Saturday, 1 September 2018 17:50:13 BST Charles Lepple wrote:
> I don’t have the code in front of me at the moment, but my guess is that the
> config parser stopped parsing at the “#” character. 

I suspected a rogue character was being interpreted and used `backticks`, 
'single quotes' and then "double quotes", but all failed.  I ended up removing 
the offending # character and it seems to have worked:

Sep 01 19:33:00 osmc upsdrvctl[1423]: Using subdriver: MGE HID 1.33
Sep 01 19:33:00 osmc upsdrvctl[1423]: Network UPS Tools - Generic HID driver 
0.38 (2.7.2)
Sep 01 19:33:00 osmc upsdrvctl[1423]: USB communication driver 0.32
Sep 01 19:33:00 osmc upsdrvctl[1423]: Network UPS Tools - UPS driver 
controller 2.7.2
Sep 01 19:33:00 osmc usbhid-ups[1459]: Startup successful
Sep 01 19:33:02 osmc upsd[1460]: fopen /var/run/nut/upsd.pid: No such file or 
directory
Sep 01 19:33:02 osmc upsd[1460]: listening on 127.0.0.1 port 3493
Sep 01 19:33:02 osmc upsd[1460]: listening on ::1 port 3493
Sep 01 19:33:02 osmc upsd[1460]: listening on 127.0.0.1 port 3493
Sep 01 19:33:02 osmc upsd[1460]: listening on ::1 port 3493
Sep 01 19:33:02 osmc upsd[1460]: Connected to UPS [T1000G3]: usbhid-ups-
T1000G3
Sep 01 19:33:02 osmc upsd[1460]: Connected to UPS [T1000G3]: usbhid-ups-
T1000G3
Sep 01 19:33:02 osmc upsd[1494]: Startup successful
Sep 01 19:33:02 osmc upsmon[1495]: fopen /var/run/nut/upsmon.pid: No such file 
or directory
Sep 01 19:33:02 osmc upsmon[1495]: Using power down flag file /etc/killpower
Sep 01 19:33:02 osmc upsmon[1495]: UPS: T1000G3 at localhost (master) (power 
value 1)
Sep 01 19:33:02 osmc upsmon[1495]: Using power down flag file /etc/killpower
Sep 01 19:33:02 osmc systemd[1]: PID file /var/run/nut/upsmon.pid not readable 
(yet?) after start.
Sep 01 19:33:02 osmc upsmon[1496]: Startup successful
Sep 01 19:33:02 osmc upsmon[1497]: Init SSL without certificate database
Sep 01 19:33:03 osmc upsd[1494]: User upsmon@::1 logged into UPS [T1000G3]


Thank you very much for your help.

Is there a particular command I could run to make sure upsmon is working as 
expected?  A recent battery failure caused the server to crash, but thankfully 
it didn't corrupt any data.

-- 
Regards,
Mick