Jump to content

fezster

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

fezster's Achievements

Noob

Noob (1/14)

1

Reputation

  1. Try enabling "Host access to custom networks" under Settings -> Docker (need to disable Docker first).
  2. Found the new version of the plugin has USB power management override Will see if that may have been the reason for the disconnection and if this setting helps.
  3. Unplugging the USB and reconnecting has resolved it. Not ideal, though (esp as it lost communication silently). Any ideas? EDIT - I should also add, it was running perfectly fine for 8 days prior to that, before throwing that error in the log yesterday.
  4. I noticed I randomly started getting this error yesterday: Mar 1 12:05:43 SM1 usbhid-ups[15531]: nut_libusb_get_report: Input/Output Error Mar 1 12:05:57 SM1 usbhid-ups[15531]: libusb1: Could not open any HID devices: insufficient permissions on everything Mar 1 12:05:57 SM1 upsd[15590]: Data for UPS [ups] is stale - check driver Mar 1 12:06:00 SM1 upsmon[15594]: Poll UPS [[email protected]] failed - Data stale Mar 1 12:06:00 SM1 upsmon[15594]: Communications with UPS [email protected] lost It just repeats itself all the way to today. Only noticed because the dashbaord was not showing the UPS status anymore (no alert or error in Unraid). Tried to restart NUT server and got this: Mar 2 12:17:08 SM1 root: Stopping the NUT services... Mar 2 12:17:08 SM1 upsmon[15594]: Signal 15: exiting Mar 2 12:17:08 SM1 root: Network UPS Tools upsmon 2.8.1 Mar 2 12:17:08 SM1 upsd[15590]: User [email protected] logged out from UPS [ups] Mar 2 12:17:08 SM1 upsmon[15593]: upsmon parent: read Mar 2 12:17:08 SM1 upsd[15590]: mainloop: Interrupted system call Mar 2 12:17:08 SM1 upsd[15590]: Signal 15: exiting Mar 2 12:17:08 SM1 root: Network UPS Tools upsd 2.8.1 Mar 2 12:17:10 SM1 usbhid-ups[15531]: Signal 15: exiting Mar 2 12:17:10 SM1 usbhid-ups[15531]: WARNING: send_to_all: write 38 bytes to socket 16 failed (ret=-1), disconnecting: Broken pipe Mar 2 12:17:11 SM1 root: Network UPS Tools - UPS driver controller 2.8.1 Mar 2 12:17:15 SM1 root: Writing NUT configuration... Mar 2 12:17:17 SM1 root: Updating permissions for NUT... Mar 2 12:17:17 SM1 root: Checking if the NUT Runtime Statistics Module should be enabled... Mar 2 12:17:17 SM1 root: Disabling the NUT Runtime Statistics Module... Mar 2 12:17:18 SM1 root: Network UPS Tools - Generic HID driver 0.52 (2.8.1) Mar 2 12:17:18 SM1 root: USB communication driver (libusb 1.0) 0.46 Mar 2 12:17:18 SM1 root: libusb1: Could not open any HID devices: insufficient permissions on everything Mar 2 12:17:18 SM1 root: No matching HID UPS found Mar 2 12:17:18 SM1 root: Driver failed to start (exit status=1) Mar 2 12:17:18 SM1 root: Network UPS Tools - UPS driver controller 2.8.1 Running nutscanner, it does find the UPS: root@SM1:~# nut-scanner -U Cannot load XML library (libneon.so) : file not found. XML search disabled. Cannot load IPMI library (libfreeipmi.so) : file not found. IPMI search disabled. Scanning USB bus. [nutdev1] driver = "usbhid-ups" port = "auto" vendorid = "0764" productid = "0501" bus = "002" device = "028" busport = "001" ###NOTMATCHED-YET###bcdDevice = "0001" root@SM1:~# As does lsusb: root@SM1:~# lsusb Bus 001 Device 002: ID 0930:6545 Toshiba Corp. Kingston DataTraveler 102/2.0 / HEMA Flash Drive 2 GB / PNY Attache 4GB Stick Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 028: ID 0764:0501 Cyber Power System, Inc. CP1500 AVR UPS Bus 002 Device 003: ID 0e0f:0002 VMware, Inc. Virtual USB Hub Bus 002 Device 002: ID 0e0f:0003 VMware, Inc. Virtual Mouse Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Will try a restart in a bit. Other posts on this topic suggest a dying USB port or cable - but I'm not sure, as it has been working fine.
  5. Agreed, appreciate the input. On a slightly different topic - I see increased CPU utilization with NUT running. I'm using a Cyberpower BR700ELCD with the usbhid-ups driver. I've changed the pollinterval to 15 which has helped, but I see consistent spikes (which arent there if I shut down NUT). Is this normal? [ups] driver = usbhid-ups port = auto # If not in manual mode, put any additional settings below this line desc = "BR700ELCD" offdelay = 180 ondelay = 0 ignorelb override.battery.charge.low = 20 override.battery.charge.warning = 40 pollinterval = 15
  6. Thank you - I expected as much. I have everything working as required with the GUI settings, so was only looking for an easy way to add an additional script to run as part of the shutdown sequence. It's not easy to modify rc.nut / rc.0 / rc.6 - maybe as a future enhancement a GUI option could be added for an additional script to run just before shutdown? Thanks for this plugin btw!
  7. Is it possible to use upssched with this plugin? NOTIFYCMD "/usr/sbin/nut-notify" I believe no, as the notifycmd has to be upssched-cmd - or is there an alternative way to run a custom script *after* the server has been forced to shutdown? (I want to run a script to shutdown my esxi server, but want to ensure this Unraid VM has all but finished before doing so). At the moment, I am using UserScripts to do it on Array Shutdown, but upssched would be cleaner.
×
×
  • Create New...