Questions[nut](ubuntu)

I'm using Kubuntu 20.04.1 64 bit. To clarify I'm not trying to use this via network but directly via USB cable.

The UPS should be Bus 001 Device 004: ID 0001:0000 Fry's Electronics

EDIT:

I found the drivers list with, "Various" "ups" "2" "(Various USB)" "UPSilon 2000 software" "blazer_usb langid_fix=0x409" and a little web search pointed to have the configuration like this and it connected.

[upsilon-2000]
driver = "blazer_usb"
port = auto
langid_fix="0x409"
desc="Upsilon 2000"
vendorid = "0001"
productid = "0000"

Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
Supported UPS detected with megatec protocol
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf

Using 'guestimation' (low: 20.800000, high: 26.000000)!
Battery runtime will not be calculated (runtimecal not set)

Now I need to be able to configure it or is it already configured by default?

# --------------------------------------------------------------------------
# FINALDELAY - last sleep interval before shutting down the system
#
# On a master, upsmon will wait this long after sending the NOTIFY_SHUTDOWN
# before executing your SHUTDOWNCMD.  If you need to do something in between
# those events, increase this number.  Remember, at this point your UPS is 
# almost depleted, so don't make this too high.
#
# Alternatively, you can set this very low so you don't wait around when
# it's time to shut down.  Some UPSes don't give much warning for low
# battery and will require a value of 0 here for a safe shutdown.
#
# Note: If FINALDELAY on the slave is greater than HOSTSYNC on the master,
# the master will give up waiting for the slave to disconnect.

FINALDELAY 5

upsmon.conf

I made a systemd service and this is the status shown. EDIT: I just needed nut-server.service

Message from system

Broadcast message from nut@carlos-AB350-Gaming-3 (somewhere) (Tue Nov 17 16:03:
Communications with UPS upsilon-2000@localhost established 

[Unit]
Description=Upsilon monitor start

[Service]
Type=oneshot
ExecStart=upsdrvctl start

[Install]
WantedBy=multi-user.target

systemctl status ups-start.service 
● ups-start.service - Upsilon monitor start
     Loaded: loaded (/etc/systemd/system/ups-start.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Tue 2020-11-17 15:38:41 AST; 3s ago
    Process: 7911 ExecStart=/usr/sbin/upsdrvctl start (code=exited, status=0/SUCCESS)
   Main PID: 7911 (code=exited, status=0/SUCCESS)

nov 17 15:38:37 carlos-AB350-Gaming-3 upsdrvctl[7912]: Supported UPS detected with megatec protocol
nov 17 15:38:38 carlos-AB350-Gaming-3 upsdrvctl[7912]: Vendor information unavailable
nov 17 15:38:38 carlos-AB350-Gaming-3 upsdrvctl[7912]: No values provided for battery high/low voltages in ups.conf
nov 17 15:38:38 carlos-AB350-Gaming-3 upsdrvctl[7912]: Using 'guestimation' (low: 20.800000, high: 26.000000)!
nov 17 15:38:38 carlos-AB350-Gaming-3 upsdrvctl[7912]: Battery runtime will not be calculated (runtimecal not set)
nov 17 15:38:39 carlos-AB350-Gaming-3 upsdrvctl[7911]: Network UPS Tools - UPS driver controller 2.7.4
nov 17 15:38:39 carlos-AB350-Gaming-3 blazer_usb[7924]: Startup successful
nov 17 15:38:41 carlos-AB350-Gaming-3 blazer_usb[7924]: Signal 15: exiting
nov 17 15:38:41 carlos-AB350-Gaming-3 systemd[1]: ups-start.service: Succeeded.
nov 17 15:38:41 carlos-AB350-Gaming-3 systemd[1]: Finished Upsilon monitor start.

This commands show:

upsdrvctl start
Network UPS Tools - UPS driver controller 2.7.4
Network UPS Tools - Megatec/Q1 protocol USB driver 0.12 (2.7.4)
Supported UPS detected with megatec protocol
Vendor information unavailable
No values provided for battery high/low voltages in ups.conf

Using 'guestimation' (low: 20.800000, high: 26.000000)!
Battery runtime will not be calculated (runtimecal not set)

sudo upsdrvctl stop
Network UPS Tools - UPS driver controller 2.7.4
Can't open /run/nut/blazer_usb-auto.pid: No such file or directory

I am trying to configure my Ubuntu Server (20.04) as a slave to my Synology NAS hooked up to my UPS, but I'm not sure how to complete the process and I haven't found much of anything in terms of documentation or tutorials. Here are the steps I have taken:

On Synology DSM:

1. Hooked Synology up to UPS via USB
2. Turn on UPS Server in DSM settings

3. Add my Linux server IP in "Permitted DiskStation devices" dialog.

On Linux Server:

1. Installed NUT sudo apt-get install nut
2. Modified /etc/nut/nut.conf to mode=netclient
3. Added to /etc/nut/upsmon.conf MONITOR [email protected] UPSUSER MYPASS slave

Finally, when I try to run service nut-client restart, I get the error:

Job for nut-monitor.service failed because the control process exited with error code.

Any ideas what I am doing wrong or what further steps I need to take? Thanks in advance!

I have attached my UPS to ubuntu and it's recognised. However I don't like the options that I see in ubuntu power settings. I have another PC also attached to same UPS. So I want ubuntu desktop to execute script when power is about 50% so my second pc can also properly hibernate. And then I can hibernate my ubuntu PC with same script.

Is it possible to do that in the way that is not breaking ubuntu implpementation of UPS monitor? I have read that I can install nut but I have some errors, maybe it's a conflict

● 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 Sat 2019-07-13 02:09:46 MSK; 11ms ago
  Process: 13906 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)

Maybe I can catch some dmesg message or check the status of UPS with some native tool?

I am attempting to install a UPS onto my Ubuntu 16.04 LTS server. Besides the power connection the UPS has a USB cable connection to the PC.

I am using nut (network ups tools), which I installed with

sudo apt install nut nut-monitor usbhid-ups

I then edited the configuration files in /etc/nut , adapting the instructions found at http://networkupstools.org/docs/user-manual.chunked/ar01s06.html (which used slightly different paths).

I successfully got to the stage in the instructions where /var/log/syslog contained messages such as

May 29 01:11:27 mybox upsmon[102]: Startup successful
May 29 01:11:28 mybox upsd[100]: Client [email protected]
logged into UPS [myupsname]

When I got to the "testing shutdown" section I had my first serious problem: to test a forced shutdown sequence I was told to issue the command

upsmon -c fsd

...with the expectation that "If everything works correctly, the computer will be forcibly powered off, may remain off for a few seconds to a few minutes (depending on the driver and UPS type), then will power on again."

What happened was that the computer did shut down and then never came back on. Note I have explicitly configured the BIOS to turn the computer "always on" when power is reapplied after a power cut (as opposed to "last state" or "always off").

How do I diagnose why it's not coming back on, and what can I do to remedy?