Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    NUT package (2.8.0 and below)

    Scheduled Pinned Locked Moved UPS Tools
    1.2k Posts 128 Posters 4.3m Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • dennypageD
      dennypage
      last edited by

      @cuco:

      So I did more research, did deeper looks into the code and found a bug in the nut-driver. Posted the issue on GitHub: https://github.com/networkupstools/nut/issues/460 then I fixed it: https://github.com/networkupstools/nut/pull/461/commits/b82b9cf3b4695f3171b6250af431a6a3f7fc81c4 and did a pull request: https://github.com/networkupstools/nut/pull/461
      It then has been reviewed and merged into nut https://github.com/networkupstools/nut/commit/bc6ca11be42281e6d7f36dc6cf2860c2fe950f66

      Awesome!

      1 Reply Last reply Reply Quote 0
      • B
        bulldog5
        last edited by

        @dennypage:

        @bulldog5:

        @dennypage:

        @bulldog5:

        I plugged the UPS into a 2K12 server and installed CPs PowerPanel software, let it run for few days and didn't get any LOWBATT messages, then plugged it into my FreeNAS server which is using driver 2.7.3, internal driver .39. and no LOWBATT messages.

        So, something is not the same after the upgrade on pfsense because i dont see the LOWBATT message on 2 other boxes.  Going to try mirroring the freenas NUT configs, (being doubtful that will matter) then going to have to find some time to reinstall pfsense to 2.3.2 and go from there).

        When you put it back on the pfSense box did the LOWBATT messages immediately return?

        No

        Bulldog, did your issue get resolved?

        Hi, it seems that adjusting the following has kept it quiet. Thanks again.
        battery.charge.low: 20
        battery.charge.warning: 25

        1 Reply Last reply Reply Quote 0
        • dennypageD
          dennypage
          last edited by

          @bulldog5:

          Hi, it seems that adjusting the following has kept it quiet. Thanks again.
          battery.charge.low: 20
          battery.charge.warning: 25

          Cool. You are quite welcome. Thanks for letting me know.

          1 Reply Last reply Reply Quote 0
          • dennypageD
            dennypage
            last edited by

            Just FYI, the PR for the dummy driver has gone in. The shutdown issue will have to be addressed in a follow-on release. This issue will need an enhancement in the core so it may have to wait until 2.4 is release.

            1 Reply Last reply Reply Quote 0
            • W
              wishyou
              last edited by

              @dennypage:

              I have. The power kill logic is gone from the base os level. Still searching to find out when and why.

              Being a long time NUT user with pfSense this made me curious. Is this a new problem recently?
              I've been adding stuff to rc.shutdown for "ages" to get proper shutdown-killpower-restart loops with a couple of APC serial ups-es:

              
              #Final shutdown stuff, UPS
              if /usr/local/sbin/upsmon -K; then
              
                  # Warning message
              	echo "POWERDOWNFLAG detected - Power cycling the UPS loads..."
              
                  # Do shutdown
                  /usr/local/sbin/upsdrvctl shutdown
              
                  #Might be needed for power races
                  # /bin/sleep 180
                  # /sbin/reboot
              fi
              
              
              1 Reply Last reply Reply Quote 0
              • dennypageD
                dennypage
                last edited by

                The problem pre dates the current generation of the NUT package, but I'm not sure how far back it goes.

                What needs to be done is pretty much the same thing you are doing with your patch to rc.shutdown, except that I need to genericize it so that it can be used with other packages such as apcupsd.

                1 Reply Last reply Reply Quote 0
                • W
                  wishyou
                  last edited by

                  OK, thanks for the update
                  And nice to know that I didn't misunderstand anything with my fix, although it would be nice not having to remember the manual rc.shutdown patch every time pfSense is updated.

                  Thanks, keep up the good work!

                  1 Reply Last reply Reply Quote 0
                  • B
                    bdf0506
                    last edited by

                    I upgraded NUT on pfSense to latest 2.7.4_5, and ever since I did that, it seems there is a high uptick in UPS communication errors. It's possible that it's another environmental condition that is going on here, but wanted to see if anyone else has had issues. PfSense is running on a small physical box, and it is directly connected via USB to a CyberPower EC650.

                    I've been getting flooded with emails as a result of this (yes, I know that I can turn them off). But it points to something else that is going on. Here is a dump of the ups related events for a small window on 9/4. In the last 24 hours, I have 232 events that are the Permission denied error.

                    One thing I did notice, if you look in /usr/local/etc/nut, all the *.conf files have perms of 640, but all the *.conf.sample files have perms of 644. Not sure if that matters or not, and also not sure if that's "new" or not.

                    Sep  4 19:36:09 upsmon[32699]: Communications with UPS ups established
                    Sep  4 19:36:09 upsmon[32699]: Communications with UPS ups established
                    Sep  4 19:36:09 upsd[73255]: User monuser@::1 logged into UPS [ups]
                    Sep  4 19:36:09 upsd[73255]: User monuser@::1 logged into UPS [ups]
                    Sep  4 19:36:04 upsmon[32699]: Communications with UPS ups lost
                    Sep  4 19:36:04 upsmon[32699]: Communications with UPS ups lost
                    Sep  4 19:36:04 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                    Sep  4 19:36:04 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                    Sep  4 19:32:48 upsmon[32699]: Communications with UPS ups established
                    Sep  4 19:32:48 upsmon[32699]: Communications with UPS ups established
                    Sep  4 19:32:48 upsd[73255]: User monuser@::1 logged into UPS [ups]
                    Sep  4 19:32:48 upsd[73255]: User monuser@::1 logged into UPS [ups]
                    Sep  4 19:32:43 upsmon[32699]: Communications with UPS ups lost
                    Sep  4 19:32:43 upsmon[32699]: Communications with UPS ups lost
                    Sep  4 19:32:43 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                    Sep  4 19:32:43 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                    Sep  4 19:30:12 upsmon[32699]: Communications with UPS ups established
                    Sep  4 19:30:12 upsmon[32699]: Communications with UPS ups established
                    Sep  4 19:30:12 upsd[73255]: User monuser@::1 logged into UPS [ups]
                    Sep  4 19:30:12 upsd[73255]: User monuser@::1 logged into UPS [ups]
                    Sep  4 19:30:07 upsmon[32699]: Communications with UPS ups lost
                    Sep  4 19:30:07 upsmon[32699]: Communications with UPS ups lost
                    Sep  4 19:30:07 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                    Sep  4 19:30:07 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                    
                    
                    1 Reply Last reply Reply Quote 0
                    • B
                      bdf0506
                      last edited by

                      @bdf0506:

                      I upgraded NUT on pfSense to latest 2.7.4_5, and ever since I did that, it seems there is a high uptick in UPS communication errors. It's possible that it's another environmental condition that is going on here, but wanted to see if anyone else has had issues. PfSense is running on a small physical box, and it is directly connected via USB to a CyberPower EC650.

                      I've been getting flooded with emails as a result of this (yes, I know that I can turn them off). But it points to something else that is going on. Here is a dump of the ups related events for a small window on 9/4. In the last 24 hours, I have 232 events that are the Permission denied error.

                      One thing I did notice, if you look in /usr/local/etc/nut, all the *.conf files have perms of 640, but all the *.conf.sample files have perms of 644. Not sure if that matters or not, and also not sure if that's "new" or not.

                      Sep  4 19:36:09 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:36:09 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:36:09 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:36:09 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:36:04 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:36:04 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:36:04 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:36:04 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:32:48 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:32:48 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:32:48 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:32:48 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:32:43 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:32:43 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:32:43 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:32:43 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:30:12 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:30:12 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:30:12 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:30:12 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:30:07 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:30:07 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:30:07 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:30:07 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      
                      

                      Okay, this isn't a NUT issue.

                      I dove deeper into the logging before these errors hit, and I see each time a log line like this:

                      Sep  4 19:32:37 dpinger: Mobility_Server 192.168.35.21: Alarm latency 266us stddev 32us loss 21%
                      

                      After that line, bad things were happening. I'm surprised I wasn't having other network issues - I probably was, just unknown to me.

                      Sep  4 19:32:48 php-cgi: nut_email.php: Message sent to <redacted>@gmail.com OK
                      Sep  4 19:32:48 php-cgi: nut_email.php: Message sent to <redacted>@gmail.com OK
                      Sep  4 19:32:48 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:32:48 upsmon[32699]: Communications with UPS ups established
                      Sep  4 19:32:48 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:32:48 upsd[73255]: User monuser@::1 logged into UPS [ups]
                      Sep  4 19:32:43 php-cgi: nut_email.php: Message sent to <redacted>@gmail.com OK
                      Sep  4 19:32:43 php-cgi: nut_email.php: Message sent to <redacted>@gmail.com OK
                      Sep  4 19:32:43 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:32:43 upsmon[32699]: Communications with UPS ups lost
                      Sep  4 19:32:43 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:32:43 upsmon[32699]: Poll UPS [ups] failed - Write error: Permission denied
                      Sep  4 19:32:38 php-fpm[30305]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use Mobility_Server.
                      Sep  4 19:32:38 php-fpm[30305]: /rc.openvpn: OpenVPN: One or more OpenVPN tunnel endpoints may have changed its IP. Reloading endpoints that may use Mobility_Server.
                      Sep  4 19:32:37 check_reload_status: Reloading filter
                      Sep  4 19:32:37 check_reload_status: Reloading filter
                      Sep  4 19:32:37 check_reload_status: Restarting OpenVPN tunnels/interfaces
                      Sep  4 19:32:37 check_reload_status: Restarting OpenVPN tunnels/interfaces
                      Sep  4 19:32:37 check_reload_status: Restarting ipsec tunnels
                      Sep  4 19:32:37 check_reload_status: Restarting ipsec tunnels
                      Sep  4 19:32:37 check_reload_status: updating dyndns Mobility_Server
                      Sep  4 19:32:37 check_reload_status: updating dyndns Mobility_Server
                      Sep  4 19:32:37 dpinger: Mobility_Server 192.168.35.21: Alarm latency 266us stddev 32us loss 21%</redacted></redacted></redacted></redacted>
                      

                      The fix was to go into the gateways, and disable the gateway checking on 192.168.35.21. I still don't know what was causing that in the first place, but that's not something that needs to be addressed in the NUT forum.

                      1 Reply Last reply Reply Quote 0
                      • P
                        pigbrother
                        last edited by

                        dennypage, thanks for your great job!

                        My old Back-UPS RS 1000 connected to pfsense working great, but once or few times a day shows the following in the log\email:
                        Sep 6 10:47:16 upsmon 42126 UPS Back-UPS_RS_1000 on battery
                        Sep 6 10:47:21 upsmon 42126 UPS Back-UPS_RS_1000 on line power.

                        Time is always random, but event duration is always 5 seconds exactly.

                        My settings:
                        ups.conf

                        [Back-UPS_RS_1000]
                        driver=usbhid-ups
                        port=auto
                        ignorelb
                        override.battery.charge.low = 30
                        override.battery.runtime.low = 300
                        

                        upsmon.conf

                        MONITOR Back-UPS_RS_1000 1 monuser 7504xxxxxxxxxxxx master
                        SHUTDOWNCMD "/sbin/shutdown -p +0"
                        POWERDOWNFLAG /etc/killpower
                        NOTIFYCMD /usr/local/pkg/nut/nut_email.php
                        NOTIFYFLAG ONLINE   SYSLOG+WALL+EXEC
                        NOTIFYFLAG ONBATT   SYSLOG+WALL+EXEC
                        NOTIFYFLAG LOWBATT  SYSLOG+WALL+EXEC
                        NOTIFYFLAG FSD	  SYSLOG+WALL+EXEC
                        NOTIFYFLAG COMMOK   SYSLOG+WALL+EXEC
                        NOTIFYFLAG COMMBAD  SYSLOG+WALL+EXEC
                        NOTIFYFLAG SHUTDOWN SYSLOG+WALL+EXEC
                        NOTIFYFLAG REPLBATT SYSLOG+WALL+EXEC
                        NOTIFYFLAG NOCOMM   SYSLOG+WALL+EXEC
                        NOTIFYFLAG NOPARENT SYSLOG+WALL+EXEC
                        RUN_AS_USER root
                        
                        

                        I realize that is UPS problem but apart from that it works fine.
                        Are there any NUT tweaks to avoid such behavior?

                        1 Reply Last reply Reply Quote 0
                        • dennypageD
                          dennypage
                          last edited by

                          @pigbrother:

                          dennypage, thanks for your great job!

                          My old Back-UPS RS 1000 connected to pfsense working great, but once or few times a day shows the following in the log\email:
                          Sep 6 10:47:16 upsmon 42126 UPS Back-UPS_RS_1000 on battery
                          Sep 6 10:47:21 upsmon 42126 UPS Back-UPS_RS_1000 on line power.

                          Time is always random, but event duration is always 5 seconds exactly.

                          …

                          I realize that is UPS problem but apart from that it works fine.
                          Are there any NUT tweaks to avoid such behavior?

                          You're welcome!

                          The event itself may be very brief in duration, but is logged as 5 seconds due to the polling interval. There are several reasons that a momentary transfer to battery can happen depending upon the UPS.

                          Some UPSs allow the variables which control transfer to be changed. The complete list of variables supported by NUT can be found here. To see what your UPS actually supports, use the upsc command. For transfer items, look for variables "input sensitivity" or "input.transfer…"

                          Be careful with these. :)

                          1 Reply Last reply Reply Quote 0
                          • P
                            pigbrother
                            last edited by

                            My UPS variables:

                            battery.charge: 100
                            battery.charge.low: 30
                            battery.charge.warning: 50
                            battery.date: 2001/09/25
                            battery.mfr.date: 2016/10/10
                            battery.runtime: 5798
                            battery.runtime.low: 300
                            battery.type: PbAc
                            battery.voltage: 26.9
                            battery.voltage.nominal: 24.0
                            device.mfr: American Power Conversion
                            device.model: Back-UPS RS 1000
                            device.serial:xxxxxxxxxx
                            device.type: ups
                            driver.flag.ignorelb: enabled
                            driver.name: usbhid-ups
                            driver.parameter.pollfreq: 30
                            driver.parameter.pollinterval: 2
                            driver.parameter.port: auto
                            driver.parameter.synchronous: no
                            driver.version: 2.7.4
                            driver.version.data: APC HID 0.96
                            driver.version.internal: 0.41
                            input.sensitivity: medium
                            input.transfer.high: 264
                            input.transfer.low: 194
                            input.transfer.reason: input voltage out of range
                            input.voltage: 228.0
                            input.voltage.nominal: 230
                            ups.beeper.status: enabled
                            ups.delay.shutdown: 20
                            ups.firmware: 7.g8 .I
                            ups.firmware.aux: g8
                            ups.load: 5
                            ups.mfr: American Power Conversion
                            ups.mfr.date: 2004/07/28
                            ups.model: Back-UPS RS 1000
                            ups.productid: 0002
                            ups.realpower.nominal: 600
                            ups.serial: xxxxxxxxxxxx
                            ups.status: OL
                            ups.test.result: No test initiated
                            ups.timer.reboot: 0
                            ups.timer.shutdown: -1
                            ups.vendorid: 051d
                            

                            input.transfer.reason: input voltage out of range - probably is the event reason?

                            I believe that
                            input.transfer.high:264 and  input.transfer.low:194
                            are just voltage threshold? Am I right?

                            Should  I try change input.sensitivity to low? If so - where to put it in NUT settings page?

                            1 Reply Last reply Reply Quote 0
                            • D
                              doktornotor Banned
                              last edited by

                              Why would you be doing any such thing? The UPS is doing its job, just leave it alone.

                              1 Reply Last reply Reply Quote 0
                              • dennypageD
                                dennypage
                                last edited by

                                @pigbrother:

                                nput.transfer.reason: input voltage out of range - probably is the event reason?

                                I believe that
                                input.transfer.high:264 and  input.transfer.low:194
                                are just voltage threshold? Am I right?

                                Should  I try change input.sensitivity to low? If so - where to put it in NUT settings page?

                                Yes, those are the voltage levels that will trigger transfer.

                                Setting UPS variables is not something that you do in your NUT config. You set them in the UPS using the upsrw command.

                                As Dok notes, the UPS is doing it's job, protecting the attached systems from excessive power fluctuations. You might want to investigate the source of the voltage problem before turning down the sensitivity. Consulting with the UPS manufacturer might be a good idea as well.

                                1 Reply Last reply Reply Quote 0
                                • P
                                  pigbrother
                                  last edited by

                                  dennypaged, oktornotor, thanks for answers.
                                  Agreed,  the UPS is doing it's job. I'm just trying to avoid annoying mail reports (at the night time especially).
                                  Another SMART UPSes connected  to same power input do not have any complains about power conditions.

                                  1 Reply Last reply Reply Quote 0
                                  • S
                                    SilverJS
                                    last edited by

                                    Denny (or whoever else wants to lend a hand!),

                                    Running pfSense 2.4.1 as a firewall and router, with NUT 2.7.4_5.  I have the pfSense box, a FreeNAS server, and another FreeNAS server (Replication target) all on a CyberPower CP1000AVRLCD UPS.  (My switch is also on that, a 16-port Netgear item.)  I currently have my FreeNAS server as the master, and both the backups box and pfSense are "seeing" the master no problem.  When I pull the cord on the UPS, I get three nice e-mail notifications (one from each of the boxes), and all boxes shutdown in an orderly fashion when ordered to by the master (tested both Battery Low and On Battery, the latter with a 10 second timer in my tests).

                                    The problem is : none of the boxes start back up when I plug the UPS back in!  I'm sure this is something dumb, because I'm not that knowledgeable at all - but what I CAN say is, the blue LED is lit on the UPS (but the display itself is blank).  As in, it's not shut down.  If I press it, it goes completely dark, and if I press it again, it lights up again, along with the LCD display and all - and, voila, most of the boxes start up.  That is, both FreeNAS boxes start up - the pfSense one needs to be started manually.  All three boxes have Always On setting in the BIOS for waking up after power loss.

                                    Any ideas…?  I think it would make more sense to have the box doing the routing (pfSense) also being the master, but I'm not 100% sure how to configure that.  But the better question is - do I need to?  Would that fix anything?

                                    Thanks in advance, and thanks also both for all your work on this package, and for the continued support you offer to us plebes on this forum! =)

                                    Cheers!

                                    pfSense Rig : SuperMicro X8SIL-F with X3430 Xeon CPU, Shuriken cooler | 12 Gb ECC RAM | Kingston 64GB SSD | Antec VP450 P/S | Silverstone ML03B Case

                                    1 Reply Last reply Reply Quote 0
                                    • dennypageD
                                      dennypage
                                      last edited by

                                      Can you clarify what you mean by “the pfSense one needs to be started manually”?

                                      Traveling, so expect delayed responses…

                                      Thanks.

                                      1 Reply Last reply Reply Quote 0
                                      • S
                                        SilverJS
                                        last edited by

                                        Thanks for the quick reply - far from "delayed"!

                                        I mean I have to physically push the power button on the pfSense box.

                                        Enjoy your travels!

                                        pfSense Rig : SuperMicro X8SIL-F with X3430 Xeon CPU, Shuriken cooler | 12 Gb ECC RAM | Kingston 64GB SSD | Antec VP450 P/S | Silverstone ML03B Case

                                        1 Reply Last reply Reply Quote 0
                                        • B
                                          bdf0506
                                          last edited by

                                          @SilverJS:

                                          Thanks for the quick reply - far from "delayed"!

                                          I mean I have to physically push the power button on the pfSense box.

                                          Enjoy your travels!

                                          This is kind of a known issue…what should happen is that the master should shut down the UPS before the UPS fully drains. In your case, the master is your free NAS so you likely need to look there.

                                          I reported this issue back in June or so. Now that 2.4 is out I believe a bug fix for the nut package for pfSense can be released to fix this on the pfSense side. But I don’t think this will help you out, as it sounds like the freeNAS isn’t shutting down the UPS prior to fully draining it.

                                          1 Reply Last reply Reply Quote 0
                                          • S
                                            SilverJS
                                            last edited by

                                            @bdf0506:

                                            This is kind of a known issue…what should happen is that the master should shut down the UPS before the UPS fully drains. In your case, the master is your free NAS so you likely need to look there.

                                            I reported this issue back in June or so. Now that 2.4 is out I believe a bug fix for the nut package for pfSense can be released to fix this on the pfSense side. But I don’t think this will help you out, as it sounds like the freeNAS isn’t shutting down the UPS prior to fully draining it.

                                            Oh!  So the UPS NEEDS to be shut down too? Too easy - FreeNAS has a setting for that in the UPS settings.  I'll tick that box, try again and report.

                                            pfSense Rig : SuperMicro X8SIL-F with X3430 Xeon CPU, Shuriken cooler | 12 Gb ECC RAM | Kingston 64GB SSD | Antec VP450 P/S | Silverstone ML03B Case

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post
                                            Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.