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

      @dennypage said in NUT package:

      hw.usb.quirk.0="0x2e51 0x0002 0x0000 0xffff UQ_HID_IGNORE"

      You can test this in advance by running this:

      usbconfig add_dev_quirk_vlph 0x2e51 0x0002 0x0000 0xffff UQ_HID_IGNORE

      followed by unplugging and replugging the usb cable to your ups. If the values are correct, when you run "usbconfig -d ugen0.2 show_ifdrv" again, you should only see one line of output like so:

      ugen0.2: <EVER ECO PRO AVR CDS> at usbus0, cfg=0 md=HOST spd=FULL (12Mbps) pwr=ON (100mA)

      The ugen0.2.0 should be gone.

      Thanks, this was very helpfull. I had to modifiy command a bit, as I've noticed its add_dev_quirk_vplh not vlph and I changed pid (product id) to 0x0000. Now the second line is gone:

      968f6812-b18a-4f46-a327-89f2e61b2ad3-image.png

      Now NUT starts without user=root just fine:

      Feb 23 22:27:05	upsmon	20539	Communications with UPS ever established
Feb 23 22:27:05	upsd	23193	User local-monitor@127.0.0.1 logged into UPS [ever]
Feb 23 22:27:01	php	16832	/usr/local/sbin/acbupload.php: End of configuration backup to https://acb.netgate.com/save (success).
Feb 23 22:27:01	upsd	23193	Startup successful
Feb 23 22:27:01	upsd	23193	Connected to UPS [ever]: usbhid-ups-ever
Feb 23 22:27:01	upsd	23193	listening on 127.0.0.1 port 3493
Feb 23 22:27:01	upsd	23193	listening on ::1 port 3493
Feb 23 22:27:00	usbhid-ups	21611	Startup successful

      But soon after one minute or so:

      Feb 23 22:28:15	upsmon	20539	Poll UPS [ever] failed - Driver not connected
Feb 23 22:28:10	upsmon	20539	Communications with UPS ever lost
Feb 23 22:28:10	upsmon	20539	Poll UPS [ever] failed - Driver not connected
Feb 23 22:28:08	kernel		pid 21611 (usbhid-ups), jid 0, uid 66: exited on signal 10
Feb 23 22:28:08	upsd	23193	Can't connect to UPS [ever] (usbhid-ups-ever): Connection refused
      dennypageD 1 Reply Last reply Reply Quote 0
      • dennypageD
        dennypage @tnowak
        last edited by

        @tnowak said in NUT package:

        I had to modifiy command a bit, as I've noticed its add_dev_quirk_vplh not vlph

        Sorry, typo. I corrected the original post.

        But soon after one minute or so:
        Feb 23 22:28:08 kernel pid 21611 (usbhid-ups), jid 0, uid 66: exited on signal 10

        Congratulations, you are a double winner. 😀
        The post above regarding the CyberPower UPS units applies to you as well.

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

          @dennypage said in NUT package:

          Congratulations, you are a double winner. 😀

          Wow, amazing! I deployed that workaround for the time being and it works reliably now! Looking forward for future nut package releases that solves this issue.

          You're the man @dennypage! Thank you VERY much for your support that is extremely competent and helpful.

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

            @dennypage

            the "usbhid-ups" binary built from the FreeBSD nut-devel port you provided earlier this week to test looks to have solved the problem for me (or at least for those that have CyberPower UPSs). As of this morning eastern time, it's been running for over 72 hours with no more "exit on signal 10" errors in my system log file. Thanks for all your help in identifying the issue and that its already been fixed in the newer version of nut.

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

              @shaffergr is this available form package manager now?

              Make sure to upvote

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

                @jonathanlee

                No. Denny provided me a build from nut-devel branch so that we could validate if the signal 10 issue was fix or not.

                1 Reply Last reply Reply Quote 0
                • L LamaZ referenced this topic on
                • L LamaZ referenced this topic on
                • J
                  JPP 0 @dennypage
                  last edited by JPP 0

                  @dennypage I've been seeing logs like this:

                  Feb 25 19:37:13 gatekeeper kernel: pid 29800 (usbhid-ups), jid 0, uid 0: exited on signal 10
Feb 25 19:37:15 gatekeeper upsmon[28298]: Poll UPS [tripplite] failed - Driver not connected
Feb 25 19:37:15 gatekeeper upsmon[28298]: Communications with UPS tripplite lost
Feb 25 19:37:20 gatekeeper upsmon[28298]: Poll UPS [tripplite] failed - Driver not connected
Feb 25 19:37:25 gatekeeper upsmon[28298]: Poll UPS [tripplite] failed - Driver not connected
Feb 25 19:37:30 gatekeeper upsmon[28298]: Poll UPS [tripplite] failed - Driver not connected
Feb 25 19:37:35 gatekeeper upsmon[28298]: Poll UPS [tripplite] failed - Driver not connected

<goes on the same until manually restarted.>

                  setting interruptonly appears to have mitigated it. UPS is a Tripp Lite SMART1500LCD rack mount unit. It seemed to work fine prior to the last update.

                  dennypageD whoami TMW 2 Replies Last reply Reply Quote 0
                  • dennypageD
                    dennypage @JPP 0
                    last edited by

                    @jpp-0 I sent you the dev build of usbhid-ups. Please let me know if it works for you.

                    J 1 Reply Last reply Reply Quote 1
                    • J
                      JPP 0 @dennypage
                      last edited by

                      @dennypage Thanks sending the dev version, it looks to be working, it's been running for over 8 hours with all the extra config (interruptonly and user=root etc) removed. No crashes. It correctly detected power loss and power restored. If it fails laster I'll post and update but I'm not expecting it to as it would fine within minutes before.

                      1 Reply Last reply Reply Quote 1
                      • W
                        wirehead @dennypage
                        last edited by

                        @dennypage can confirm interruptonly does the job as a workaround with my Cyberpower UPS. Many thanks.

                        1 Reply Last reply Reply Quote 1
                        • whoami TMW
                          whoami TM @JPP 0
                          last edited by whoami TM

                          @jpp-0 I couldn't get the Smart1500 LCD I had to work if my life depended on it. I must have had a defective unit. I ended up returning it and getting a APC BGM1500B which worked right out of the box.

                          I couldn't get offdelay=60 and ondelay=90 to hold. It would hold the settings for 20 mins max then revert to default values.

                          To top that off the UPS would run down until the battery died and never send shutdown command to my Netgate box.

                          Can you screen shot or post your settings. I'm interested to find out what actually works with that UPS. I killed myself for weeks until my return window was about to close before my autism would allow me to give up.

                          link to my orginal post

                          J 2 Replies Last reply Reply Quote 0
                          • J
                            JPP 0 @whoami TM
                            last edited by

                            @whoami-tm right now I just have the defaults set on pfsense. My setup is a bit odd in that it should never get to shutdown becasue the generator / automatic transfer kicks in after 25 seconds and I have about a week's worth of propane on site.

                            I have by proxmox servers (the very originally named pxoxie and moxie, both nut clients) set to shutdown after 10 mins if for some reason the generator fails.

                            The pfsense box is not configured to shutdown. I'm running ram disk filesystems so I'm less worried about disk corruption and want to keep it running as long as possible.

                            I blew away all the config I had on pfSense trying to debug the crashes, I may add some complexity back but not for a while.

                            Lastly I would not buy Tripplite again it completely fails to give a decent runtime estimate (best guess is the power factor on modife sine wave is different enough from tru sine on the grid that it just get's confused).

                            J 1 Reply Last reply Reply Quote 0
                            • J
                              JPP 0 @JPP 0
                              last edited by

                              This post is deleted!
                              1 Reply Last reply Reply Quote 0
                              • J
                                JPP 0 @whoami TM
                                last edited by JPP 0

                                @whoami-tm have you tried this

                                [23.01-RELEASE][root@gatekeeper]/root: upsrw -s ups.delay.shutdown tripplite
Username (root): admin
Password: 
Enter new value for ups.delay.shutdown: 59
OK

                                sub in your ups name and get the password for admin from /usr/local/etc/nut/upsd.users

                                ups.delay.shutdown seems to be the only value you can program but if I'm reading it correctly it should let you make it wait longer before powering off.

                                1 Reply Last reply Reply Quote 0
                                • D
                                  dreadful9278
                                  last edited by

                                  I'm using a CyberPower UPS, and I'm experiencing the same signal 10 error. I've found the interruptonly setting to work until the USB issue is resolved.

                                  If there is anything I can do to help/test a fix then let me know :-)

                                  Anecdotally I've noticed my firewall's processor is running hotter than it used to, I don't think the CPU is idling properly not sure if anyone else is noticing a similar problem and if it is related in some way.

                                  1 Reply Last reply Reply Quote 0
                                  • L
                                    LamaZ
                                    last edited by

                                    @dennypage I just wanted to thank you again sincerely for this post and for finding my erroneous post. This research has made the upgrade to pfSense+ 23.01 stable.

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

                                      @lamaz You're welcome. Glad it's working for you.

                                      1 Reply Last reply Reply Quote 0
                                      • demD dem referenced this topic on
                                      • demD dem referenced this topic on
                                      • demD dem referenced this topic on
                                      • T
                                        trentk10
                                        last edited by trentk10

                                        Thanks for the work everyone has put into this so far.

                                        Decided to upgrade from 2.6 CE to plus 23.01 today. Having the same issues as others are too. Looks to be with the usb driver. Started happening shortly after updrade completed.

                                        I am getting the same results after adding root as a user.

                                        
Mar  8 21:53:35 pfSense upsd[9141]: Can't connect to UPS [eaton9130rm] (usbhid-ups-eaton9130rm): Connection refused
Mar  8 21:53:35 pfSense kernel: pid 8842 (usbhid-ups), jid 0, uid 0: exited on signal 10
Mar  8 21:53:39 pfSense upsmon[1672]: Poll UPS [eaton9130rm] failed - Driver not connected
Mar  8 21:53:39 pfSense upsmon[1672]: Communications with UPS eaton9130rm lost
Mar  8 21:53:45 pfSense upsmon[1672]: Poll UPS [eaton9130rm] failed - Driver not connected
Mar  8 21:53:50 pfSense upsmon[1672]: Poll UPS [eaton9130rm] failed - Driver not connected
Mar  8 21:53:55 pfSense upsmon[1672]: Poll UPS [eaton9130rm] failed - Driver not connected
                                        dennypageD 1 Reply Last reply Reply Quote 0
                                        • dennypageD
                                          dennypage @trentk10
                                          last edited by

                                          @trentk10 said in NUT package:

                                          Mar 8 21:53:35 pfSense kernel: pid 8842 (usbhid-ups), jid 0, uid 0: exited on signal 10

                                          Unfortunately, this is being hit by a lot of people with NUT 8.0. See this post for information.

                                          1 Reply Last reply Reply Quote 1
                                          • dennypageD dennypage referenced this topic on
                                          • D
                                            DavidIr @dennypage
                                            last edited by

                                            @dennypage I seem to have a similar but possibly different problem.

                                            My UPS is an Eaton Eclipse ECO 650 connected by USB to my Netgate-3100 running 23.01-RELEASE (arm) with NUT 2.8.0_2.

                                            Note: the setup worked perfectly before my update to 23.01 and 2.8.0 for over 6 months, there have been no powercuts/surges or hardware changes.

                                            As with others I am seeing repeated log entries from upsmon.

                                            Mar 12 09:57:09	upsmon	80760	Poll UPS [EatonUPS] failed - Driver not connected
Mar 12 09:57:04	upsmon	80760	Poll UPS [EatonUPS] failed - Driver not connected

                                            If I filter my logs to upshid-ups I only see the following:

                                            Mar 9 22:26:16	usbhid-ups	91631	Startup successful
Mar 9 22:26:09	usbhid-ups	70838	Signal 15: exiting
Mar 9 22:20:46	usbhid-ups	70838	Startup successful
Mar 9 22:20:41	usbhid-ups	47718	Signal 15: exiting
Mar 9 22:13:14	usbhid-ups	47718	Startup successful
Mar 9 22:10:05	usbhid-ups	75991	Signal 15: exiting
Mar 9 21:57:06	usbhid-ups	75991	Startup successful

                                            If I filter the logs to upsd I see:

                                            Mar 12 09:07:25	upsd	82791	Can't connect to UPS [EatonUPS] (usbhid-ups-EatonUPS): Connection refused
Mar 12 09:02:25	upsd	82791	Can't connect to UPS [EatonUPS] (usbhid-ups-EatonUPS): Connection refused
Mar 12 08:57:25	upsd	82791	Can't connect to UPS [EatonUPS] (usbhid-ups-EatonUPS): Connection refused
Mar 12 08:52:25	upsd	82791	Can't connect to UPS [EatonUPS] (usbhid-ups-EatonUPS): Connection refused
Mar 9 22:26:16	upsd	82791	Connected to UPS [EatonUPS]: usbhid-ups-EatonUPS
Mar 9 22:26:14	upsd	82791	User local-monitor@::1 logged into UPS [EatonUPS]
Mar 9 22:26:10	upsd	82791	Startup successful
Mar 9 22:26:10	upsd	82791	Can't connect to UPS [EatonUPS] (usbhid-ups-EatonUPS): No such file or directory
Mar 9 22:26:10	upsd	82791	not listening on 127.0.0.1 port 3493
Mar 9 22:26:10	upsd	82791	listening on ::1 port 3493
Mar 9 22:26:10	upsd	82791	listening on 127.0.0.1 port 3493
Mar 9 22:26:10	upsd	82791	not listening on 192.168.200.254 port 3493
Mar 9 22:26:10	upsd	82791	listening on pfsense.{internaldomainname} port 3493
Mar 9 22:26:09	upsd	62680	Signal 15: exiting
Mar 9 22:26:09	upsd	62680	mainloop: Interrupted system call
Mar 9 22:26:09	upsd	62680	User local-monitor@::1 logged out from UPS [EatonUPS]

                                            This morning the failure occurred at 08:52 (from notification email):

                                            8:52:27 UPS Notification from pfSense.irwazu.co.uk - Sun, 12 Mar 2023 08:52:27 +0000

Communications with UPS EatonUPS lost

                                            My configuration is extra arguments to driver:

                                            pollfreq=90

                                            Additional configuration lines for upsmon.conf

                                            RUN_AS_USER root

                                            Additional configuration lines for ups.conf

                                            user=root
pollinterval=15

                                            Other than using the "interruptonly" option is there anything I can do to resolve or help debug the cause? Is this likely the same issue as for CyberPower UPSs you've already identified?

                                            Full logs of a restart of the UPS service are as follows:

                                            Mar 12 10:05:19	upsmon	69168	Communications with UPS EatonUPS established
Mar 12 10:05:16	upsd	70834	Connected to UPS [EatonUPS]: usbhid-ups-EatonUPS
Mar 12 10:05:15	usbhid-ups	80232	Startup successful
Mar 12 10:05:14	upsmon	69168	UPS EatonUPS is unavailable
Mar 12 10:05:14	upsmon	69168	Poll UPS [EatonUPS] failed - Driver not connected
Mar 12 10:05:14	upsd	70834	User local-monitor@::1 logged into UPS [EatonUPS]
Mar 12 10:05:10	upsd	70834	Startup successful
Mar 12 10:05:10	upsd	70834	Can't connect to UPS [EatonUPS] (usbhid-ups-EatonUPS): Connection refused
Mar 12 10:05:10	upsd	70834	not listening on 127.0.0.1 port 3493
Mar 12 10:05:10	upsd	70834	listening on ::1 port 3493
Mar 12 10:05:10	upsd	70834	listening on 127.0.0.1 port 3493
Mar 12 10:05:10	upsd	70834	not listening on 192.168.200.254 port 3493
Mar 12 10:05:10	upsd	70834	listening on pfsense.irwazu.co.uk port 3493
Mar 12 10:05:09	upsmon	69168	Communications with UPS EatonUPS lost
Mar 12 10:05:09	upsmon	69168	UPS [EatonUPS]: connect failed: Connection failure: Connection refused
Mar 12 10:05:09	upsmon	69168	Startup successful
Mar 12 10:05:08	upsd	82791	Signal 15: exiting
Mar 12 10:05:08	upsd	82791	mainloop: Interrupted system call
Mar 12 10:05:08	upsd	82791	User local-monitor@::1 logged out from UPS [EatonUPS]
Mar 12 10:05:08	upsmon	80760	Signal 15: exiting
Mar 12 10:05:07	upsmon	80760	Poll UPS [EatonUPS] failed - Driver not connected

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