[NUT] Proxmox 9.1.1, impossible de se connecter sur NUT . upsd Not Listening

[brioulgalopin]

Bonjour,
J'ai fait l'installation d'un proxmox v9.1.1 pour herberger homeAssistant et d'autres VM.
j'ai branché son ce PC un onduleur Eaton 3S 850 en usb.
Cependant j'ai un problème avec l'installation de NUT .
J' ai suivi plusieurs tuto et refait plusieurs fois l'installation, mais j'arrive toujours au même résultat.
Lorsque je lance la commande " upsd " voilà ce que ca me renvoit:

Code : Tout sélectionner

root@pve:~# upsd
Network UPS Tools upsd 2.8.1
fopen /run/nut/upsd.pid: No such file or directory
Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
not listening on 127.0.0.1 port 3493
no listening interface available

voici ce que j'obtiens dans le system log:

Code : Tout sélectionner

Nov 28 22:19:16 pve usbhid-ups[1150]: Startup successful
Nov 28 22:19:16 pve usbhid-ups[1150]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Nov 28 22:19:16 pve nut-driver@eaton[699]: Network UPS Tools - UPS driver controller 2.8.1
Nov 28 22:19:16 pve usbhid-ups[1150]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Nov 28 22:19:16 pve systemd[1]: Started nut-driver@eaton.service - Network UPS Tools - device driver for NUT device 'eaton'.
Nov 28 22:19:16 pve usbhid-ups[1150]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Nov 28 22:19:16 pve systemd[1]: Reached target nut-driver.target - Network UPS Tools - target for power device drivers on this system.
Nov 28 22:19:16 pve systemd[1]: Starting nut-server.service - Network UPS Tools - power devices information server...
Nov 28 22:19:16 pve systemd[1]: Started nut-server.service - Network UPS Tools - power devices information server.
Nov 28 22:19:16 pve systemd[1]: Starting nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller...
Nov 28 22:19:16 pve systemd[1]: Started nut-monitor.service - Network UPS Tools - power device monitor and shutdown controller.
Nov 28 22:19:16 pve systemd[1]: Reached target nut.target - Network UPS Tools - target for power device drivers, data server and monitoring client (if enabled) on this system.
Nov 28 22:19:16 pve nut-server[1153]: fopen /run/nut/upsd.pid: No such file or directory
Nov 28 22:19:16 pve nut-server[1153]: Could not find PID file '/run/nut/upsd.pid' to see if previous upsd instance is already running!
Nov 28 22:19:16 pve nut-server[1153]: listening on 127.0.0.1 port 3493
Nov 28 22:19:16 pve upsd[1153]: listening on 127.0.0.1 port 3493
Nov 28 22:19:16 pve nut-server[1153]: Connected to UPS [eaton]: usbhid-ups-eaton
Nov 28 22:19:16 pve nut-server[1153]: Found 1 UPS defined in ups.conf
Nov 28 22:19:16 pve upsd[1153]: Connected to UPS [eaton]: usbhid-ups-eaton
Nov 28 22:19:16 pve upsd[1153]: Found 1 UPS defined in ups.conf
Nov 28 22:19:16 pve nut-server[1153]: Running as foreground process, not saving a PID file
Nov 28 22:19:16 pve nut-server[1153]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Nov 28 22:19:16 pve nut-server[1153]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Nov 28 22:19:16 pve nut-server[1153]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Nov 28 22:19:16 pve upsd[1153]: Running as foreground process, not saving a PID file
Nov 28 22:19:16 pve upsd[1153]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Nov 28 22:19:16 pve upsd[1153]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Nov 28 22:19:16 pve upsd[1153]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Nov 28 22:19:16 pve nut-monitor[1156]: fopen /run/nut/upsmon.pid: No such file or directory
Nov 28 22:19:16 pve nut-monitor[1156]: Could not find PID file to see if previous upsmon instance is already running!
Nov 28 22:19:16 pve nut-monitor[1156]: UPS: eaton@localhost (primary) (power value 1)
Nov 28 22:19:16 pve nut-monitor[1156]: Using power down flag file /etc/killpower
Nov 28 22:19:16 pve nut-monitor[1158]: Init SSL without certificate database
Nov 28 22:19:16 pve nut-monitor[1158]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more about it
Nov 28 22:19:16 pve nut-monitor[1158]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Nov 28 22:19:16 pve nut-monitor[1158]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Nov 28 22:19:16 pve nut-server[1153]: User upsadmin@127.0.0.1 logged into UPS [eaton]
Nov 28 22:19:16 pve upsd[1153]: User upsadmin@127.0.0.1 logged into UPS [eaton]

En requêtant l'onduleur en localhost j'ai pourtant bien les information de celui-ci : upsc eaton@localhost

Code : Tout sélectionner

root@pve:~# upsc eaton@localhost
Init SSL without certificate database
battery.charge: 100
battery.charge.low: 20
battery.runtime: 2400
battery.type: PbAc
device.mfr: EATON
device.model: Eaton 3S 850 
device.serial: Blank
device.type: ups
driver.debug: 0
driver.flag.allow_killpower: 0
driver.name: usbhid-ups
driver.parameter.pollfreq: 30
driver.parameter.pollinterval: 2
driver.parameter.port: auto
driver.parameter.synchronous: auto
driver.state: quiet
driver.version: 2.8.1
driver.version.data: MGE HID 1.46
driver.version.internal: 0.52
driver.version.usb: libusb-1.0.28 (API: 0x100010a)
input.transfer.high: 264
input.transfer.low: 184
outlet.1.desc: PowerShare Outlet 1
outlet.1.id: 1
outlet.1.status: on
outlet.1.switchable: no
outlet.desc: Main Outlet
outlet.id: 0
outlet.switchable: yes
output.frequency.nominal: 50
output.voltage: 230.0
output.voltage.nominal: 230
ups.beeper.status: enabled
ups.delay.shutdown: 20
ups.delay.start: 30
ups.firmware: 02.08.0010
ups.load: 12
ups.mfr: EATON
ups.model: Eaton 3S 850 
ups.power.nominal: 850
ups.productid: ffff
ups.realpower: 82
ups.serial: Blank
ups.status: OL
ups.timer.shutdown: -1
ups.timer.start: -1
ups.type: offline / line interactive
ups.vendorid: 0463

Voici le status du nut-server configuré

Code : Tout sélectionner

root@pve:~# systemctl status nut-server.service
● nut-server.service - Network UPS Tools - power devices information server
     Loaded: loaded (/usr/lib/systemd/system/nut-server.service; enabled; preset: enabled)
     Active: active (running) since Fri 2025-11-28 22:19:16 CET; 32min ago
 Invocation: ba3d01606dd74604a8be7b076845f742
    Process: 1152 ExecStartPre=/usr/bin/systemd-tmpfiles --create /usr/lib/tmpfiles.d/nut-common-tmpfiles.conf (code=exited, status=0/SUCCESS)
   Main PID: 1153 (upsd)
      Tasks: 1 (limit: 18734)
     Memory: 1.8M (peak: 2.5M)
        CPU: 87ms
     CGroup: /system.slice/nut-server.service
             └─1153 /lib/nut/upsd -F

Nov 28 22:19:16 pve nut-server[1153]: Running as foreground process, not saving a PID file
Nov 28 22:19:16 pve nut-server[1153]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam m>
Nov 28 22:19:16 pve nut-server[1153]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Nov 28 22:19:16 pve nut-server[1153]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Nov 28 22:19:16 pve upsd[1153]: Running as foreground process, not saving a PID file
Nov 28 22:19:16 pve upsd[1153]: upsnotify: notify about state 2 with libsystemd: was requested, but not running as a service unit now, will not spam more ab>
Nov 28 22:19:16 pve upsd[1153]: upsnotify: failed to notify about state 2: no notification tech defined, will not spam more about it
Nov 28 22:19:16 pve upsd[1153]: upsnotify: logged the systemd watchdog situation once, will not spam more about it
Nov 28 22:19:16 pve nut-server[1153]: User upsadmin@127.0.0.1 logged into UPS [eaton]
Nov 28 22:19:16 pve upsd[1153]: User upsadmin@127.0.0.1 logged into UPS [eaton]

Pourriez-vous m'aider? Celà fait 1 semaine que je cherche sans solution.
Merci

[benjarobin]

Bonjour,
Je ne comprends pas quel est le souci, tout à l'air de parfaitement fonctionner...
Tu ne dois surtout pas lancer upsd à la main. Tu dois utiliser le service, mais celui à l'air fonctionnel

[brioulgalopin]

Bonjour,

Sur ma VM homeAssitant je n'arrive pas à me connecter au service NUT hébergé sur mon proxmox.
J'ai ce message lorsque je l'ajoute:




Comme si Nut ne répondait pas sur le 127.0.0.1:3493

[benjarobin]

Car ce n'est pas localhost l'IP de ton serveur NUT.
De plus le serveur NUT n'écoute que sur localhost, donc tu dois le configurer afin d'écouter sur l'interface externe. Voir fichier de configuration du serveur NUT