need to upgrade nut tp 2.7.4 from 2.7.2

  • I seem to be suffering from this bug below
    https://bugzilla.redhat.com/show_bug.cgi?id=1365904


    the current version installed is


    ||/ Name Version Architecture Description
    +++-==============-============-============-=================================
    ii nut 2.7.2-4 all network UPS tools - metapackage


    I see in the log below, the following.
    2017-11-12T21:03:56+0100 nas systemd[1]: Starting Network UPS Tools - power device monitor and shutdown controller...
    2017-11-12T21:03:55+0100 nas systemd[1]: PID file /var/run/nut/upsmon.pid not readable (yet?) after start.
    2017-11-12T21:03:55+0100 nas systemd[1]: nut-monitor.service: Supervising process 1835 which is not our child. We'll most likely not notice when it exits.
    2017-11-12T21:03:55+0100 nas systemd[1]: Started Network UPS Tools - power device monitor and shutdown controller.
    2017-11-12T21:03:56+0100 nas upsmon[1829]: fopen /var/run/nut/upsmon.pid: No such file or directory
    2017-11-12T21:03:56+0100 nas upsmon[1829]: UPS: eapeups@localhost (master) (power value 1)
    2017-11-12T21:03:56+0100 nas upsmon[1829]: Using power down flag file /etc/killpower


    i see that the upsmon process is running as two different users, so i guess if the above is not the problem, then this must be.
    root@nas:~# ps aux | grep nut
    nut 1695 0.0 0.0 17156 1440 ? Ss 21:03 0:00 /lib/nut/usbhid-ups -a eapeups
    nut 1777 0.0 0.0 37708 1928 ? Ss 21:03 0:00 /lib/nut/upsd
    root 1832 0.0 0.0 37692 2152 ? Ss 21:03 0:00 /lib/nut/upsmon
    nut 1835 0.0 0.0 45440 2504 ? S 21:03 0:00 /lib/nut/upsmon
    root 6226 0.0 0.0 14200 2256 pts/0 S+ 21:35 0:00 grep nut


    ---- perhaps one other interesting thing. i nut the run user is nut for all but upsmon, but whereas the conf files are all owned by root:nut
    root@nas:/var/run/nut# ls -l
    total 12
    -rw-r--r-- 1 nut nut 5 Nov 12 22:01 upsd.pid
    -rw-r--r-- 1 root root 5 Nov 12 22:01 upsmon.pid
    srw-rw---- 1 nut nut 0 Nov 12 22:01 usbhid-ups-eapeups
    -rw-r--r-- 1 nut nut 5 Nov 12 22:01 usbhid-ups-eapeups.pid

  • I have the same version installed - and I have the same messages in my logfile. Also the output of the ps- and ls-commands are the same, with a different UPS of course.


    But my UPS is running flawlessly.


    What is your problem?

    OMV 3.0.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

  • All the graphics, etc work, so aside from the errors it seems to work alight.


    Having had a situation yet where the nas had to shutdown so can't confirm if there are any consequences in that regard,
    but if we know there is a bug there and there has been a fix for it, why wouldn't we implement it?

  • But are you sure that this problem still exists in OMV? However the services are running on my system:


    service --status-all | grep nut returns
     [ + ] nut-client
     [ + ] nut-server



    but if we know there is a bug there and there has been a fix for it, why wouldn't we implement it?

    Basically you are absolutely right!

    OMV 3.0.100 (Gray style)

    ASRock Rack C2550D4I C0-stepping - 16GB ECC - 6x WD RED 3TB (ZFS 2x3 Striped RaidZ1) - Fractal Design Node 304 -

    3x WD80EMAZ Snapraid / MergerFS-pool via eSATA - 4-Bay ICYCube MB561U3S-4S with fan-mod

Jetzt mitmachen!

Sie haben noch kein Benutzerkonto auf unserer Seite? Registrieren Sie sich kostenlos und nehmen Sie an unserer Community teil!