Bonjour à vous tous,
J'ai un petit soucis avec un onduleur que j'essaie de commander avec nut.
Tout fonctionne très bien mise à part que lors d'un redémarrage l'onduleur ne semble plus communiquer. J'ai cette ligne dans les log système :
Code :
- Dec 14 21:52:54 upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
|
Un
permet de résoudre le problème.
Voila ce que me retourne la commande status :
Code :
- # sudo upsdrvctl status
- Network UPS Tools - UPS driver controller 2.7.4
- Error: unrecognized command [status]
|
Et en effet :
Code :
- # sudo upsdrvctl --
- Network UPS Tools - UPS driver controller 2.7.4
- Starts and stops UPS drivers via ups.conf.
- usage: upsdrvctl [OPTIONS] (start | stop | shutdown) [<ups>]
- -h display this help
- -r <path> drivers will chroot to <path>
- -t testing mode - prints actions without doing them
- -u <user> drivers started will switch from root to <user>
- -D raise debugging level
- start start all UPS drivers in ups.conf
- start <ups> only start driver for UPS <ups>
- stop stop all UPS drivers in ups.conf
- stop <ups> only stop driver for UPS <ups>
- shutdown shutdown all UPS drivers in ups.conf
- shutdown <ups> only shutdown UPS <ups>
|
Après je remarque que lorsque je lance la commande manuellement; j'ai l'impression de comprendre qu'il utilise un "sous driver":
Code :
- # sudo upsdrvctl start
- 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: MGE HID 1.39
|
Alors que le driver indiqué dans /etc/nut/ups.conf et bien celui préconisé par cette page : https://networkupstools.org/stable-hcl.html pour un onduleur Eaton Ellipse ECO 650 VA USB
Code :
- [myups]
- driver = usbhid-ups
- port = auto
- desc = "Eaton Ellipse ECO 650 VA USB"
|
Tout en sachant que le "subdriver: MGE HID 1.39" n'est pas présent dans la liste affichée par ls /lib/nut
Code :
- # ls /lib/nut
- al175 bestups ivtscd oneac tripplitesu
- apcsmart blazer_ser liebert optiups tripplite_usb
- apcsmart-old blazer_usb liebert-esp2 powercom upscode2
- apcupsd-ups clone masterguard powerpanel upsd
- bcmxcp clone-outlet metasys rhino upsmon
- bcmxcp_usb dummy-ups mge-shut richcomm_usb usbhid-ups
- belkin etapro mge-utalk riello_ser victronups
- belkinunv everups microdowell riello_usb
- bestfcom gamatronic nutdrv_atcl_usb safenet
- bestfortress genericups nutdrv_qx solis
- bestuferrups isbmex oldmge-shut tripplite
|
Il s'agit donc peut-être d'un sous drivre de "usbhid-ups" et le problème ne viendrait donc pas d'un soucis de driver mais bien d'un soucis de démarrage.
Alors je pourrais en effet faire un script de démarrage pour lancer automatiquement un "upsdrvctl start". Mais j'aurais bien aimé trouver la source du problème.
De plus, même après un "upsdrvctl start", la commande "# systemctl list-units --type=service" me retourne ces lignes :
Code :
- nut-driver.service loaded failed failed Network UPS Tools - power device driver controller
- nut-monitor.service loaded active running Network UPS Tools - power device monitor and shutdown controller
- nut-server.service loaded active running Network UPS Tools - power devices information server
|
J'essaie donc :
Code :
- # sudo systemctl restart nut-driver.service
- Job for nut-driver.service failed because a timeout was exceeded.
- See "systemctl status nut-driver.service" and "journalctl -xe" for details
|
Et voila ce qu'il y a dans les log
Code :
- Dec 15 13:53:10 cal.fr upsdrvctl[25019]: Duplicate driver instance detected! Terminating other driver!
- Dec 15 13:53:15 cal.fr systemd[1]: nut-driver.service: Start operation timed out. Terminating.
- Dec 15 13:53:15 cal.fr systemd[1]: nut-driver.service: Control process exited, code=killed, status=15/TERM
- Dec 15 13:53:18 cal.fr upsdrvctl[25019]: Using subdriver: MGE HID 1.39
- Dec 15 13:53:18 cal.fr upsdrvctl[25019]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)
- Dec 15 13:53:18 cal.fr upsdrvctl[25019]: USB communication driver 0.33
- Dec 15 13:53:20 cal.fr systemd[1]: nut-driver.service: State 'stop-final-sigterm' timed out. Killing.
- Dec 15 13:53:20 cal.fr systemd[1]: nut-driver.service: Killing process 25020 (usbhid-ups) with signal SIGKILL.
- Dec 15 13:53:20 cal.fr systemd[1]: nut-driver.service: Failed with result 'timeout'.
- Dec 15 13:53:20 cal.fr systemd[1]: Failed to start Network UPS Tools - power device driver controller.
|
Voici également le retour de 3 autres commandes :
Code :
- # systemctl status nut-driver.service
- ● nut-driver.service - Network UPS Tools - power device driver controller
- Loaded: loaded (/lib/systemd/system/nut-driver.service; static; vendor preset: enabled)
- Active: failed (Result: timeout) since Wed 2021-12-15 13:53:20 CET; 14min ago
- Process: 25019 ExecStart=/sbin/upsdrvctl start (code=killed, signal=TERM)
- Dec 15 13:53:10 cal.fr upsdrvctl[25019]: Duplicate driver instance detected! Terminating other driver!
- Dec 15 13:53:15 cal.fr systemd[1]: nut-driver.service: Start operation timed out. Terminating.
- Dec 15 13:53:15 cal.fr systemd[1]: nut-driver.service: Control process exited, code=killed, status=15/TERM
- Dec 15 13:53:18 cal.fr upsdrvctl[25019]: Using subdriver: MGE HID 1.39
- Dec 15 13:53:18 cal.fr upsdrvctl[25019]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)
- Dec 15 13:53:18 cal.fr upsdrvctl[25019]: USB communication driver 0.33
- Dec 15 13:53:20 cal.fr systemd[1]: nut-driver.service: State 'stop-final-sigterm' timed out. Killing.
- Dec 15 13:53:20 cal.fr systemd[1]: nut-driver.service: Killing process 25020 (usbhid-ups) with signal SIGKILL.
- Dec 15 13:53:20 cal.fr systemd[1]: nut-driver.service: Failed with result 'timeout'.
- Dec 15 13:53:20 cal.fr systemd[1]: Failed to start Network UPS Tools - power device driver controller.
|
Code :
- # systemctl status nut-monitor.service
- ● 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: active (running) since Tue 2021-12-14 21:52:29 CET; 16h ago
- Process: 1668 ExecStart=/sbin/upsmon (code=exited, status=0/SUCCESS)
- Main PID: 1670 (upsmon)
- Tasks: 2 (limit: 4915)
- Memory: 3.2M
- CGroup: /system.slice/nut-monitor.service
- ├─1669 /lib/nut/upsmon
- └─1670 /lib/nut/upsmon
- Dec 15 14:07:59 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:04 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:09 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:14 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:19 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:19 cal.fr upsmon[1670]: UPS myups@localhost is unavailable
- Dec 15 14:08:24 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:29 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:34 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
- Dec 15 14:08:39 cal.fr upsmon[1670]: Poll UPS [myups@localhost] failed - Driver not connected
|
Code :
- # systemctl status nut-server.service
- ● nut-server.service - Network UPS Tools - power devices information server
- Loaded: loaded (/lib/systemd/system/nut-server.service; enabled; vendor preset: enabled)
- Active: active (running) since Tue 2021-12-14 21:52:29 CET; 16h ago
- Process: 1664 ExecStart=/sbin/upsd (code=exited, status=0/SUCCESS)
- Main PID: 1667 (upsd)
- Tasks: 1 (limit: 4915)
- Memory: 1.5M
- CGroup: /system.slice/nut-server.service
- └─1667 /lib/nut/upsd
- Dec 14 22:32:29 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
- Dec 14 22:37:29 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
- Dec 14 22:41:08 cal.fr upsd[1667]: Connected to UPS [myups]: usbhid-ups-myups
- Dec 15 09:27:07 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
- Dec 15 09:27:19 cal.fr upsd[1667]: Connected to UPS [myups]: usbhid-ups-myups
- Dec 15 09:27:37 cal.fr upsd[1667]: Connected to UPS [myups]: usbhid-ups-myups
- Dec 15 13:53:10 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
- Dec 15 13:58:11 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
- Dec 15 14:03:11 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
- Dec 15 14:08:11 cal.fr upsd[1667]: Can't connect to UPS [myups] (usbhid-ups-myups): No such file or directory
|
Auriez-vous une piste de recherche ?
Merci de votre aide !
Message édité par Petlo_Lithi le 15-12-2021 à 14:13:26