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.2m 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.
    • L
      lcbbcl @dennypage
      last edited by lcbbcl

      @dennypage said in NUT package:

      @lcbbcl I'm looking for messages from "usbhid-ups". I don't need anything from "upsd" or "upsmon".

      Also, I note in your former post your advanced section is cut off... but it is expanded which would indicate that you have something set in there. Can you confirm if you have anything in the advanced section at all?
      I have only Feb 19 20:35:00 upsd 30880 Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
      msg whith usbhid-ups

      In advance section i set only what interface to use to listen and users

      dennypageD 1 Reply Last reply Reply Quote 1
      • T
        tman222 @dennypage
        last edited by

        @dennypage said in NUT package:

        For anyone else who is having the signal 10/11 issue with usbhid-ups, are able to do a complete reinstall?

        If so, could you report back after doing so?

        Thanks!

        Unfortunately, in my case I'm dealing with a custom build so there is no direct path to install 23.01. If I recall correctly, isn't it still 2.60 CE > 22.05 > 23.01? If that's the case, I'm not sure it would necessarily fix the problem since it still an upgrade vs. a fresh install.

        For good measure, I did try uninstalling the NUT package, rebooting, reinstalling, rebooting again, but still end up with the same signal 10/11 issue unless I run NUT with the interruptonly flag. When the NUT package is uninstalled, is there anything left behind that can be removed manually? The one thing that I have not tried yet is simply switching the USB port on the back of the system to see if that might fix it.

        dennypageD 2 Replies Last reply Reply Quote 1
        • dennypageD
          dennypage @tman222
          last edited by

          @tman222 I can't advise you on the upgrade path, but based on what is currently known with a fresh re-install fixing the issue, I have assume that the issue is kernel or libusb related. Re-install of nut will not have any effect on that.

          There have been several reports of upgrades not fully completing, so I think a re-install is a good idea.

          The best that I can recommend is reaching out to Netgate for advice on how to do a fresh install. I'm sure there is some way to accomplish it.

          1 Reply Last reply Reply Quote 1
          • JonathanLeeJ
            JonathanLee @dennypage
            last edited by

            @dennypage I spoke to soon its back. . . :(

            Make sure to upvote

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

              @jonathanlee said in NUT package:

              its back. . . :(

              Sigh. That's unfortunate. Back on the path of getting a debug build I guess.

              S 1 Reply Last reply Reply Quote 1
              • dennypageD
                dennypage @tman222
                last edited by

                @tman222 Hey, I'm sorry if you mentioned this before and I missed it, but could you share some information on the kind of hardware you are running pfSense on? Is it Intel or Arm based? Thanks

                T keyserK 2 Replies Last reply Reply Quote 1
                • S
                  shaffergr @dennypage
                  last edited by

                  @dennypage

                  so rebooted XG-7100 back into 22.05 (thanks to ZFS) and confirmed nut package and USB drivers work as expected. Rebooted back into 23.01 and same - exit on signal 10.

                  Some data points:

                  My NAS runs TrueNAS Core 13.0-U3.1, which os based on FreeBSD 13.1-RELEASE-p2. It is connected to a 1U CyberPower 700VA UPS via nut and it is also working as expected - no issues.

                  If I connect the 700VA UPS to my XG-7100 I get the same results - exit on signal 10. If I connect the 500VA UPS (normally connected to the XG-7100) to my TrueNAS server, works as expected - no issues and reports correct information.

                  Also, I have connected the USB cable of both UPS to both USB 2.0 ports on my XG-7100 with the same results - eventually exits on signal 10.

                  so...

                  nut package and USB devices look to work correctly under FreeBSD 12.3-STABLE and FreeBSD-13.1-RELEASE. Issue must be with FreeBSD-14-CURRENT.

                  dennypageD 1 Reply Last reply Reply Quote 2
                  • T
                    tman222 @dennypage
                    last edited by

                    @dennypage said in NUT package:

                    @tman222 Hey, I'm sorry if you mentioned this before and I missed it, but could you share some information on the kind of hardware you are running pfSense on? Is it Intel or Arm based? Thanks

                    Hi @dennypage - this particular system that is seeing the signal 10 errors is based on newer Intel based hardware (running on an 10th gen Intel Core i3 CPU). It looks like it continues to run fine using the interruptonly flag as additional input to the NUT usbhid-ups driver (no disconnections/crashes yet). Please let me know if the NUT status screenshots would still be helpful to have.

                    S dennypageD 2 Replies Last reply Reply Quote 1
                    • S
                      shaffergr @tman222
                      last edited by

                      @tman222

                      where do you put the interruptonly flag in the nut config gui?

                      T 1 Reply Last reply Reply Quote 1
                      • T
                        tman222 @shaffergr
                        last edited by

                        @shaffergr said in NUT package:

                        @tman222

                        where do you put the interruptonly flag in the nut config gui?

                        Hi @shaffergr - you would put it in the "Extra Arguments to driver (optional)" section:

                        fd603557-084b-497d-be1a-0573360cf378-image.png

                        1 Reply Last reply Reply Quote 2
                        • keyserK
                          keyser Rebel Alliance @dennypage
                          last edited by

                          @dennypage Thank you very much for your excellent work on this package.
                          I have not upgraded to 23.01 yet, so a quick question:

                          Should we expect this to be an issue with all USB-HID driver local attached UPS’es, or do you suspect this is UPS model (USB implementation) dependant?

                          About once or twice a week I have a short UPS dropout (< 1 minute) on SG-2100/22.05 with my Eaton 500S UPS.
                          The SG-2100 is VERY remote, so I will try and replace the USB cable in a couple of weeks when I’m on-site again. I was hoping to upgrade to 23.01 at that time :-)

                          My SG-6100/22.05 have no such symptoms with its Eaton 550SC.

                          Love the no fuss of using the official appliances :-)

                          dennypageD 1 Reply Last reply Reply Quote 1
                          • dennypageD
                            dennypage @tman222
                            last edited by

                            @tman222 said in NUT package:

                            Please let me know if the NUT status screenshots would still be helpful to have.

                            They would. The purpose is to know what additional variables are being processed for the cyberpower when interruptonly is not set. Thanks.

                            1 Reply Last reply Reply Quote 1
                            • dennypageD
                              dennypage @keyser
                              last edited by dennypage

                              @keyser said in NUT package:

                              Should we expect this to be an issue with all USB-HID driver local attached UPS’es, or do you suspect this is UPS model (USB implementation) dependant?

                              So far all the signal 10/11 reports pertain to the cyberpower subdriver of usbhid. Not a guarantee, but a good indicator.

                              T 1 Reply Last reply Reply Quote 1
                              • dennypageD
                                dennypage @shaffergr
                                last edited by

                                @shaffergr said in NUT package:

                                My NAS runs TrueNAS Core 13.0-U3.1, which os based on FreeBSD 13.1-RELEASE-p2. It is connected to a 1U CyberPower 700VA UPS via nut and it is also working as expected - no issues.

                                Is the nas running nut 2.8.0? Or is it still on 2.7.4? I was thinking it was nut, particularly the cyberpower subdriver, rather than a kernel issue.

                                S 1 Reply Last reply Reply Quote 1
                                • T
                                  tman222 @dennypage
                                  last edited by tman222

                                  @dennypage - actually, here is a list of all the CyberPower monitored variables from UPS status page. First one is with the interruptonly flag set, the second one is the full set (i.e. regular with polling enabled). I figured it would easier for you to diff the sets this way:

                                  Interrupt Only:
                                  battery.charge
                                  battery.runtime
                                  battery.runtime.low
                                  device.mfr
                                  device.model
                                  device.serial
                                  device.type
                                  driver.flag.interruptonly
                                  driver.name
                                  driver.parameter.pollfreq
                                  driver.parameter.pollinterval
                                  driver.parameter.port
                                  driver.parameter.synchronous
                                  driver.version
                                  driver.version.data
                                  driver.version.internal
                                  driver.version.usb
                                  ups.beeper.status
                                  ups.mfr
                                  ups.model
                                  ups.productid
                                  ups.serial
                                  ups.status
                                  ups.vendorid

                                  Full (Polling Enabled):
                                  battery.charge
                                  battery.charge.low
                                  battery.charge.warning
                                  battery.mfr.date
                                  battery.runtime
                                  battery.runtime.low
                                  battery.type
                                  battery.voltage
                                  battery.voltage.nominal
                                  device.mfr
                                  device.model
                                  device.serial
                                  device.type
                                  driver.name
                                  driver.parameter.pollfreq
                                  driver.parameter.pollinterval
                                  driver.parameter.port
                                  driver.parameter.synchronous
                                  driver.version
                                  driver.version.data
                                  driver.version.internal
                                  driver.version.usb
                                  input.voltage
                                  input.voltage.nominal
                                  output.voltage
                                  ups.beeper.status
                                  ups.delay.shutdown
                                  ups.delay.start
                                  ups.load
                                  ups.mfr
                                  ups.model
                                  ups.productid
                                  ups.realpower.nominal
                                  ups.serial
                                  ups.status
                                  ups.test.result
                                  ups.timer.shutdown
                                  ups.timer.start
                                  ups.vendorid

                                  Hope this helps.

                                  1 Reply Last reply Reply Quote 2
                                  • S
                                    shaffergr @dennypage
                                    last edited by

                                    @dennypage

                                    "pkg list" shows nut-2.7.4_20 installed

                                    dennypageD 1 Reply Last reply Reply Quote 1
                                    • dennypageD
                                      dennypage @shaffergr
                                      last edited by

                                      @shaffergr said in NUT package:

                                      "pkg list" shows nut-2.7.4_20 installed

                                      That's what I expected. With 23.01, pfSense moved to nut 2.8.0. I expect that it's a regression in nut itself.

                                      S 2 Replies Last reply Reply Quote 1
                                      • S
                                        shaffergr @dennypage
                                        last edited by

                                        @dennypage

                                        I also added the "interruptonly" flag to the "Extra Arguments to driver" at approx 11:40 AM. No signal 10 errors/issues found in /var/log/system.log so far (little over 3 hours).

                                        1 Reply Last reply Reply Quote 2
                                        • S
                                          shaffergr @dennypage
                                          last edited by

                                          @dennypage

                                          Also if it helps, XG-7100 has a Intel(R) Atom(TM) CPU C3558 @ 2.20GHz processor and my TrueNAS system is a SuperMicro Server MB with an Intel(R) Atom(TM) CPU C3758 @ 2.20GHz processor, so both amd64 architecture.

                                          dennypageD 1 Reply Last reply Reply Quote 2
                                          • dennypageD
                                            dennypage @lcbbcl
                                            last edited by

                                            @lcbbcl, @xavier1 Are you still having a problem or is it resolved?

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