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

      In another thread, @shaffergr posted important log info:

      kernel: pid 38678 (usbhid-ups), jid 0, uid 66: exited on signal 10
      

      This is a bus error, generally indicative of a pointer problem. Unfortunately this indicates a serious problem in NUT itself. Tracking this with the nut maintainers is going to be a bit of work. Are any of you affected by this experienced C developers?

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

        @dennypage
        Logs I am still waiting for the random disconnect again.

        Feb 17 13:59:28 upsmon 34044 Communications with UPS CyberPower established
        Feb 17 13:59:28 upsd 35103 User local-monitor@127.0.0.1 logged into UPS [CyberPower]
        Feb 17 13:59:24 upsd 35103 Startup successful
        Feb 17 13:59:24 upsd 35103 Connected to UPS [CyberPower]: usbhid-ups-CyberPower
        Feb 17 13:59:24 upsd 35103 listening on 127.0.0.1 port 3493
        Feb 17 13:59:24 upsd 35103 listening on ::1 port 3493
        Feb 17 13:59:23 usbhid-ups 35031 Startup successful
        Feb 17 13:59:23 upsmon 34044 Communications with UPS CyberPower lost
        Feb 17 13:59:23 upsmon 34044 UPS [CyberPower]: connect failed: Connection failure: Connection refused
        Feb 17 13:59:23 upsmon 34044 Startup successful
        Feb 17 13:59:23 php-fpm 84710 /nut_settings.php: Starting service nut
        Feb 17 13:59:23 upsd 57325 Signal 15: exiting
        Feb 17 13:59:23 upsd 57325 mainloop: Interrupted system call
        Feb 17 13:59:23 upsd 57325 User local-monitor@127.0.0.1 logged out from UPS [CyberPower]
        Feb 17 13:59:23 upsmon 46187 Signal 15: exiting
        Feb 17 13:59:23 php-fpm 84710 /nut_settings.php: Stopping service nut
        Feb 17 13:59:23 check_reload_status 430 Syncing firewall
        Feb 17 13:59:23 php-fpm 84710 /nut_settings.php: Configuration Change: admin@192.168.1.13 (Local Database): Updated UPS settings
        Feb 17 13:59:19 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:59:14 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:59:09 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:59:05 php-fpm 84710 /index.php: Successful login for user 'admin' from: 192.168.1.13 (Local Database)
        Feb 17 13:59:04 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:59 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:54 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:49 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:44 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:42 php-fpm 84710 /widgets/widgets/gateways.widget.php: Session timed out for user 'admin' from: 192.168.1.13 (Local Database)
        Feb 17 13:58:39 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:34 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:29 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:24 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:19 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:14 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:09 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:58:04 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:59 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:54 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:49 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:44 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:39 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:34 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:29 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:24 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:19 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:14 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:14 kernel ugen1.2: <CPS CP 1300D> at usbus1
        Feb 17 13:57:09 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:57:04 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:59 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:54 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:49 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:44 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:39 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:34 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:29 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:23 upsmon 46187 Communications with UPS CyberPower lost
        Feb 17 13:56:23 upsmon 46187 Poll UPS [CyberPower] failed - Driver not connected
        Feb 17 13:56:23 kernel pid 53495 (usbhid-ups), jid 0, uid 66: exited on signal 11
        Feb 17 13:56:23 upsd 57325 Can't connect to UPS [CyberPower] (usbhid-ups-CyberPower): Connection refused
        Feb 17 13:56:18 kernel ugen1.2: <CPS CP 1300D> at usbus1 (disconnected)
        Feb 17 13:54:36 kernel mvneta0: promiscuous mode enabled
        Feb 17 13:53:58 login 66832 ROOT LOGIN (admin) ON ttyu0
        Feb 17 13:53:58 login 66832 login on ttyu0 as admin
        Feb 17 13:53:23 upsmon 46187 Communications with UPS CyberPower established
        Feb 17 13:53:23 upsd 57325 User local-monitor@127.0.0.1 logged into UPS [CyberPower]
        Feb 17 13:53:19 upsd 57325 Startup successful
        Feb 17 13:53:19 upsd 57325 Connected to UPS [CyberPower]: usbhid-ups-CyberPower
        Feb 17 13:53:19 upsd 57325 listening on 127.0.0.1 port 3493
        Feb 17 13:53:19 upsd 57325 listening on ::1 port 3493
        Feb 17 13:53:19 usbhid-ups 53495 Startup successful

        Make sure to upvote

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

          @dennypage Thanks for looking into this so quickly. Maybe they can fix it with HLA (High Level Assembly) it is very C++ like I am learning assembly this semester, again HLA versus Intel based assembly code is very different. ARM based assembly language is also different. We are doing x86-x64 intel right now it's very cool!!

          Make sure to upvote

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

            @dennypage

            unfortunately, the system keeps thinking that my reply is spam and won't let me post it.

            went through the instructions.

            usbconfig -v gives the same before and after. UPS is attached to ugen0.2 and identified correctly - "CPS OR500LCDRM1Ua".

            [23.01-RELEASE][X@Y]/var/log: cat *.log | egrep -ie usb | more

            shows no errors or info that already reported in my original post.

            [23.01-RELEASE][X@Y]/var/log: usbconfig -v

            ugen0.1: <Intel XHCI root HUB> at usbus0, cfg=0 md=HOST spd=SUPER (5.0Gbps) pwr=SAVE (0mA)
            ugen0.1.0: uhub0: <Intel XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1>

            ugen0.2: <CPS OR500LCDRM1Ua> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (2mA)

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

              @shaffergr said in NUT package:

              [23.01-RELEASE][X@Y]/var/log: cat *.log | egrep -ie usb | more
              shows no errors or info that already reported in my original post.

              Thanks. Your original post contained the crucial information, which is that usbhid-ups is exiting with a bus error.

              I'm assuming that the others will also see this in their logs.

              Are you a C coder by chance? I don't have a CPS.

              S JonathanLeeJ 2 Replies Last reply Reply Quote 1
              • dennypageD
                dennypage @azdeltawye
                last edited by

                @azdeltawye said in NUT package:

                I am experiencing the same issue with my Tripp Lite rack mount UPS; NUT not able to connect after upgrading pfSense to 23.01.

                Is it the same issue? It works for several minutes and then fails? Or is the issue you are seeing that it never works?

                If the former, please check your logs for usbhid-ups messages and post them.

                If the latter, have you unplugged and replugged since updating? Alternatively a second reboot would work as well.

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

                  @dennypage

                  Its been a long time since I coded anything so most likely no help.

                  nut/usb package worked flawlessly under 22.05 so wonder what changed...

                  Can I turn the log level up to debug to gather more info?

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

                    @dennypage

                    9f0f6aa7-8e8e-4d03-95b0-7c73f29be9e7-image.png
                    (Image: Same issue)
                    acf4cd92-c56f-4e67-b14f-5e99ff811249-image.png
                    (Image: Same issue)

                    Feb 17 13:56:23 Lee_Family kernel: pid 53495 (usbhid-ups), jid 0, uid 66: exited on signal 11

                    Feb 17 09:20:53 Lee_Family kernel: pid 85785 (usbhid-ups), jid 0, uid 66: exited on signal 11

                    Make sure to upvote

                    S 1 Reply Last reply Reply Quote 0
                    • S
                      shaffergr @JonathanLee
                      last edited by

                      @jonathanlee

                      I am only seeing exit signal 10, not signal 11 so interesting..

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

                        @shaffergr I am running an ARM processor for this one

                        Make sure to upvote

                        S 1 Reply Last reply Reply Quote 0
                        • JonathanLeeJ
                          JonathanLee @azdeltawye
                          last edited by JonathanLee

                          @azdeltawye
                          Run this command in the GUI

                          5d5ae5c9-7a94-4aad-bcd6-3077410cf877-image.png

                          cat /var/log/*.log

                          After search with ctl-f usbhid-ups this should make it easy so you do not need to log in with a console cable or ssh in, and still get the log entry everyone is looking for.

                          b6677be3-db34-4357-ac96-cd331ff2fa07-image.png

                          Quick and easy way to find it, my grep | was not working in the command area.

                          Make sure to upvote

                          A 1 Reply Last reply Reply Quote 0
                          • S
                            shaffergr @JonathanLee
                            last edited by

                            @jonathanlee

                            My Bo’s is a Netgate XG-7100. Intel Atom processor so amd64

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

                              @shaffergr

                              Box, not Bo’s

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

                                @shaffergr said in NUT package:

                                I am only seeing exit signal 10, not signal 11 so interesting.

                                Different sides of the same random pointer coin. One is accessing memory that doesn't exist, the other is accessing memory that exists but doing so improperly.

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

                                  @shaffergr mine is a Netgate SG-2100 Max

                                  Make sure to upvote

                                  1 Reply Last reply Reply Quote 0
                                  • T
                                    tman222
                                    last edited by tman222

                                    Fingers crossed, I may have found a workaround. My CyberPower UPS has now been continuously connected for a little over 1.5 hours.

                                    After a lot of searching, I came across this link:

                                    https://github.com/networkupstools/nut/wiki/Troubleshooting-eventual-disconnections-(Data-stale)

                                    I ended up setting/adjusting the following variables:
                                    pollinterval=15 in the section for ups.conf
                                    MAXAGE 25 in the section for upsd.conf
                                    DEADTIME 25 in the section for upsmon.conf

                                    Will continue to monitor - hopefully it will to stay connected.

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

                                      @tman222 said in NUT package:

                                      Fingers crossed, I may have found a workaround. My CyberPower UPS has now been continuously connected for a little over 1.5 hours.

                                      After a lot of searching, I came across this link:

                                      https://github.com/networkupstools/nut/wiki/Troubleshooting-eventual-disconnections-(Data-stale)

                                      I ended up setting/adjusting the following variables:
                                      pollinterval=15 in the section for ups.conf
                                      MAXAGE 25 in the section for upsd.conf
                                      DEADTIME 25 in the section for upsmon.conf

                                      Will continue to monitor - hopefully it will to stay connected.

                                      Well, I spoke too soon - shortly after posting this the connection was lost again with the same signal 10 kernel error shown in the logs that has already been referenced above.

                                      Would another temporary workaround be just to set up a cron job to restart nut every e.g. 15min until a more permanent solution is found?

                                      1 Reply Last reply Reply Quote 1
                                      • A
                                        azdeltawye @JonathanLee
                                        last edited by

                                        @jonathanlee

                                        My problem looks a bit different.

                                        b5e72f85-d3a1-41b8-aa4c-10486eaad734-image.png

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

                                          @dennypage I removed the package for now, it is generating tons of logs that I can't see anything else in the GUI logs. It seems to be consuming more resources than normal also with the pointer issues. Will reinstall once we have a solid resolve for this issue.

                                          Make sure to upvote

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

                                            @azdeltawye is that the only entry ?

                                            Make sure to upvote

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