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

    NUT Package (2.8.1 and above)

    Scheduled Pinned Locked Moved UPS Tools
    296 Posts 41 Posters 175.5k 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.
    • D
      DanBlackaz @incith
      last edited by

      @incith I just did the package upgrade and although the service appeared to be working, it wasn't.

      I went to Services -> UPS and UPS Status brought up errors, but then I went to the "UPS Settings" tab and everything looked fine so just pressed Save at the bottom and service is running fine. Maybe try pressing the Save button from the settings page and see if this works for you?

      1 Reply Last reply Reply Quote 0
      • GertjanG
        Gertjan @dennypage
        last edited by

        @dennypage

        NUT Package (2.8.1 and above)

        and now its

        NUT Package (2.8.1 and above - and back again)

        as I received a message from my pfSense :

        Notifications in this message: 1
================================

13:01:10 The following updates are available and can be installed using System > Package Manager:

nut: 2.8.2_1 ==> 2.8.2 (downgrade)

        So the update is a downgrade ?

        Or is 2.8.2 a more recent as 2.8.2_1 because the name (numbering) changed ?

        No "help me" PM's please. Use the forum, the community will thank you.
        Edit : and where are the logs ??

        1 Reply Last reply Reply Quote 0
        • H
          ha11oga11o
          last edited by

          Hello all,

          it seems i have new/old issues with nut 2.8.2_1 on 2.7.2-RELEASE (amd64)
          I need to reload service to get it up again. Its on serial connection.
          Can i do something about this?

          Feb 9 22:20:41 	upsmon 	80900 	UPS RielloSEP2200: on bypass (powered, not protecting)
Feb 9 22:20:41 	upsmon 	80900 	Communications with UPS RielloSEP2200 established
Feb 9 22:20:38 	upsd 	73072 	Connected to UPS [RielloSEP2200]: riello_ser-RielloSEP2200
Feb 9 22:20:37 	riello_ser 	66770 	Startup successful
Feb 9 22:20:36 	upsmon 	80900 	Poll UPS [RielloSEP2200] failed - Driver not connected
Feb 9 22:20:31 	upsmon 	80900 	Poll UPS [RielloSEP2200] failed - Driver not connected
Feb 9 22:20:26 	upsmon 	80900 	UPS RielloSEP2200 is unavailable
Feb 9 22:20:26 	upsmon 	80900 	Poll UPS [RielloSEP2200] failed - Driver not connected
Feb 9 22:20:21 	upsmon 	80900 	Communications with UPS RielloSEP2200 lost
Feb 9 22:20:21 	upsmon 	80900 	Poll UPS [RielloSEP2200] failed - Driver not connected
Feb 9 22:20:21 	upsd 	73072 	User local-monitor@127.0.0.1 logged into UPS [RielloSEP2200]
Feb 9 22:20:21 	upsmon 	80419 	Startup successful
Feb 9 22:20:20 	upsd 	73072 	Startup successful
Feb 9 22:20:20 	upsd 	72610 	Found 1 UPS defined in ups.conf
Feb 9 22:20:20 	upsd 	72610 	Can't connect to UPS [RielloSEP2200] (riello_ser-RielloSEP2200): Connection refused
Feb 9 22:20:20 	upsd 	72610 	listening on ::1 port 3493
Feb 9 22:20:20 	upsd 	72610 	listening on 127.0.0.1 port 3493
Feb 9 22:20:20 	upsmon 	58399 	Signal 15: exiting
Feb 9 22:20:20 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:20:15 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:20:09 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:20:07 	php-fpm 	95968 	/pfblockerng/pfblockerng_update.php: Successful login for user 'admin' from: 192.168.1.210 (Local Database)
Feb 9 22:20:04 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:59 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:54 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:49 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:44 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:39 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:34 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:29 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:24 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:19 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:14 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:09 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:19:04 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:59 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:54 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:49 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:44 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:39 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:34 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:29 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:24 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:19 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:14 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:09 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:18:04 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:59 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:54 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:49 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:44 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:39 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:34 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:29 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:24 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:19 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:14 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:09 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:17:04 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:59 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:54 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:49 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:44 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:39 	upsmon 	58399 	UPS RielloSEP2200 is unavailable
Feb 9 22:16:39 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:34 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:29 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:23 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:18 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:13 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:08 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:16:03 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:58 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:53 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:48 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:43 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:38 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:33 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:28 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:23 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:18 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:13 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:08 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
Feb 9 22:15:03 	upsmon 	58399 	UPS [RielloSEP2200]: connect failed: Connection failure: Connection refused
          1 Reply Last reply Reply Quote 0
          • H
            hspindel
            last edited by

            Not sure if this is a reasonable forum to post this in, but maybe somebody has a helpful idea.

            I have NUT 2.8.2.1 installed on pfSense+ (Netgate 8200).

            I have three Synology units in my network. Two DS120j and one DS1522. Both of the DS120j can see the NUT server and configure it. The DS1522 just reports "No UPS is connected." Settings are identical in all Synology. I have tried disabling the firewall in the DS1522 (although the DS120j are happy with firewall enabled).

            Any suggestions on what to look for?

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

              Hey all,

              Sorry, but I am out of the loop with whatever change just happened. I tried to get the update locked in before my trip, but it didn’t happen. I won’t be able to work on an update until the week of the 19th.

              In the interim, if you have an outstanding issue I suggest looking earlier in this thread for executables that I posted several weeks ago.

              Again, sorry for the upheaval.

              Denny

              I 1 Reply Last reply Reply Quote 0
              • I
                incith @dennypage
                last edited by incith

                @dennypage when I try to service nut onestart..

                I tried chmod everything to 0777

                Network UPS Tools - UPS driver controller 2.8.1.1
                Network UPS Tools - Tripp Lite OMNIVS / SMARTPRO driver 0.35 (2.8.1.1)
                Warning: This is an experimental driver.
                Some features may not function correctly.

                libusb1: Could not open any HID devices: insufficient permissions on everything
                No matching USB/HID UPS found
                upsnotify: failed to notify about state 4: no notification tech defined, will not spam more about it
                Driver failed to start (exit status=1)
                /usr/local/etc/rc.d/nut: WARNING: failed precmd routine for nut

                dennypageD 2 Replies Last reply Reply Quote 0
                • dennypageD
                  dennypage
                  last edited by

                  Quick note: Based on a notice I just received from my own firewall, it might be worthwhile to thy

                  pkg upgrade

                  from the command line and then re-save the config.

                  1 Reply Last reply Reply Quote 0
                  • H
                    hspindel @hspindel
                    last edited by

                    @hspindel said in NUT Package (2.8.1 and above):

                    Not sure if this is a reasonable forum to post this in, but maybe somebody has a helpful idea.

                    I have NUT 2.8.2.1 installed on pfSense+ (Netgate 8200).

                    I have three Synology units in my network. Two DS120j and one DS1522. Both of the DS120j can see the NUT server and configure it. The DS1522 just reports "No UPS is connected." Settings are identical in all Synology. I have tried disabling the firewall in the DS1522 (although the DS120j are happy with firewall enabled).

                    Any suggestions on what to look for?

                    I have some additional clues:

                    upsc NUTIP returns Connection Refused on DS1522, returns correct status on other Synologies.

                    telnet NUTIP 3493 returns Connection Refused on DS1522, connects to NUT server from any other computer on the network.

                    It appears to me that this is not an issue with pfSense (on which the NUT server is running) since it works for every device except the DS1522. I tried adding a special firewall rule to pfSense, but it made no difference. My guess is something is wrong with the DS1522's request.

                    1 Reply Last reply Reply Quote 0
                    • I
                      incith
                      last edited by 

                      curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/pfSense-pkg-nut-2.8.2.pkg

curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/nut-devel-2023.10.07_1.pkg

pkg install -f ./nut-devel-2023.10.07_1.pkg
pkg install -f ./pfSense-pkg-nut-2.8.2.pkg

                      You may just need nut-devel...I did both. UPS is back online.

                      I 1 Reply Last reply Reply Quote 1
                      • I
                        incith @incith
                        last edited by

                        @incith said in NUT Package (2.8.1 and above):

                        curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/pfSense-pkg-nut-2.8.2.pkg

curl -O https://pkg01-atx.netgate.com/pfSense_v2_7_1_amd64-pfSense_v2_7_1/All/nut-devel-2023.10.07_1.pkg

pkg install -f ./nut-devel-2023.10.07_1.pkg
pkg install -f ./pfSense-pkg-nut-2.8.2.pkg

                        You may just need nut-devel...I did both. UPS is back online.

                        Update/Edit: noticing that nut is not listed in my Package manager after this. May need to just do a pkg remove pfSense-pkg-nut nut-devel in a few weeks once a fix is posted. Not sure honestly.

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

                          @incith, @LanterIT, @ha11oga11o

                          If you are still having a problem with the current package, can you post your configs please?

                          Also, can you please confirm that you performed the

                          pkg upgrade

                          step mentioned above?

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

                            @incith said in NUT Package (2.8.1 and above):

                            libusb1: Could not open any HID devices: insufficient permissions on everything
                            No matching USB/HID UPS found

                            This indicates that the USB device could not be opened.

                            Did you say if you are running as root?
                            Also, have you checked to see if there is a quirk registered for your UPS?

                            A 1 Reply Last reply Reply Quote 0
                            • A
                              apremselaar @dennypage
                              last edited by

                              @dennypage I have the same symptoms with the tripplite_usb driver.
                              I have a quirk registered and "user=root" in the config file.

                              it worked without issue with version 2.8.2 and stopped working with 2.8.2_1 (as previously reported by others)

                              I've tried unplugging the UPS' USB cable and plugging it back in. I've tried manually loading the driver as the root user, the netgate (in my case the 4100) recognizes that the UPS is connected and on ugen0.2

                              I haven't attempted a downgrade yet to get it working again, I've just stopped the NUT daemon for now but I would like for this to be working again.

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

                                @apremselaar said in NUT Package (2.8.1 and above):

                                I have the same symptoms with the tripplite_usb driver.
                                I have a quirk registered and "user=root" in the config file.

                                Thank you for letting me know. I do appreciate it.

                                Can you please let me know what UPS model you have?

                                Also, can you let me know the output from "usbconfig -v" please? Thanks

                                A 1 Reply Last reply Reply Quote 0
                                • A
                                  apremselaar @dennypage
                                  last edited by

                                  @dennypage Sure. I have a Tripp Lite Smart500RT1U

                                  here's the output of 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>

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0300
  bDeviceClass = 0x0009  <HUB>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0003
  bMaxPacketSize0 = 0x0009
  idVendor = 0x0000
  idProduct = 0x0000
  bcdDevice = 0x0100
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <XHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001


 Configuration index 0

    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x001f
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040
    bMaxPower = 0x0000

    Interface 0
      bLength = 0x0009
      bDescriptorType = 0x0004
      bInterfaceNumber = 0x0000
      bAlternateSetting = 0x0000
      bNumEndpoints = 0x0001
      bInterfaceClass = 0x0009  <HUB>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0000
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081  <IN>
        bmAttributes = 0x0003  <INTERRUPT>
        wMaxPacketSize = 0x0002
        bInterval = 0x00ff
        bRefresh = 0x0000
        bSynchAddress = 0x0000

      Additional Descriptor

      bLength = 0x06
      bDescriptorType = 0x30
      bDescriptorSubType = 0x00
       RAW dump:
       0x00 | 0x06, 0x30, 0x00, 0x00, 0x00, 0x00




ugen0.2: <Tripp Lite TRIPP LITE SMART500RT1U> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (0mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0008
  idVendor = 0x09ae
  idProduct = 0x0001
  bcdDevice = 0x000a
  iManufacturer = 0x0001  <Tripp Lite >
  iProduct = 0x0002  <TRIPP LITE SMART500RT1U >
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001


 Configuration index 0

    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x0022
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x00c0
    bMaxPower = 0x0000

    Interface 0
      bLength = 0x0009
      bDescriptorType = 0x0004
      bInterfaceNumber = 0x0000
      bAlternateSetting = 0x0000
      bNumEndpoints = 0x0001
      bInterfaceClass = 0x0003  <HID device>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0000
      iInterface = 0x0000  <no string>

      Additional Descriptor

      bLength = 0x09
      bDescriptorType = 0x21
      bDescriptorSubType = 0x10
       RAW dump:
       0x00 | 0x09, 0x21, 0x10, 0x01, 0x00, 0x01, 0x22, 0x34,
       0x08 | 0x00

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081  <IN>
        bmAttributes = 0x0003  <INTERRUPT>
        wMaxPacketSize = 0x0008
        bInterval = 0x000a
        bRefresh = 0x0000
        bSynchAddress = 0x0000

                                  Thanks.

                                  GertjanG dennypageD 2 Replies Last reply Reply Quote 0
                                  • GertjanG
                                    Gertjan @apremselaar
                                    last edited by

                                    @apremselaar said in NUT Package (2.8.1 and above):

                                    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>

                                    bLength = 0x0012
                                    bDescriptorType = 0x0001
                                    bcdUSB = 0x0300
                                    bDeviceClass = 0x0009 <HUB>
                                    bDeviceSubClass = 0x0000
                                    bDeviceProtocol = 0x0003
                                    bMaxPacketSize0 = 0x0009
                                    idVendor = 0x0000
                                    idProduct = 0x0000
                                    bcdDevice = 0x0100
                                    iManufacturer = 0x0001 <Intel>
                                    iProduct = 0x0002 <XHCI root HUB>
                                    iSerialNumber = 0x0000 <no string>
                                    bNumConfigurations = 0x0001

                                    That's just the main USB on board concentrator (see this as a USB switch).

                                    Typically, you would see the connected devices, like mouse, keyboard, and in my case : an UPS :

                                    [23.09.1-RELEASE][root@pfSense.bhf.tld]/root: 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>

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0300
  bDeviceClass = 0x0009  <HUB>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0003
  bMaxPacketSize0 = 0x0009
  idVendor = 0x0000
  idProduct = 0x0000
  bcdDevice = 0x0100
  iManufacturer = 0x0001  <Intel>
  iProduct = 0x0002  <XHCI root HUB>
  iSerialNumber = 0x0000  <no string>
  bNumConfigurations = 0x0001


 Configuration index 0

    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x001f
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x0040
    bMaxPower = 0x0000

    Interface 0
      bLength = 0x0009
      bDescriptorType = 0x0004
      bInterfaceNumber = 0x0000
      bAlternateSetting = 0x0000
      bNumEndpoints = 0x0001
      bInterfaceClass = 0x0009  <HUB>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0000
      iInterface = 0x0000  <no string>

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081  <IN>
        bmAttributes = 0x0003  <INTERRUPT>
        wMaxPacketSize = 0x0002
        bInterval = 0x00ff
        bRefresh = 0x0000
        bSynchAddress = 0x0000

      Additional Descriptor

      bLength = 0x06
      bDescriptorType = 0x30
      bDescriptorSubType = 0x00
       RAW dump:
       0x00 | 0x06, 0x30, 0x00, 0x00, 0x00, 0x00




ugen0.2: <American Power Conversion Back-UPS XS 700U   FW:924.Z5 .I USB FW:Z5> at usbus0, cfg=0 md=HOST spd=LOW (1.5Mbps) pwr=ON (24mA)

  bLength = 0x0012
  bDescriptorType = 0x0001
  bcdUSB = 0x0110
  bDeviceClass = 0x0000  <Probed by interface class>
  bDeviceSubClass = 0x0000
  bDeviceProtocol = 0x0000
  bMaxPacketSize0 = 0x0008
  idVendor = 0x051d
  idProduct = 0x0002
  bcdDevice = 0x0106
  iManufacturer = 0x0003  <American Power Conversion>
  iProduct = 0x0001  <Back-UPS XS 700U   FW:924.Z5 .I USB FW:Z5 >
  iSerialNumber = 0x0002  <3B1926X61525  >
  bNumConfigurations = 0x0001


 Configuration index 0

    bLength = 0x0009
    bDescriptorType = 0x0002
    wTotalLength = 0x0022
    bNumInterfaces = 0x0001
    bConfigurationValue = 0x0001
    iConfiguration = 0x0000  <no string>
    bmAttributes = 0x00e0
    bMaxPower = 0x000c

    Interface 0
      bLength = 0x0009
      bDescriptorType = 0x0004
      bInterfaceNumber = 0x0000
      bAlternateSetting = 0x0000
      bNumEndpoints = 0x0001
      bInterfaceClass = 0x0003  <HID device>
      bInterfaceSubClass = 0x0000
      bInterfaceProtocol = 0x0000
      iInterface = 0x0000  <no string>

      Additional Descriptor

      bLength = 0x09
      bDescriptorType = 0x21
      bDescriptorSubType = 0x10
       RAW dump:
       0x00 | 0x09, 0x21, 0x10, 0x01, 0x21, 0x01, 0x22, 0x05,
       0x08 | 0x04

     Endpoint 0
        bLength = 0x0007
        bDescriptorType = 0x0005
        bEndpointAddress = 0x0081  <IN>
        bmAttributes = 0x0003  <INTERRUPT>
        wMaxPacketSize = 0x0006
        bInterval = 0x000a
        bRefresh = 0x0000
        bSynchAddress = 0x0000

                                    I tend to say : on a low level, USB didn't notice that there was a device (your UPS) connected.
                                    NUT wouldn't see t neither then ...

                                    No "help me" PM's please. Use the forum, the community will thank you.
                                    Edit : and where are the logs ??

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

                                      @apremselaar said in NUT Package (2.8.1 and above):

                                      Smart500RT1U

                                      I assume that this is one of the older non HID units that require tripplite_usb rather than usbhid-ups.

                                      Can you show the logs from your test please?

                                      grep tripplite_usb /var/log/system.log

                                      Thanks

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

                                        @incith Can you show the logs from the driver for your failed attempt to use the current version? Thanks.

                                        1 Reply Last reply Reply Quote 0
                                        • A
                                          apremselaar @dennypage
                                          last edited by

                                          @dennypage here is the output of grep tripplite_usb /var/log/system.log*:

                                          /var/log/system.log:Feb 19 08:56:06 pfs upsd[10877]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.1:Feb 14 11:12:30 pfs upsd[13538]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.1:Feb 14 11:18:48 pfs upsd[69465]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.1:Feb 15 16:52:52 pfs upsd[71312]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.1:Feb 15 16:53:06 pfs upsd[87990]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.2:Feb 14 10:53:40 pfs upsd[47040]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.2:Feb 14 10:56:29 pfs upsd[41261]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.2:Feb 14 11:06:41 pfs upsd[45559]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:17:19 pfs tripplite_usb[79064]: Signal 15: exiting
/var/log/system.log.3:Feb 13 10:17:52 pfs upsd[13641]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:17:55 pfs upsd[30664]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:19:04 pfs upsd[84876]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:20:38 pfs upsd[48093]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:21:59 pfs upsd[38797]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:22:02 pfs upsd[50219]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:22:07 pfs upsd[79386]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:25:23 pfs upsd[75920]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:30:24 pfs upsd[76037]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:35:25 pfs upsd[76037]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 10:40:26 pfs upsd[76037]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 14:51:33 pfs upsd[18479]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 14:53:28 pfs upsd[50130]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 14:57:43 pfs upsd[81124]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 14:59:23 pfs upsd[1010]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory
/var/log/system.log.3:Feb 13 15:08:40 pfs upsd[13672]: Can't connect to UPS [RackTripp] (tripplite_usb-RackTripp): No such file or directory

                                          Thanks

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

                                            @apremselaar said in NUT Package (2.8.1 and above):

                                            /var/log/system.log.3:Feb 13 10:17:19 pfs tripplite_usb[79064]: Signal 15: exiting

                                            Unfortunately the only log entry from the tripplite_usb process is an exit signal.

                                            It's more complicated, but would you try the following?

                                            First, this insures that the nut service is running:

                                            /usr/local/etc/rc.d/nut.sh restart

                                            This kills any driver that may be running:

                                            killall tripplite_usb

                                            This starts the tripplite_usb driver in debug mode:

                                            /usr/local/libexec/nut/tripplite_usb -D -a RackTripp

                                            The driver will output debug information in the shell. Let it run for a few seconds, then you can kill it. Please post the output. Thanks.

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