I have plugged my TrueNAS into a new Eaton 3S 550D and connected it via USB. I’m running TrueNAS Scale 25.04.2.4. The Eaton doesn’t seem to communicate correctly with my NAS. I keep getting the following error message:
root@***# upsc upsmon@localhost
Init SSL without certificate database
Error: Unknown UPS
The UPS the following model:
www.eaton . com/de/de-de/skuPage.3S550D.html
(sorry, it appears I’m too new a forum user to be allowed to include links.)
The Eaton 3S is listed in the overview of compatible UPS devices:
networkupstools . org/stable-hcl.html
The nut-scanner identifies it correctly:
root@***# nut-scanner -U
Scanning USB bus.
[nutdev1]
driver = "usbhid-ups"
port = "auto"
vendorid = "0463"
productid = "FFFF"
product = "Eaton 3S"
serial = "Blank"
vendor = "EATON"
bus = "003"
I believe to have configured the UPS service settings correctly (although I have to admit to being a noob when it comes to TrueNAS):
General options:
Identifier: ups
Monitor user: upsmon
UPS Mode: Master
Monitor password: ****
Driver: Eaton ups 5 3S (usbhid-ups)
Port or Hostname: auto
(The “Eaton ups 5 3S (usbhid-ups)” is the only Eaton driver referencing “3S”, but I have tried some other Eaton-drivers of the “usbhid-ups” type – to no avail.)
A test with a simulated loss of power correctly triggers the corresponding “critical alert” (“UPS ups is on battery power.”), which also gets sent out via mail correctly and shutdown commences after the specified time period of being on battery power (although, weirdly, before shutdown I receive an alert mail stating that “The following alert has been cleared: UPS ups is on battery power.” But I guess that’s intended behaviour [?].).
This is the test log (power outage simulation started at 09:56:02, shutdown timer 300 seconds):
Sep 20 09:56:02 truenas nut-monitor[2747]: UPS ups@localhost:3493 on battery
Sep 20 09:56:02 truenas nut-monitor[28052]: Executing command: NOTIFY-ONBATT
Sep 20 09:56:02 truenas upssched[28052]: Executing command: NOTIFY-ONBATT
(...)
Sep 20 09:56:03 truenas upssched[28067]: Timer daemon started
Sep 20 09:56:03 truenas upssched[28067]: New timer: SHUTDOWN (300 seconds)
Sep 20 09:56:03 truenas nut-monitor[28050]: Network UPS Tools upsmon 2.8.0
(...)
Sep 20 10:01:03 truenas upssched[28067]: Event: SHUTDOWN
Sep 20 10:01:03 truenas nut-monitor[2747]: Signal 10: User requested FSD
Sep 20 10:01:03 truenas nut-monitor[2747]: Executing automatic power-fail shutdown
Sep 20 10:01:03 truenas upsd[2742]: Client upsmon@::1 set FSD on UPS [ups]
Sep 20 10:01:03 truenas nut-server[2742]: Client upsmon@::1 set FSD on UPS [ups]
Sep 20 10:01:03 truenas nut-monitor[34824]: wall: /dev/ws/2: No such file or directory
Sep 20 10:01:03 truenas nut-monitor[2747]: Auto logout and shutdown proceeding
Sep 20 10:01:03 truenas nut-monitor[34827]: Executing command: NOTIFY-SHUTDOWN
Sep 20 10:01:03 truenas upssched[34827]: Executing command: NOTIFY-SHUTDOWN
(...)
Sep 20 10:01:03 truenas upssched[28067]: Timer queue empty, exiting
Sep 20 10:01:03 truenas nut-monitor[34831]: null
(...)
Sep 20 10:01:03 truenas nut-monitor[34825]: Network UPS Tools upsmon 2.8.0
Sep 20 10:01:08 truenas nut-monitor[2747]: Network UPS Tools upsmon 2.8.0
(...)
Sep 20 10:01:08 truenas systemd-logind[2395]: The system will power off now!
Sep 20 10:01:08 truenas systemd-logind[2395]: System is powering down.
Sep 20 10:01:08 truenas nut-monitor[2743]: Network UPS Tools upsmon 2.8.0
Nonetheless, the upsc output concerns me.
Any ideas as to what I should try?