Skip to content
View in the app

A better way to browse. Learn more.
Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

[Plugin] NUT v2 - Network UPS Tools

dmacias
in Plugin Support

Featured Replies

The most recent update introduces a new setting that allows redirecting all NUT output to a separate logfile.

This can be helpful for users where the SYSLOG is continuously spammed and rule based filters did not help.

But please make sure to read the help-text to understand the implications of this setting before activating it. 🙂 

 

  • Quote
    • Like 1
    • Replies 2.1k
    • Views 467.4k
    • Created
    • Last Reply

    Top Posters In This Topic

    Popular Days

    Most Popular Posts

    • SimonF
      SimonF

      I am stopping updates for my version of the plugin. Update to the latest version 2023.09.17 and then you can remove my version and install Rysz's from CA and it will retain your configs.   T

    • SimonF
      SimonF

      Released 2023.07.26, @ich777 is creating a new package for me to use, and I want to look to move to 2.8 as the default version but will need to check upgrade path works ok.

    • Rysz
      Rysz

      That APC BX series is known to suffer from this (what we believe to be) firmware issue and we've put patches in place to suppress this unwanted behaviour on the UPS side. Here's how you can set it up:

    Posted Images

    My previous UPS was overdue for replacement, which was also being reported by the unit itself. I fully replaced the UPS with a newer system, but I'm still getting somewhat daily alert notifications saying "Alert [UNRAIDSERVER] NUT: [ups] UPS Battery Replacement" with description "UPS reports that its batteries need replacement.". I would have to assume that these are being caused from some data of the old system lingering around in the server, as there are no alerts showing on the NUT Settings page since I connected the new unit and two self tests of the unit passed without issues (ups.test.result = "Done and passed"). Both units were monitored via a direct USB connection, if that's relevant.

     

    Is there anything I can do to check that this is old data and, if so, how can I fully clear this alert so it stops showing up unnecessarily?

  • Quote
    6 hours ago, Glodenox said:

    My previous UPS was overdue for replacement, which was also being reported by the unit itself. I fully replaced the UPS with a newer system, but I'm still getting somewhat daily alert notifications saying "Alert [UNRAIDSERVER] NUT: [ups] UPS Battery Replacement" with description "UPS reports that its batteries need replacement.". I would have to assume that these are being caused from some data of the old system lingering around in the server, as there are no alerts showing on the NUT Settings page since I connected the new unit and two self tests of the unit passed without issues (ups.test.result = "Done and passed"). Both units were monitored via a direct USB connection, if that's relevant.

     

    Is there anything I can do to check that this is old data and, if so, how can I fully clear this alert so it stops showing up unnecessarily?

     

    What manufacturer and model is your UPS?

    Please post the NUT Debug Package that can be found in NUT Settings.

     

  • Quote
    On 12/3/2024 at 12:32 AM, Rysz said:

    The most recent update introduces a new setting that allows redirecting all NUT output to a separate logfile.

    Thanks for cool future.

    Maybe you can add option 'copy nut log to flash on shutdown' like we have in syslog if you think it will be useful? 

  • Quote
    • Upvote 1
    2 hours ago, Rysz said:

     

    What manufacturer and model is your UPS?

    Please post the NUT Debug Package that can be found in NUT Settings.

     

    Thanks for the help! The old UPS was an APC Back-UPS BE700G-FR, the new one is an APC Back-UPS BX750MI. I don't remember when exactly I replaced the unit, but I think it was around November 27. For a short while, I also used the built-in APC UPS Settings, but that one is of course stopped now, and I'm not seeing any reference to it in the notification.

     

    I've attached the debug logs to this message. While looking around in those logs myself, I saw that upsmon is apparently triggering these notifications, but I'm not immediately seeing anything out of the ordinary in the conf files of the NUT package on the server.

    nut-debug-20241205092143.zip

  • Quote
    18 minutes ago, Glodenox said:

    Thanks for the help! The old UPS was an APC Back-UPS BE700G-FR, the new one is an APC Back-UPS BX750MI. I don't remember when exactly I replaced the unit, but I think it was around November 27. For a short while, I also used the built-in APC UPS Settings, but that one is of course stopped now, and I'm not seeing any reference to it in the notification.

     

    I've attached the debug logs to this message. While looking around in those logs myself, I saw that upsmon is apparently triggering these notifications, but I'm not immediately seeing anything out of the ordinary in the conf files of the NUT package on the server.

    nut-debug-20241205092143.zip 132.11 kB · 0 downloads

     

    That APC BX series is known to suffer from this (what we believe to be) firmware issue and we've put patches in place to suppress this unwanted behaviour on the UPS side. Here's how you can set it up:

    • Go to NUT Settings.
    • Set Network UPS Tools Backend Switch to preview (latest build).
    • Apply settings and either reinstall NUT or reboot the machine.
    • Confirm the Network UPS Tools Backend now has "master" in the name.
    • Using the NUT Configuration Editor (in NUT Settings) put at the end of ups.conf (after line 8 or later): 
      pollonly
lbrb_log_delay_sec = 3
lbrb_log_delay_without_calibrating
    • Save the configuration file and restart NUT.
    • After reloading the NUT Settings page, confirm the made changes are still present in ups.conf.

    Please let us know if the process worked out for you or if you have any additional questions. 🙂 

     

  • Quote
    • Like 5
    50 minutes ago, Rysz said:

     

    That APC BX series is known to suffer from this (what we believe to be) firmware issue and we've put patches in place to suppress this unwanted behaviour on the UPS side. Here's how you can set it up:

    [snip]

    Please let us know if the process worked out for you or if you have any additional questions. 🙂 

     

    Just my luck to buy a device from that series 🤣

    I'm now on version nut-2.8.2-x86_64-6master.ssl11 and the added configuration remains present after the restart. Hopefully this stops the notifications from happening again. I've added a task to my calendar to report here on any results. Thanks for the help already!

  • Quote

    @Rysz Also will be cool to see var descriptions in NUT Details on hover from cmdvartab , if it possible to make and you will have time for it , also if you think its useful.

    Edited by Masterwishx

  • Quote
    • Upvote 1

    Hello,

     

    I installed your plugin since my brand new APC BGM2200-GR isn't natively recognized by Unraid.

     

    Your plugin works for some time, then it stops to work and I get all these warnings: 

    Dec  5 20:23:23 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:23 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:23 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:25 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:25 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:25 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:26 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:27 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:27 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:27 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:29 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:29 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:29 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:31 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:31 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:31 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:31 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:33 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:33 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:33 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:35 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:35 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:35 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:36 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:37 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:37 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:37 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:39 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:39 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:39 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:41 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:41 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:41 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:41 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:43 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:43 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:43 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:45 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:45 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:45 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:46 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:47 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:47 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:47 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:49 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:49 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:49 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:51 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:51 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:51 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:51 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:53 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:53 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:53 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:55 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:55 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:55 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:56 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:57 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:57 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:57 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:59 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:59 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:59 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:01 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:01 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:01 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:01 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:03 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:03 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:03 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:05 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:05 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:05 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:06 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:07 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:07 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:07 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:09 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:09 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:09 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:11 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:11 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:11 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:11 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:13 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:13 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:13 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:15 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:15 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:15 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:16 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:17 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:17 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:17 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:19 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:19 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:19 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:21 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:21 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:21 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:21 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:23 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:23 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:23 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:25 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:25 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:25 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:26 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:27 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:27 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:27 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:29 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:29 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:29 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:31 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:31 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:31 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:31 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:31 NAS upsmon[90853]: UPS [email protected] is unavailable
Dec  5 20:24:33 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:33 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:34 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:35 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:35 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:36 NAS ool www[1149035]: /usr/local/emhttp/plugins/nut-dw/scripts/restart
Dec  5 20:24:36 NAS rc.nut: Stopping the NUT services... 
Dec  5 20:24:36 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:36 NAS rc.nut: Network UPS Tools upsmon 2.8.2
Dec  5 20:24:36 NAS upsmon[90853]: Signal 15: exiting
Dec  5 20:24:36 NAS upsd[90850]: User [email protected] logged out from UPS [ups]
Dec  5 20:24:36 NAS upsd[90850]: mainloop: Interrupted system call
Dec  5 20:24:36 NAS upsd[90850]: Signal 15: exiting
Dec  5 20:24:36 NAS rc.nut: Network UPS Tools upsd 2.8.2
Dec  5 20:24:37 NAS usbhid-ups[90825]: WARNING: send_to_all: write 34 bytes to socket 9 failed (ret=-1), disconnecting: Broken pipe
Dec  5 20:24:37 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:37 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:37 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:38 NAS usbhid-ups[90825]: Signal 15: exiting
Dec  5 20:24:39 NAS rc.nut: fopen /var/run/nut/usbhid-ups-ups.pid: No such file or directory
Dec  5 20:24:39 NAS rc.nut: Network UPS Tools - UPS driver controller 2.8.2
Dec  5 20:24:43 NAS rc.nut: Writing NUT configuration...
Dec  5 20:24:46 NAS rc.nut: Updating permissions for NUT...
Dec  5 20:24:46 NAS rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Dec  5 20:24:46 NAS rc.nut: Enabling the NUT Runtime Statistics Module...
Dec  5 20:24:47 NAS rc.nut: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:47 NAS rc.nut: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
Dec  5 20:24:47 NAS rc.nut: USB communication driver (libusb 1.0) 0.47
Dec  5 20:24:47 NAS rc.nut: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:47 NAS rc.nut: No matching HID UPS found
Dec  5 20:24:47 NAS rc.nut: Driver failed to start (exit status=1)
Dec  5 20:24:47 NAS rc.nut: Network UPS Tools - UPS driver controller 2.8.2

     

    The only way to get it to work again is to uninstall and reinstall the plugin itself.

    Can you please help me?

     

    Thanks

     

    nut-debug-20241205203725.zip

    nut-debug-20241205203725.zip

  • Quote
    10 minutes ago, rgreco said:

    Hello,

     

    I installed your plugin since my brand new APC BGM2200-GR isn't natively recognized by Unraid.

     

    Your plugin works for some time, then it stops to work and I get all these warnings: 

    Dec  5 20:23:23 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:23 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:23 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:25 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:25 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:25 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:26 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:27 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:27 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:27 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:29 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:29 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:29 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:31 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:31 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:31 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:31 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:33 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:33 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:33 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:35 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:35 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:35 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:36 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:37 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:37 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:37 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:39 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:39 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:39 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:41 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:41 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:41 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:41 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:43 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:43 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:43 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:45 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:45 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:45 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:46 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:47 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:47 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:47 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:49 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:49 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:49 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:51 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:51 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:51 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:51 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:53 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:53 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:53 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:55 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:55 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:55 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:56 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:23:57 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:57 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:57 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:23:59 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:23:59 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:23:59 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:01 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:01 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:01 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:01 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:03 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:03 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:03 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:05 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:05 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:05 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:06 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:07 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:07 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:07 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:09 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:09 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:09 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:11 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:11 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:11 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:11 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:13 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:13 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:13 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:15 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:15 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:15 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:16 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:17 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:17 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:17 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:19 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:19 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:19 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:21 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:21 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:21 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:21 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:23 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:23 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:23 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:25 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:25 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:25 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:26 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:27 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:27 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:27 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:29 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:29 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:29 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:31 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:31 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:31 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:31 NAS upsmon[90853]: Poll UPS [[email protected]] failed - Data stale
Dec  5 20:24:31 NAS upsmon[90853]: UPS [email protected] is unavailable
Dec  5 20:24:33 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:33 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:34 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:35 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:35 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:36 NAS ool www[1149035]: /usr/local/emhttp/plugins/nut-dw/scripts/restart
Dec  5 20:24:36 NAS rc.nut: Stopping the NUT services... 
Dec  5 20:24:36 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:36 NAS rc.nut: Network UPS Tools upsmon 2.8.2
Dec  5 20:24:36 NAS upsmon[90853]: Signal 15: exiting
Dec  5 20:24:36 NAS upsd[90850]: User [email protected] logged out from UPS [ups]
Dec  5 20:24:36 NAS upsd[90850]: mainloop: Interrupted system call
Dec  5 20:24:36 NAS upsd[90850]: Signal 15: exiting
Dec  5 20:24:36 NAS rc.nut: Network UPS Tools upsd 2.8.2
Dec  5 20:24:37 NAS usbhid-ups[90825]: WARNING: send_to_all: write 34 bytes to socket 9 failed (ret=-1), disconnecting: Broken pipe
Dec  5 20:24:37 NAS usbhid-ups[90825]: #012Reconnecting. If you saw "nut_libusb_get_interrupt: Input/Output Error" or similar message in the log above, try setting "pollonly" flag in "ups.conf" options section for this driver!
Dec  5 20:24:37 NAS usbhid-ups[90825]: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:37 NAS usbhid-ups[90825]: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:38 NAS usbhid-ups[90825]: Signal 15: exiting
Dec  5 20:24:39 NAS rc.nut: fopen /var/run/nut/usbhid-ups-ups.pid: No such file or directory
Dec  5 20:24:39 NAS rc.nut: Network UPS Tools - UPS driver controller 2.8.2
Dec  5 20:24:43 NAS rc.nut: Writing NUT configuration...
Dec  5 20:24:46 NAS rc.nut: Updating permissions for NUT...
Dec  5 20:24:46 NAS rc.nut: Checking if the NUT Runtime Statistics Module should be enabled...
Dec  5 20:24:46 NAS rc.nut: Enabling the NUT Runtime Statistics Module...
Dec  5 20:24:47 NAS rc.nut: device->Product is NULL so it is not possible to determine whether to activate max_report_size workaround
Dec  5 20:24:47 NAS rc.nut: Network UPS Tools - Generic HID driver 0.53 (2.8.2)
Dec  5 20:24:47 NAS rc.nut: USB communication driver (libusb 1.0) 0.47
Dec  5 20:24:47 NAS rc.nut: libusb1: Could not open any HID devices: insufficient permissions on everything
Dec  5 20:24:47 NAS rc.nut: No matching HID UPS found
Dec  5 20:24:47 NAS rc.nut: Driver failed to start (exit status=1)
Dec  5 20:24:47 NAS rc.nut: Network UPS Tools - UPS driver controller 2.8.2

     

    The only way to get it to work again is to uninstall and reinstall the plugin itself.

    Can you please help me?

     

    Thanks

     

    nut-debug-20241205203725.zip

    nut-debug-20241205203725.zip 187.74 kB · 0 downloads

     

    Do you have another USB port you can try? This looks a bit like a USB port problem - 2.0 ports usually behave better. You can also try switching the backend to "preview (latest build)" in NUT Settings (requires reinstall of NUT or reboot of server) as we've introduced some APC patches recently that might also help here. Please let me know how it goes, I've got another thing we can try afterwards.

     

  • Quote
    8 minutes ago, Rysz said:

     

    Do you have another USB port you can try? This looks a bit like a USB port problem. You can also try switching the backend to "preview (latest build)" in NUT Settings (requires reinstall of NUT or reboot of server) as we've introduced some APC patches recently that might also help here. Please let me know how it goes, I've got another thing we can try afterwards.

     

    Hello,

     

    Thank you for your reply!

    I tried to change USB port and I also switched to "preview (latest build)" then I rebooted my NAS.

     

    As always I still have my UPS status this way:

    Screenshot2024-12-05205647.thumb.png.4bbbd5310c9cbc3a15483cdab27a8a5e.png

     

    And this is how it get recognized:

    Screenshot2024-12-05205612.thumb.png.e2b043de670dd756cefcfca9e0dc23a9.png

  • Quote
    2 minutes ago, rgreco said:

     

    Hello,

     

    Thank you for your reply!

    I tried to change USB port and I also switched to "preview (latest build)" then I rebooted my NAS.

     

    As always I still have my UPS status this way:

    Screenshot2024-12-05205647.thumb.png.4bbbd5310c9cbc3a15483cdab27a8a5e.png

     

    And this is how it get recognized:

    Screenshot2024-12-05205612.thumb.png.e2b043de670dd756cefcfca9e0dc23a9.png

     

    Looks good, let me know if it loses the connection again, then we can try another solution. 🙂 

  • Quote
    • Like 1
    1 minute ago, Rysz said:

     

    Looks good, let me know if it loses the connection again, then we can try another solution. 🙂 

     

    Okay, I'll keep you updated!


    Really thanks

  • Quote
    On 12/5/2024 at 8:52 AM, Masterwishx said:

    Thanks for cool future.

    Maybe you can add option 'copy nut log to flash on shutdown' like we have in syslog if you think it will be useful? 

     

    On 12/5/2024 at 2:59 PM, Masterwishx said:

    @Rysz Also will be cool to see var descriptions in NUT Details on hover from cmdvartab , if it possible to make and you will have time for it , also if you think its useful.

     

    Both features are implemented now in the latest update. 🙂 

  • Quote
    • Thanks 1
    1 hour ago, Rysz said:

    Both features are implemented now in the latest update

     

    Thanks a lot, the info on hover looks really cool, i think will be very useful for new users ...

    for persist on reboot only 200kb of nut log will be avalible?

     

  • Quote
    30 minutes ago, Masterwishx said:

     

    Thanks a lot, the info on hover looks really cool, i think will be very useful for new users ...

    for persist on reboot only 200kb of nut log will be avalible?

     

     

    Yes. Unraid log files are rotated at 1MB and 200KB is around 2000 medium-length log lines, which leaves enough room for new log lines after a system reboot.

  • Quote
    • Like 1
    On 12/5/2024 at 9:04 PM, Rysz said:

     

    Looks good, let me know if it loses the connection again, then we can try another solution. 🙂 

     

    Hello, the plugin stopped working again.

    You can find logs attached.

     

    nut-debug-20241207191435.zip

     

    Thanks!

  • Quote
    13 hours ago, rgreco said:

     

    Hello, the plugin stopped working again.

    You can find logs attached.

     

    nut-debug-20241207191435.zip 134.11 kB · 1 download

     

    Thanks!

     

    These kind of instabilities are very hard to diagnose, read here about possible reasons:

     

    The other possible solution, you can try putting this option at the end of ups.conf (after line 8) : 

    pollonly

    using the NUT Configuration Editor on NUT Settings page.

     

    Afterwards save the changes and restart NUT.

    Make sure that the extra option is still there after NUT was restarted. 🙂 

  • Quote
    22 hours ago, Rysz said:

    Yes. Unraid log files are rotated at 1MB and 200KB is around 2000 medium-length log lines, which leaves enough room for new log lines after a system reboot.

     

    Should be file like `nutlog-previous`  available after reboot in log , don't have it :(

  • Quote
    7 minutes ago, Masterwishx said:

     

    Should be file like `nutlog-previous`  available after reboot in log , don't have it :(

     

    It's the same logfile, if you click on the book icon, you'll see both the logs from before the reboot and after.

     

    grafik.thumb.png.bcff664dbacf62200bd306e89f1ad513.png

     

  • Quote
    • Like 1
    On 12/5/2024 at 11:07 AM, Glodenox said:

    I've added a task to my calendar to report here on any results. Thanks for the help already!

    A couple of days later: I haven't seen the notification any more, so that configuration has indeed fixed the issue. Thanks!

  • Quote
    • Thanks 1
    13 hours ago, Rysz said:

     

    These kind of instabilities are very hard to diagnose, read here about possible reasons:

     

    The other possible solution, you can try putting this option at the end of ups.conf (after line 8) : 

    pollonly

    using the NUT Configuration Editor on NUT Settings page.

     

    Afterwards save the changes and restart NUT.

    Make sure that the extra option is still there after NUT was restarted. 🙂 

    Hi man,

     

    It still doesn’t work.

     

    nas-syslog-20241208-2150.zip

     

  • Quote
    9 hours ago, rgreco said:

    Hi man,

     

    It still doesn’t work.

     

    nas-syslog-20241208-2150.zip 14.7 kB · 0 downloads

     

     

    Unfortunately there's not really much else I can suggest here other than what's posted in:

    Common reasons have included broken USB cables (could attempt new USB cable), USB ports (could attempt a different USB port), USB buses (either on the host system or the UPS itself) and/or overall instability of the UPS driver in combination with a specific USB bus (could attempt PCIe USB card, could try on another PC).

     

  • Quote

    Hi, I have a small issue with NUT that came to light this weekend in the big storm we had here in the UK. We had 4 power cuts lasting between 1 and 2.5 hours each, each time the server waited until the UPS reached 25% and then shutdown cleanly, but it didn't power off the UPS as it is set to do, so the server didn't automatically restart when the power returned! It protects the server as it should, just annoying that it doesn't come back up when power returns, especially when I'm away!

     

    UPS is a Riello Vision Rack 1100

    driver is riello_usb

     

    Thanks,

    Tim

  • Quote

    image.thumb.png.bd29bd6ac2055a06550b4e118df20611.pngI encountered an issue where I enabled UPS and manually unplugged the power to test the power outage situation. I found that NUT was able to send the shutdown command to Unraid, but shortly after, I received the message "UPS is online, any planned shutdowns were cancelled." Then, Unraid rebooted.

  • Quote

    • Join the conversation

    You can post now and register later. If you have an account, sign in now to post with your account.
    Note: Your post will require moderator approval before it will be visible.

    Guest
    Reply to this topic...
    Go to topic listing

    Account

    Navigation

    Search

    Search

    Configure browser push notifications
    Chrome (Android)
    1. Tap the lock icon next to the address bar.
    2. Tap Permissions → Notifications.
    3. Adjust your preference.
    Chrome (Desktop)
    1. Click the padlock icon in the address bar.
    2. Select Site settings.
    3. Find Notifications and adjust your preference.