Nut plugin no graph

g2_ufo · 4. November 2017

No gpaph after install nut plugin omv4

votdev · 4. November 2017

Fixed in openmediavault-nut 4.0.3, see https://github.com/openmediava…c4367b8d66a78473d32edb6b0.

g2_ufo · 5. November 2017

Openmediavault-nut 4.0.3 has new issue

votdev · 5. November 2017

Sad to hear. Currently i'm not able to test this plugin, so things like this might happen. I'm looking how to fix it.

votdev · 5. November 2017

OK, now finally fixed (https://github.com/openmediava…8fe2149be328c32b0bae7b3ac).

g2_ufo · 5. November 2017

Zitat von votdev

Fixed in openmediavault-nut 4.0.3, see https://github.com/openmediava…c4367b8d66a78473d32edb6b0.

Yes, fix now

g2_ufo · 22. November 2017

New strange issue with service status info in omv web- it is red, but services are started and ups shows full info:

Spoiler anzeigen

g2_ufo · 22. November 2017

New strange issue with service status info in omv web- it is red, but services are started and ups shows full info with upsc command.

mikebetz42 · 25. November 2017

Zitat von g2_ufo

New strange issue with service status info in omv web- it is red, but services are started and ups shows full info with upsc command.

I'm having the same issue, and after a while the UPS/NUT stop working. It could be an issue with NUT itself and not a OMV issue., as my OMV 3.x install is working fine with the same setup. The UPS communication is over SNMP on the lan. Not sure how to go about troubleshooting this one myself.

device.model: Eaton 5PX 1500
device.type: ups

driver.name: snmp-ups

g2_ufo · 26. November 2017

After 4.0.12 update still error in web gui

votdev · 26. November 2017

We can not see on your system, so the best way to help YOU AND the community would be to find out the problem on your system and open a bugreport with detailed information what has to be fixed to get it running ON YOUR system. After that we can destill the information to fix the plugin in general.
Check the syslog and 'systemctl status xxx.service' output to find out what is going wrong on your system.

g2_ufo · 27. November 2017

Service status:

Code

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 Sun 2017-11-26 18:21:04 MSK; 16h ago
 Main PID: 27589 (upsd)
    Tasks: 1 (limit: 4915)
   Memory: 748.0K
      CPU: 13.700s
   CGroup: /system.slice/nut-server.service
           └─27589 /lib/nut/upsd


ноя 26 18:21:04 nas systemd[1]: Starting Network UPS Tools - power devices information server...
ноя 26 18:21:04 nas upsd[27588]: fopen /var/run/nut/upsd.pid: No such file or directory
ноя 26 18:21:04 nas upsd[27588]: listening on 127.0.0.1 port 3493
ноя 26 18:21:04 nas upsd[27588]: listening on 127.0.0.1 port 3493
ноя 26 18:21:04 nas upsd[27588]: Connected to UPS [ups]: usbhid-ups-ups
ноя 26 18:21:04 nas upsd[27588]: Connected to UPS [ups]: usbhid-ups-ups
ноя 26 18:21:04 nas upsd[27589]: Startup successful
ноя 26 18:21:04 nas systemd[1]: Started Network UPS Tools - power devices information server.
ноя 26 18:21:04 nas upsd[27589]: User monmaster@127.0.0.1 logged into UPS [ups]

Alles anzeigen

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: active (running) since Sun 2017-11-26 18:21:04 MSK; 16h ago
 Main PID: 27587 (usbhid-ups)
    Tasks: 1 (limit: 4915)
   Memory: 820.0K
      CPU: 6.014s
   CGroup: /system.slice/nut-driver.service
           └─27587 /lib/nut/usbhid-ups -a ups


ноя 26 18:21:01 nas systemd[1]: Starting Network UPS Tools - power device driver controller...
ноя 26 18:21:02 nas upsdrvctl[27567]: Using subdriver: CyberPower HID 0.4
ноя 26 18:21:02 nas upsdrvctl[27567]: Network UPS Tools - Generic HID driver 0.41 (2.7.4)
ноя 26 18:21:02 nas upsdrvctl[27567]: USB communication driver 0.33
ноя 26 18:21:04 nas usbhid-ups[27587]: Startup successful
ноя 26 18:21:04 nas upsdrvctl[27567]: Network UPS Tools - UPS driver controller 2.7.4
ноя 26 18:21:04 nas systemd[1]: Started Network UPS Tools - power device driver controller.

Alles anzeigen

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 Sun 2017-11-26 18:21:04 MSK; 16h ago
 Main PID: 27604 (upsmon)
    Tasks: 2 (limit: 4915)
   Memory: 2.9M
      CPU: 3.651s
   CGroup: /system.slice/nut-monitor.service
           ├─27603 /lib/nut/upsmon
           └─27604 /lib/nut/upsmon


ноя 26 18:21:04 nas systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller...
ноя 26 18:21:04 nas upsmon[27602]: fopen /var/run/nut/upsmon.pid: No such file or directory
ноя 26 18:21:04 nas upsmon[27602]: UPS: ups@localhost (master) (power value 1)
ноя 26 18:21:04 nas upsmon[27602]: Using power down flag file /etc/killpower
ноя 26 18:21:04 nas systemd[1]: nut-monitor.service: PID file /var/run/nut/upsmon.pid not readable (yet?) after start: No such file or directory
ноя 26 18:21:04 nas upsmon[27603]: Startup successful
ноя 26 18:21:04 nas systemd[1]: nut-monitor.service: Supervising process 27604 which is not our child. We'll most likely not notice when it exits.
ноя 26 18:21:04 nas systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller.
ноя 26 18:21:04 nas upsmon[27604]: Init SSL without certificate database
ноя 26 18:21:05 nas systemd[1]: nut-monitor.service: Supervising process 27604 which is not our child. We'll most likely not notice when it exits.

Alles anzeigen

Last log:

Code

Nov 26 18:21:01 nas upsd[1401]: mainloop: Interrupted system call
Nov 26 18:21:01 nas upsd[1401]: Signal 15: exiting
Nov 26 18:21:01 nas upsmon[1406]: Signal 15: exiting
Nov 26 18:21:04 nas upsd[27588]: fopen /var/run/nut/upsd.pid: No such file or directory
Nov 26 18:21:04 nas upsd[27588]: listening on 127.0.0.1 port 3493
Nov 26 18:21:04 nas upsd[27588]: listening on 127.0.0.1 port 3493
Nov 26 18:21:04 nas upsd[27588]: Connected to UPS [ups]: usbhid-ups-ups
Nov 26 18:21:04 nas upsd[27588]: Connected to UPS [ups]: usbhid-ups-ups
Nov 26 18:21:04 nas upsd[27589]: Startup successful
Nov 26 18:21:04 nas upsmon[27602]: fopen /var/run/nut/upsmon.pid: No such file or directory
Nov 26 18:21:04 nas upsmon[27602]: UPS: ups@localhost (master) (power value 1)
Nov 26 18:21:04 nas upsmon[27602]: Using power down flag file /etc/killpower
Nov 26 18:21:04 nas upsmon[27603]: Startup successful
Nov 26 18:21:04 nas upsmon[27604]: Init SSL without certificate database
Nov 26 18:21:04 nas upsd[27589]: User monmaster@127.0.0.1 logged into UPS [ups]

Alles anzeigen

votdev · 27. November 2017

What about

Bash

# monit summary
# monit status

g2_ufo · 27. November 2017

monit summary - see screen

monit status:

System 'nas' - running
Process 'rrdcached' - running
Process 'nut-server' - running
Process 'nut-monitor' - running
Process 'nginx' - running
Filesystem 'rootfs' - Accessible

and others - running /accessible/ok

votdev · 27. November 2017

The output wouldn't be that much different, but to be sure:

Bash

# monit -B summary

g2_ufo · 27. November 2017

Code

Service Name                     Status                      Type
 nas                              Running                     System
 rrdcached                        Running                     Process
 php-fpm                          Running                     Process
 nut-server                       Running                     Process
 nut-monitor                      Running                     Process
 nginx                            Running                     Process
 omv-engined                      Running                     Process
 collectd                         Running                     Process
 rootfs                           Accessible                  Filesystem
 filesystem_srv_dev-disk-by-l...  Accessible                  Filesystem
 filesystem_srv_dev-disk-by-i...  Accessible                  Filesystem
 mountpoint_srv_dev-disk-by-l...  Status ok                   Program
 mountpoint_srv_dev-disk-by-i...  Status ok                   Program

Alles anzeigen

votdev · 27. November 2017

Fixed in openmediavault 4.0.13, see https://github.com/openmediava…b066e27bad42a75c3ea864a85.

g2_ufo · 27. November 2017

Zitat von votdev

Fixed in openmediavault 4.0.13, see https://github.com/openmediava…b066e27bad42a75c3ea864a85.

Yes, fixed!Many thanks!

mikebetz42 · 28. November 2017

Zitat von votdev

Fixed in openmediavault 4.0.13, see github.com/openmediavault/open…b066e27bad42a75c3ea864a85.

Fixed for me as well!

Thank you!

Jetzt mitmachen!