installing ups monitor

[Bo Berglund]

On Sun, 10 Jan 2021 09:20:36 +0100, Bo Berglund <bo.berglund at gmail.com> wrote:

>But how is it used on Ubuntu?
>
>I have not seen any "upsmon" program on my Ubuntu 18.04 server in any case (if
>that is the correct name)...
>
>Or is it nut-client? Strange name in that case...

I found a page describing the installation of linux packages for ups:
https://networkupstools.org/docs/user-manual.chunked/ar01s05.html#Installing_packages

But when I did so I reached an error:

$ sudo apt install nut
....
The following NEW packages will be installed:
  libupsclient4 nut nut-client nut-server
....
Created symlink /etc/systemd/system/multi-user.target.wants/nut-monitor.service
? /lib/systemd/system/nut-monitor.service.
Job for nut-monitor.service failed because the service did not take the steps
required by its unit configuration.
See "systemctl status nut-monitor.service" and "journalctl -xe" for details.

invoke-rc.d: initscript nut-client, action "start" failed.  <== ERROR HERE!

? nut-monitor.service - Network UPS Tools - power device monitor and shutdown
controller
   Loaded: loaded (/lib/systemd/system/nut-monitor.service; enabled; vendor
preset: enabled)
   Active: failed (Result: protocol) since Sun 2021-01-10 09:31:07 CET; 9ms ago
  Process: 7659 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)

Jan 10 09:31:07 ubuntuserv systemd[1]: Starting Network UPS Tools - power device
monitor and shutdown controller...
Jan 10 09:31:07 ubuntuserv upsmon[7659]: upsmon disabled, please adjust the
configuration to your needs
Jan 10 09:31:07 ubuntuserv upsmon[7659]: Then set MODE to a suitable value in
/etc/nut/nut.conf to enable it
Jan 10 09:31:07 ubuntuserv systemd[1]: nut-monitor.service: Can't open PID file
/var/run/nut/upsmon.pid (yet?) after start: No such file or directory
Jan 10 09:31:07 ubuntuserv systemd[1]: nut-monitor.service: Failed with result
'protocol'.
Jan 10 09:31:07 ubuntuserv systemd[1]: Failed to start Network UPS Tools - power
device monitor and shutdown controller.
....
nut-driver.service is a disabled or a static unit, not starting it.
....

So I am asked to edit /etc/nut/nut.conf, but this only contains a single line:
MODE=none



-- 
Bo Berglund
Developer in Sweden