Openmediavault-NUT plugin

    • OMV 3.x
    • Resolved

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • Openmediavault-NUT plugin

      Hallo,
      ich hatte ein Problem mit dem NUT Plugin und meiner USV (Eaton S3 550) nach dem Aufwachen aus dem Standby erhielt ich immer folgende Fehlermeldungen:

      Display Spoiler

      Jan 2 06:00:01 Nas-TK upsd[2360]: Data for UPS [ups] is stale - check driver
      Jan 2 06:00:01 Nas-TK upsd[2360]: UPS [ups] data is no longer stale
      Jan 2 06:00:03 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Write error: Broken pipe
      Jan 2 06:00:03 Nas-TK upsmon[2363]: Communications with UPS ups@localhost lost
      Jan 2 06:00:03 Nas-TK upssched[10879]: Executing command: notify
      Jan 2 06:00:03 Nas-TK upssched-cmd: Communications with the UPS ups@localhost are lost
      Jan 2 06:00:08 Nas-TK upsd[2360]: User monmaster@127.0.0.1 logged into UPS [ups]
      Jan 2 06:00:08 Nas-TK upsmon[2363]: Communications with UPS ups@localhost established
      Jan 2 06:00:08 Nas-TK upssched[10923]: Executing command: notify
      Jan 2 06:00:08 Nas-TK upssched-cmd: Communications with the UPS ups@localhost are established
      Jan 3 06:00:01 Nas-TK upsd[2360]: Data for UPS [ups] is stale - check driver
      Jan 3 06:00:03 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Write error: Broken pipe
      Jan 3 06:00:03 Nas-TK upsmon[2363]: Communications with UPS ups@localhost lost
      Jan 3 06:00:03 Nas-TK upssched[10333]: Executing command: notify
      Jan 3 06:00:03 Nas-TK upssched-cmd: Communications with the UPS ups@localhost are lost
      Jan 3 06:00:08 Nas-TK upsd[2360]: User monmaster@127.0.0.1 logged into UPS [ups]
      Jan 3 06:00:08 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:08 Nas-TK upsmon[2363]: UPS ups@localhost is unavailable
      Jan 3 06:00:08 Nas-TK upssched[10405]: Executing command: notify
      Jan 3 06:00:08 Nas-TK upssched-cmd: Communications with the UPS ups@localhost cannot be established
      Jan 3 06:00:13 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:18 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:23 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:28 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:33 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:37 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:42 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:47 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:52 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:00:57 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:02 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:07 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:12 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:17 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:22 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:27 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:32 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:37 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:42 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:47 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:52 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:01:57 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:02 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:07 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:12 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:17 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:22 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:27 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:32 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:37 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:42 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:47 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:52 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:02:57 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:02 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:07 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:12 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:17 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:22 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:27 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:32 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:37 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:42 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:47 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:52 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:03:57 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:02 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:07 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:12 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:17 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:22 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:27 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:32 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:37 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:42 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:47 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:52 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:04:57 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:05:02 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:05:07 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:05:12 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:05:12 Nas-TK upsmon[2363]: UPS ups@localhost is unavailable
      Jan 3 06:05:12 Nas-TK upssched[12209]: Executing command: notify
      Jan 3 06:05:12 Nas-TK upssched-cmd: Communications with the UPS ups@localhost cannot be established
      Jan 3 06:05:17 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:05:22 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale
      Jan 3 06:05:27 Nas-TK upsmon[2363]: Poll UPS [ups@localhost] failed - Data stale

      Der Fehler ließ sich danach nur mit einem Aus- und Wiedereinschalten des Plugins über die GUI beheben.

      Ein Lösung fand ich auf der FAQ Seite vom Network UPS Tool

      Display Spoiler

      13. What’s this about data stale?

      It means your UPS driver hasn’t updated things in a little while. upsd refuses to serve up data that isn’t fresh, so you get the errors about staleness.
      If this happens to you, make sure your driver is still running. Also look at the syslog. Sometimes the driver loses the connection to the UPS, and that will also make the data go stale.
      This might also happen on certain virtualization platforms. If you cannot reproduce the problem on a physical machine, please report the bug to the virtualization software vendor.
      If this happens a lot, you might consider cranking up DEADTIME in the upsmon.conf to suppress some of the warnings for shorter intervals. Use caution when adjusting this number, since it directly affects how long you run on battery without knowing what’s going on with the UPS.
      Note: some drivers occasionally need more time to update than the default value of MAXAGE (in upsd.conf) allows. As a result, they are temporarily marked stale even though everything is fine. This can happen with MGE Ellipse equipment - see the mge-shut or usbhid-ups man pages. In such cases, you can raise the value of MAXAGE to avoid these warnings; try a value like 25 or 30.

      Als ich in der Datei UPSD.CONF den Eintrag MAXAGE von 15 auf 25 erhöht habe funktioniert alles wie gewünscht.

      Ich habe nur noch das Problem wenn ich das Plugin über die GUI ändern möchte wird der MAXAGE Wert wieder auf die Default Einstellung von 15 geändert.
      Gibt es eine Möglichkeit dieses Verhalten zu verhindern? Es wäre auch super wenn sich der Wert über die GUI editieren ließe.
      OMV-Server: MSI H110I-PRO | Intel G4400 | 8 GB DDR 4 | 1x Intel SSD 600p M.2 PCIe 128GB | 3x WD Red 3TB, Snapraid / mergerfs |
      omv 3.0.59 erasmus | 64 bit | 4.8 backport kernel | omvextrasorg 3.4.15
    • Have a look here: github.com/openmediavault/open…mediavault/mkconf/nut#L41

      You can use the environment variable to customize your needs. Check the forum how to do that.
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit
    • Sorry das ich nochmals nachfragen muss.
      Reicht es den folgenden Text unter /etc/default/openmediavault einzufügen

      OMV_NUT_UPSD_MAXAGE=${OMV_NUT_UPSD_MAXAGE:-"25"}

      oder müssen noch weitere Passagen übernommen werden.
      OMV-Server: MSI H110I-PRO | Intel G4400 | 8 GB DDR 4 | 1x Intel SSD 600p M.2 PCIe 128GB | 3x WD Red 3TB, Snapraid / mergerfs |
      omv 3.0.59 erasmus | 64 bit | 4.8 backport kernel | omvextrasorg 3.4.15
    • Source Code

      1. OMV_NUT_UPSD_MAXAGE="25"
      Anschließend die Konfiguration bauen und die Dienste neu starten.

      Shell-Script

      1. omv-mkconf nut
      2. systemctl restart nut-monitor
      3. systemctl restart nut-server
      Absolutely no support through PM!

      I must not fear.
      Fear is the mind-killer.
      Fear is the little-death that brings total obliteration.
      I will face my fear.
      I will permit it to pass over me and through me.
      And when it has gone past I will turn the inner eye to see its path.
      Where the fear has gone there will be nothing.
      Only I will remain.

      Litany against fear by Bene Gesserit