I am trying to get nut ups monitoring software working on ubuntu. It works on Debian and windows 10 but I can't get the web portion working on Ubuntu. Someone wrote some instructions on this in this conference a few years ago but they are out of date or missing a step Anyone have experience with this? Thanks

I recently installed a UPS on a recently configured server running Ubuntu 22.04. I'm using an APC Back-UPS 600M1. I followed this tutorial and related video to get it all set up in docker using NUT UPS Tools (with a docker file from edgd1er/webnut:latest) seemed to work properly. However one of the various daemons in the NUT packages

Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Generic HID driver 0.41 (2.7.4)
USB communication driver 0.33
Using subdriver: APC HID 0.96

seems to be stopping and I cannot seem to find out which one or why.

The syslog entries for the last failure look like this:

Feb 25 19:08:33 zeta upsd[783995]: fopen /run/nut/upsd.pid: No such file or directory
Feb 25 19:08:33 zeta systemd[1]: nut-monitor.service: Deactivated successfully.
Feb 25 19:08:33 zeta upsmon[784003]: fopen /run/nut/upsmon.pid: No such file or directory
Feb 25 19:08:33 zeta systemd[1]: nut-monitor.service: Can't open PID file /run/nut/upsmon.pid (yet?) after start: Operation not permitted
Feb 25 19:08:33 zeta systemd[1]: nut-monitor.service: Supervising process 784005 which is not our child. We'll most likely not notice when it exits.
Feb 25 19:08:33 zeta systemd[1]: nut-monitor.service: Deactivated successfully.
Feb 25 19:08:33 zeta upsmon[784010]: fopen /run/nut/upsmon.pid: No such file or directory
Feb 25 19:08:33 zeta systemd[1]: nut-monitor.service: Can't open PID file /run/nut/upsmon.pid (yet?) after start: Operation not permitted
Feb 25 19:08:33 zeta systemd[1]: nut-monitor.service: Supervising process 784012 which is not our child. We'll most likely not notice when it exits.
Feb 25 19:08:33 zeta upsdrvctl[784016]: Can't open /run/nut/usbhid-ups-auto.pid: No such file or directory
Feb 25 19:08:33 zeta systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
Feb 25 19:08:33 zeta systemd[1]: nut-driver.service: Failed with result 'exit-code'. 

It seems there is something amiss with /run/nut/upsmon.pid -- could it be permissions? Here are the files in that folder:

drwxrwx---  2 root nut   120 Feb 25 19:08 .
drwxr-xr-x 35 root root 1020 Feb 25 16:16 ..
-rw-r--r--  1 nut  nut     7 Feb 25 19:08 upsd.pid
-rw-r--r--  1 root root    7 Feb 25 19:08 upsmon.pid
srw-rw----  1 nut  nut     0 Feb 25 19:08 usbhid-ups-apc-zeta
-rw-r--r--  1 nut  nut     7 Feb 25 19:08 usbhid-ups-apc-zeta.pid

I wrote a shell script to restart the related services:

#! /usr/bin/bash
sudo service nut-server restart &&
sudo service nut-client restart &&
sudo systemctl restart nut-monitor &&
sudo upsdrvctl stop &&
sudo upsdrvctl start

Could I have got something out of order so that the startup is going haywire after running for some time? I am somewhat of a noob in this area and would appreciate any help or information that can get me looking in the correct direction to resolve the issue.