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.6m 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 @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
                      • dennypageD
                        dennypage @shaffergr
                        last edited by

                        @shaffergr, @tman222, @JonathanLee Can you check on your systems and see if you have any existing core dumps from usbhid-ups?

                        They would probably be in /root, but just in case you can run

                        find / -name '*.core'

                        to search the entire system. Thanks.

                        S JonathanLeeJ 2 Replies Last reply Reply Quote 1
                        • X
                          xavier1 @dennypage
                          last edited by

                          @dennypage Yeah same issue. Did a clean install upgraded from 2.6.0 up to 23.01 then added the package still no luck. Says daemon pending. Then reloaded my xml config and still no go.

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

                            @dennypage
                            I delete and reinstall nut and i have the same problem.
                            Why i see Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                            Pf is not able to find that file, is not generated or what?

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

                              @dennypage @tman222, @JonathanLee

                              no cores found. Also nothing in /var/crash

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

                                @xavier1 said in NUT package:

                                Did a clean install upgraded from 2.6.0 up to 23.01 then added the package still no luck. Says daemon pending.

                                Can you confirm that you have rebooted or done an unplug/replug following reload of config and install of nut? There is a common permissions issue with usb until you do that.

                                Please confirm that you are using UPS Type of "Local USB" with driver "usbhid", and that you have nothing in the Extra Arguments to driver section, and the all sections of the Advanced settings are empty. [You can stuff back later if needed]

                                Where do you see "daemon pending"? In the widget? In the status page (Services / UPS / Status)? In both? If the status page, what happens if you refresh the browser? Does it still show pending?

                                Lastly, can you check your system logs and post any entries matching "usbhid" since the reboot please? Thanks

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

                                  @shaffergr said in NUT package:

                                  no cores found

                                  I was afraid of that. Since nut is not running as root, it won't be able to write to /root.

                                  Would you mind executing the following in a shell and then regenerating the crash?

                                  sysctl kern.corefile=/var/tmp/%N.core

                                  This will cause the core file to be written in /var/tmp which is world writable. Note that this setting will not persist across reboots.

                                  Thanks

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

                                    @lcbbcl said in NUT package:

                                    Why i see Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                    Pf is not able to find that file, is not generated or what?

                                    It's not a file per se. That is a message from upsd saying that the driver isn't running.

                                    Please run usbconfig and confirm that the ups appears there. Also, can you confirm that you have rebooted or done an unplug/replug following reload of config and install of nut? There is a common permissions issue with usb until you do that.

                                    Please confirm that you are using UPS Type of "Local USB" with driver "usbhid", and that you have nothing in the Extra Arguments to driver section, and the all sections of the Advanced settings are empty. [You can stuff back later if needed]

                                    Lastly, please search your system logs for items matching "usbhid" and post the result.

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

                                      @dennypage done. removed the "interruptonly" and hit "save". Console shows:

                                      [23.01-RELEASE][X@Y]/root: sysctl kern.corefile=/var/tmp/%N.core
                                      kern.corefile: /root/%N.core -> /var/tmp/%N.core

                                      Broadcast Message from root@Y
                                      (no tty) at 16:07 EST...

                                      Communications with UPS CyberPower lost

                                      Broadcast Message from root@Y
                                      (no tty) at 16:07 EST...

                                      Communications with UPS CyberPower established

                                      Now we wait...

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

                                        @dennypage I show nothing for logs they already rotated for me. :(

                                        Make sure to upvote

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

                                          @shaffergr I don't think it will be necessary, but if it doesn't generate a core file, add this:

                                          sysctl kern.sugid_coredump=1
                                          S 1 Reply Last reply Reply Quote 1
                                          • L
                                            lcbbcl @dennypage
                                            last edited by lcbbcl

                                            @dennypage
                                            Well i just delete, reboot and reinstall nut not the operating system. Weird that i don't know why after remove nut i still had the settings when i did reinstall.
                                            Feb 19 20:34:08 zid upsd[20330]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 19 20:34:17 zid upsd[42475]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 19 20:34:54 zid upsd[15895]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 19 20:35:00 zid upsd[30880]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 19 20:38:11 zid upsd[36439]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
                                            Feb 19 20:38:30 zid upsd[79042]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
                                            Feb 19 20:39:12 zid upsd[51078]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:23:30 zid upsd[46012]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:28:30 zid upsd[46012]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:45:54 zid upsd[12751]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:49:57 zid upsd[82271]: Can't connect to UPS [ups] (usbhid-ups-ups): No such file or directory
                                            Feb 20 20:50:51 zid upsd[64233]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:52:27 zid upsd[415]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:52:36 zid upsd[85556]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 20:52:39 zid upsd[59802]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:08:57 zid upsd[92079]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:16:05 zid upsd[94197]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:19:28 zid upsd[60128]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:20:08 zid upsd[45874]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:20:11 zid upsd[73849]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:22:57 zid upsd[87326]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:23:07 zid upsd[93669]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:23:10 zid upsd[66247]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            Feb 20 22:24:27 zid upsd[70162]: Can't connect to UPS [APC] (usbhid-ups-APC): No such file or directory
                                            [23.01-RELEASE][admin@]/var/log: usbconfig
                                            ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
                                            ugen0.2: <American Power Conversion Smart-UPS C 1000 FW:UPS 12.0 / ID1005> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)

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