To test this setup I would have to install OMV on a raspberry, and it's something I keep resisting
I think you can test this on a OMV VM on the laptop/desktop.
No need to use a Pi, 😉
To test this setup I would have to install OMV on a raspberry, and it's something I keep resisting
I think you can test this on a OMV VM on the laptop/desktop.
No need to use a Pi, 😉
Good idea. It had not occurred to me to think about it, I will try it.
Been trying to follow that info but I'm feeling like a noob: (hope this is someone else's situation so to have some pointers AKA piggyback-ride )
Netclient Hostname # <- The LAN IP can be used????? Or does it need to be the Hostname where the UPS is plugged?
Netclient Username # <- This is where the doubt lives: can I just use any user or does it have to be a specific one?
Netclient Password # <- Password for the above user
Here is what I did today:
As discussed in another thread my UPS was not supported by nut, so i have my Raspberry Pi 1 monitoring it with the apcupsd toolkit and provide the readings to the network. The Pi has the hostname usv.xxx.xxx in my local network.
Here is one OMV listening to the UPS info on the Pi:
And I made the other OMV listen to the OMV above:
The same should work if the first omv listens to the UPS by USB.
Waht the plugin does when "Enable remote monitoring of the local connected UPS." is checke is to set the nut to MODE=netserver (instead standalone) and make the daemon listen on 0.0.0.0:3493
Here is what I did today:
Thanks Zoki . You saved me from having to try it myself. The procedure is already added to the guide.
I run into a nearly same issue. A freshly installed 5.6.25-1 all updates are done.
The only different ist that my APC USV SMT750RMI2U is connected with an NIC Card AP9630.
btw. on my omv4 everythink works with the USV and nut.
usrmerge is being installed too
My configuration:
When i try to save this get this error:
Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color nut 2>&1' with exit code '1': debian: ---------- ID: configure_nut_nut_conf Function: file.managed Name: /etc/nut/nut.conf Result: True Comment: File /etc/nut/nut.conf is in the correct state Started: 10:59:26.296321 Duration: 26.157 ms Changes: ---------- ID: configure_nut_ups_conf Function: file.managed Name: /etc/nut/ups.conf Result: True Comment: File /etc/nut/ups.conf is in the correct state Started: 10:59:26.322611 Duration: 7.228 ms Changes: ---------- ID: configure_nut_upsd_conf Function: file.managed Name: /etc/nut/upsd.conf Result: True Comment: File /etc/nut/upsd.conf is in the correct state Started: 10:59:26.329958 Duration: 9.944 ms Changes: ---------- ID: configure_nut_upsd_users Function: file.managed Name: /etc/nut/upsd.users Result: True Comment: File /etc/nut/upsd.users updated Started: 10:59:26.340022 Duration: 10.195 ms Changes: ---------- diff: --- +++ @@ -1,11 +1,11 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. [admin] -password = lMzLmJM96pl7ocvf +password = yBVERq2iHhi1XDKT actions = set actions = fsd instcmds = ALL [monmaster] -password = aoRT69hc9EywL7o2 +password = gOsHwInGiZ9fM5Ik upsmon master ---------- ID: configure_nut_upsmon_conf Function: file.managed Name: /etc/nut/upsmon.conf Result: True Comment: File /etc/nut/upsmon.conf updated Started: 10:59:26.350329 Duration: 16.581 ms Changes: ---------- diff: --- +++ @@ -1,6 +1,6 @@ # This file is auto-generated by openmediavault (https://www.openmediavault.org) # WARNING: Do not edit this file, your changes will get lost. -MONITOR ups 1 monmaster aoRT69hc9EywL7o2 master +MONITOR ups 1 monmaster gOsHwInGiZ9fM5Ik master MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" NOTIFYCMD "/sbin/upssched" ---------- ID: configure_nut_upssched_conf Function: file.managed Name: /etc/nut/upssched.conf Result: True Comment: File /etc/nut/upssched.conf is in the correct state Started: 10:59:26.367032 Duration: 8.777 ms Changes: ---------- ID: configure_nut_default_upssched_cmd Function: file.managed Name: /etc/default/upssched-cmd Result: True Comment: File /etc/default/upssched-cmd is in the correct state Started: 10:59:26.375935 Duration: 1.545 ms Changes: ---------- ID: configure_nut_udev_serialups_rule Function: file.managed Name: /etc/udev/rules.d/99-openmediavault-nut-serialups.rules Result: True Comment: File /etc/udev/rules.d/99-openmediavault-nut-serialups.rules is in the correct state Started: 10:59:26.377593 Duration: 1.51 ms Changes: ---------- ID: configure_nut_udevadm_trigger Function: cmd.run Name: udevadm trigger Result: True Comment: State was not run because none of the onchanges reqs changed Started: 10:59:26.379984 Duration: 0.009 ms Changes: ---------- ID: start_nut_driver_service Function: service.running Name: nut-driver Result: False Comment: Job for nut-driver.service failed because the control process exited with error code. See "systemctl status nut-driver.service" and "journalctl -xe" for details. Started: 10:59:26.393206 Duration: 73.309 ms Changes: ---------- ID: start_nut_server_service Function: service.running Name: nut-server Result: True Comment: Service restarted Started: 10:59:26.501238 Duration: 913.472 ms Changes: ---------- nut-server: True ---------- ID: monitor_nut_server_service Function: module.run Result: True Comment: monit.monitor: True Started: 10:59:27.416727 Duration: 13.347 ms Changes: ---------- monit.monitor: True ---------- ID: start_nut_monitor_service Function: service.running Name: nut-monitor Result: True Comment: Service restarted Started: 10:59:27.464851 Duration: 60.022 ms Changes: ---------- nut-monitor: True ---------- ID: monitor_nut_monitor_service Function: module.run Result: True Comment: monit.monitor: True Started: 10:59:27.525220 Duration: 12.108 ms Changes: ---------- monit.monitor: True Summary for debian ------------- Succeeded: 13 (changed=6) Failed: 1 ------------- Total states run: 14 Total run time: 1.154 s
on detail :
Fehler #0:
OMV\ExecException: Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C.UTF-8; omv-salt deploy run --no-color nut 2>&1' with exit code '1': debian:
----------
ID: configure_nut_nut_conf
Function: file.managed
Name: /etc/nut/nut.conf
Result: True
Comment: File /etc/nut/nut.conf is in the correct state
Started: 10:59:26.296321
Duration: 26.157 ms
Changes:
----------
ID: configure_nut_ups_conf
Function: file.managed
Name: /etc/nut/ups.conf
Result: True
Comment: File /etc/nut/ups.conf is in the correct state
Started: 10:59:26.322611
Duration: 7.228 ms
Changes:
----------
ID: configure_nut_upsd_conf
Function: file.managed
Name: /etc/nut/upsd.conf
Result: True
Comment: File /etc/nut/upsd.conf is in the correct state
Started: 10:59:26.329958
Duration: 9.944 ms
Changes:
----------
ID: configure_nut_upsd_users
Function: file.managed
Name: /etc/nut/upsd.users
Result: True
Comment: File /etc/nut/upsd.users updated
Started: 10:59:26.340022
Duration: 10.195 ms
Changes:
----------
diff:
---
+++
@@ -1,11 +1,11 @@
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
[admin]
-password = lMzLmJM96pl7ocvf
+password = yBVERq2iHhi1XDKT
actions = set
actions = fsd
instcmds = ALL
[monmaster]
-password = aoRT69hc9EywL7o2
+password = gOsHwInGiZ9fM5Ik
upsmon master
----------
ID: configure_nut_upsmon_conf
Function: file.managed
Name: /etc/nut/upsmon.conf
Result: True
Comment: File /etc/nut/upsmon.conf updated
Started: 10:59:26.350329
Duration: 16.581 ms
Changes:
----------
diff:
---
+++
@@ -1,6 +1,6 @@
# This file is auto-generated by openmediavault (https://www.openmediavault.org)
# WARNING: Do not edit this file, your changes will get lost.
-MONITOR ups 1 monmaster aoRT69hc9EywL7o2 master
+MONITOR ups 1 monmaster gOsHwInGiZ9fM5Ik master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h +0"
NOTIFYCMD "/sbin/upssched"
----------
ID: configure_nut_upssched_conf
Function: file.managed
Name: /etc/nut/upssched.conf
Result: True
Comment: File /etc/nut/upssched.conf is in the correct state
Started: 10:59:26.367032
Duration: 8.777 ms
Changes:
----------
ID: configure_nut_default_upssched_cmd
Function: file.managed
Name: /etc/default/upssched-cmd
Result: True
Comment: File /etc/default/upssched-cmd is in the correct state
Started: 10:59:26.375935
Duration: 1.545 ms
Changes:
----------
ID: configure_nut_udev_serialups_rule
Function: file.managed
Name: /etc/udev/rules.d/99-openmediavault-nut-serialups.rules
Result: True
Comment: File /etc/udev/rules.d/99-openmediavault-nut-serialups.rules is in the correct state
Started: 10:59:26.377593
Duration: 1.51 ms
Changes:
----------
ID: configure_nut_udevadm_trigger
Function: cmd.run
Name: udevadm trigger
Result: True
Comment: State was not run because none of the onchanges reqs changed
Started: 10:59:26.379984
Duration: 0.009 ms
Changes:
----------
ID: start_nut_driver_service
Function: service.running
Name: nut-driver
Result: False
Comment: Job for nut-driver.service failed because the control process exited with error code.
See "systemctl status nut-driver.service" and "journalctl -xe" for details.
Started: 10:59:26.393206
Duration: 73.309 ms
Changes:
----------
ID: start_nut_server_service
Function: service.running
Name: nut-server
Result: True
Comment: Service restarted
Started: 10:59:26.501238
Duration: 913.472 ms
Changes:
----------
nut-server:
True
----------
ID: monitor_nut_server_service
Function: module.run
Result: True
Comment: monit.monitor: True
Started: 10:59:27.416727
Duration: 13.347 ms
Changes:
----------
monit.monitor:
True
----------
ID: start_nut_monitor_service
Function: service.running
Name: nut-monitor
Result: True
Comment: Service restarted
Started: 10:59:27.464851
Duration: 60.022 ms
Changes:
----------
nut-monitor:
True
----------
ID: monitor_nut_monitor_service
Function: module.run
Result: True
Comment: monit.monitor: True
Started: 10:59:27.525220
Duration: 12.108 ms
Changes:
----------
monit.monitor:
True
Summary for debian
-------------
Succeeded: 13 (changed=6)
Failed: 1
-------------
Total states run: 14
Total run time: 1.154 s in /usr/share/php/openmediavault/system/process.inc:196
Stack trace:
#0 /usr/share/php/openmediavault/engine/module/serviceabstract.inc(62): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(167): OMV\Engine\Module\ServiceAbstract->deploy()
#2 [internal function]: Engined\Rpc\Config->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(588): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusHh...', '/tmp/bgoutputws...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(189): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: Engined\Rpc\Config->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(537): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}
Alles anzeigen
systemctl status nut-driver.service shows:
root@omv-5:~# 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: exit-code) since Sat 2022-02-19 10:49:20 CET; 1min 17s ago
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: APC command table version 3.1
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: Unable to open 192.168.1.2: No such file or directory
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: Things to try:
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: - Check 'port=' in ups.conf
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: - Check owner/permissions of all parts of path
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: Driver failed to start (exit status=1)
Feb 19 10:49:20 omv-5 upsdrvctl[8062]: Network UPS Tools - UPS driver controller 2.7.4
Feb 19 10:49:20 omv-5 systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
Feb 19 10:49:20 omv-5 systemd[1]: nut-driver.service: Failed with result 'exit-code'.
Feb 19 10:49:20 omv-5 systemd[1]: Failed to start Network UPS Tools - power device driver controller.
Alles anzeigen
journalctl -xe shows me:
root@omv-5:~# journalctl -xe
Feb 19 11:00:27 omv-5 monit[4519]: 'nut-upsc-ups' status failed (1) -- Init SSL without certificate database
Error: Driver not connected
Feb 19 11:00:27 omv-5 monit[4519]: 'nut-upsc-ups' trying to restart
Feb 19 11:00:27 omv-5 monit[4519]: 'nut-upsc-ups' start: '/usr/sbin/upsdrvctl start'
Feb 19 11:00:32 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:00:37 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:00:42 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:00:47 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:00:52 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:00:57 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:00:58 omv-5 monit[4519]: 'nut-upsc-ups' status failed (1) -- Init SSL without certificate database
Error: Driver not connected
Feb 19 11:00:58 omv-5 monit[4519]: 'nut-upsc-ups' trying to restart
Feb 19 11:00:58 omv-5 monit[4519]: 'nut-upsc-ups' start: '/usr/sbin/upsdrvctl start'
Feb 19 11:01:02 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:07 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:12 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:17 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:22 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:27 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:28 omv-5 monit[4519]: 'nut-upsc-ups' status failed (1) -- Init SSL without certificate database
Error: Driver not connected
Feb 19 11:01:28 omv-5 monit[4519]: 'nut-upsc-ups' trying to restart
Feb 19 11:01:28 omv-5 monit[4519]: 'nut-upsc-ups' start: '/usr/sbin/upsdrvctl start'
Feb 19 11:01:32 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:37 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:42 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:47 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:52 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:57 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:01:58 omv-5 monit[4519]: 'nut-upsc-ups' status failed (1) -- Init SSL without certificate database
Error: Driver not connected
Feb 19 11:01:58 omv-5 monit[4519]: 'nut-upsc-ups' trying to restart
Feb 19 11:01:58 omv-5 monit[4519]: 'nut-upsc-ups' start: '/usr/sbin/upsdrvctl start'
Feb 19 11:02:02 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
Feb 19 11:02:07 omv-5 upsmon[10023]: Poll UPS [ups] failed - Driver not connected
lines 2132-2167/2167 (END)
Alles anzeigen
Anyone a idea how to fix this ?
you are using the wrong driver. If the UPS is on the network, use apcupsd
Hello Zoki
no luck with this:
root@omv-5:~# 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: exit-code) since Sat 2022-02-19 11:25:22 CET; 10s ago
Feb 19 11:25:22 omv-5 systemd[1]: Starting Network UPS Tools - power device driver controller...
Feb 19 11:25:22 omv-5 upsdrvctl[14530]: can't communicate with apcupsd!
Feb 19 11:25:22 omv-5 upsdrvctl[14530]: Network UPS Tools - apcupsd network client UPS driver 0.04 (2.7.4)
Feb 19 11:25:22 omv-5 upsdrvctl[14530]: Driver failed to start (exit status=1)
Feb 19 11:25:22 omv-5 upsdrvctl[14530]: Network UPS Tools - UPS driver controller 2.7.4
Feb 19 11:25:22 omv-5 systemd[1]: nut-driver.service: Control process exited, code=exited, status=1/FAILURE
Feb 19 11:25:22 omv-5 systemd[1]: nut-driver.service: Failed with result 'exit-code'.
Feb 19 11:25:22 omv-5 systemd[1]: Failed to start Network UPS Tools - power device driver controller.
Alles anzeigen
ifix it with this :
Hello Zoki
no luck with this:
Did you saw that you're setting an IP where it should be a port?!?
Set it to auto:
Hey Soma
to late fixed this above
I do have a BX1400U-GR which does not properly report input.voltage to nut but it works perfectly well with apcupsd.
If someone can report the EATON works with nut, i qould go for it. Otherwise you have to map apcupsd to nut or ignore wrong input voltage.
I just wanted to let you know:
Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!