-
Notifications
You must be signed in to change notification settings - Fork 453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NUT plugin : nut-driver on OMV 7.x start even with service is Netclient #1721
Comments
Ok, found the problem. Switching form Standalone to Netclient don't remove nut-driver@ups.service Working for me from Standalone to Netclient :
After this it work properly. |
Has the problem fixed with the latest update |
Hi, |
…in 'Netclient' mode Fixes: openmediavault#1721 Signed-off-by: Volker Theile <votdev@gmx.de>
Hi, The problem also exists with version 7.0.5-1 (Sandworm). I uninstalled, cleaned, and then installed as described. Now it is working! Thanks! |
Hi,
On plugin UPS, when mode is Netclient, the nut-driver is still enable and activate.
So it generate a constant error in journal every 15 seconds :
...
Mar 08 16:08:27 storage nut-driver@ups[513993]: Network UPS Tools - Generic HID driver 0.47 (2.8.0)
Mar 08 16:08:27 storage nut-driver@ups[513993]: USB communication driver (libusb 1.0) 0.43
Mar 08 16:08:27 storage nut-driver@ups[513993]: libusb1: Could not open any HID devices: insufficient permissions on everything
Mar 08 16:08:27 storage nut-driver@ups[513993]: No matching HID UPS found
Mar 08 16:08:27 storage nut-driver@ups[513992]: Driver failed to start (exit status=1)
Mar 08 16:08:27 storage nut-driver@ups[513992]: Network UPS Tools - UPS driver controller 2.8.0
Mar 08 16:08:27 storage systemd[1]: nut-driver@ups.service: Control process exited, code=exited, status=1/FAILURE
Mar 08 16:08:27 storage systemd[1]: nut-driver@ups.service: Failed with result 'exit-code'.
Mar 08 16:08:27 storage systemd[1]: Failed to start nut-driver@ups.service - Network UPS Tools - device driver for NUT device 'ups'.
Mar 08 16:08:42 storage systemd[1]: nut-driver@ups.service: Scheduled restart job, restart counter is at 18.
Mar 08 16:08:42 storage systemd[1]: Stopped nut-driver@ups.service - Network UPS Tools - device driver for NUT device 'ups'.
Mar 08 16:08:42 storage systemd[1]: Starting nut-driver@ups.service - Network UPS Tools - device driver for NUT device 'ups'...
Mar 08 16:08:42 storage nut-driver@ups[514044]: Network UPS Tools - Generic HID driver 0.47 (2.8.0)
Mar 08 16:08:42 storage nut-driver@ups[514044]: USB communication driver (libusb 1.0) 0.43
Mar 08 16:08:42 storage nut-driver@ups[514044]: libusb1: Could not open any HID devices: insufficient permissions on everything
Mar 08 16:08:42 storage nut-driver@ups[514044]: No matching HID UPS found
Mar 08 16:08:42 storage nut-driver@ups[514043]: Driver failed to start (exit status=1)
Mar 08 16:08:42 storage nut-driver@ups[514043]: Network UPS Tools - UPS driver controller 2.8.0
Mar 08 16:08:42 storage systemd[1]: nut-driver@ups.service: Control process exited, code=exited, status=1/FAILURE
Mar 08 16:08:42 storage systemd[1]: nut-driver@ups.service: Failed with result 'exit-code'.
Mar 08 16:08:42 storage systemd[1]: Failed to start nut-driver@ups.service - Network UPS Tools - device driver for NUT device 'ups'.
...
Normally, when UPS is in mode = Netclient, only nut-monitor.service must be start.
Thanks.
The text was updated successfully, but these errors were encountered: