similar to: No run cmd /usbhid-ups -k !

On 01/07/2018 11.53, icingaj at gmail.com wrote: > Good day. > > Can not perform shutdowns Ups. Please help. > > Details of our installation are: > OS: Turris Omnia (TO) > NUT version: 2.7.4-5 > Installation method: from package > UPS device: EATON UPS 5SC 500i , 230V, 350W, 500VA, USB bought in jun 2018 > > If you connect to TO UPS via USB, the /dev/hidraw0

I used strace and the result is bus is busy: clock_gettime(CLOCK_MONOTONIC, {8158, 708518222}) = 0 timerfd_settime(11, TFD_TIMER_ABSTIME, {it_interval={0, 0}, it_value={8159, 708518000}}, NULL) = 0 ioctl(12, USBDEVFS_SUBMITURB, 0x40810) = 0 poll([{fd=7, events=POLLIN}, {fd=9, events=POLLIN}, {fd=11, events=POLLIN}, {fd=12, events=POLLOUT}], 4, 60000) = 1 ([{fd=12, revents=POLLOUT}]) ioctl(12,

Hi all. UPS is Eaton 5SC 500i. I tested three solutions: 1. swap "usbhid-ups -a qnapups" with "usbhid-ups -a qnapups -k" Result: server shutdown, but ups does not shut off! 2. run prog with params "upsmon -c fsd" Result: server shutdown, but ups does not shut off! 3. run prog "upscmd -u name -p passwd qnapups shutdown.return" and next

Set with upsrw: ups.delay.shutdown=60 is the same as offdelay = 30. This time was done correctly by UPS. Set with upsrw: ups.delay.start=90 is the same as ondelay = 40. The UPS shut down and reset and forget about the settings. If I use the program in Win 10 settings in the program from Eaton are stable!? Jan. > -----Original Message----- > From: Nut-upsuser

Hello, I'm trying to setup a UPS configuration whereas I have one physical UPS but two UPS entities loaded by the system used by different network slaves. In my ups.conf configuration I have ... [ups] driver = apcsmart port = /dev/ttyS0 desc = "APC UPS" [qnapups] driver = dummy-ups port = ups at localhost desc = "APC UPS for

On Sep 12, 2013, at 7:47 PM, Derek Rachul <drachul at gmail.com> wrote: > I tried reversing the order of the definitions in the config file, and it does seem to change the order in which they're loaded (at least according to the system logs) however the error remains. I don't have any experience using the dummy-ups driver on the same host as the real UPS driver, so this is a

Now I have this in /etc/nut/upsmon.conf (my QNAP NAS wants admin and 123456 or not working) RUN_AS_USER root MONITOR qnapups at localhost 1 admin 123456 master MONITOR qnapups at 192.168.222.252 3493 admin 123456 slave MINSUPPLIES 1 SHUTDOWNCMD "/sbin/shutdown -h +0" POLLFREQ 5 POLLFREQALERT 5 HOSTSYNC 15 DEADTIME 15 POWERDOWNFLAG /etc/killpower NOTIFYFLAG ONLINE SYSLOG+EXEC

Hi, Has anyone managed to get a Plexus UPS talking to their NAS. I've followed the excellent instructions here http://forum.qnap.com/viewtopic.php?f=182 <http://forum.qnap.com/viewtopic.php?f=182&t=35970&start=0> &t=35970&start=0 but I'm not there yet. When I manually start upsdrvctl without the UPS plugged in I get [~] # /usr/bin/upsdrvctl start Network UPS

Hi! Some systems I have take some time to shut down, so I would like them to shut down if the UPS have been on battery for 2 minutes. Internet has told me that SHUTDOWNCMD ?/sbin/shutdown -h +0? in /etc/nut/upsmon.conf will execute when the UPS is both OB (on battery) and LB (Low battery). Like in wiki.ipfire.org - Detailed NUT Configuration<https://wiki.ipfire.org/addons/nut/detailed>

Hi, Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during power outage. I configured QNAP properly (like this: http://geekbeat.tv/qnap-adding-external-devices-qnap), but I don't know what to do next. I work

I've searched for quite some time and read the FAQ, but to no avail. I have a UPS connected to a NAS. Unfortunately I have to specify every single client IP (ups slave), because the stupid NAS system (QNAP) does not allow me to set a /16 or /24. Changing the config files manually does not work either, because the service won't come up anymore. (One has to love QNAP at this point.) Thus I

Sorry i forgot send info from: # /lib/nut/usbhid-ups -DD -x explore -a qnapups &> usbhid-ups.debug.log Thx Jan. -------------- next part -------------- A non-text attachment was scrubbed... Name: usbhid-ups.debug.log Type: application/octet-stream Size: 23064 bytes Desc: not available URL:

[please keep the list CC'd. Thanks!] On Sep 16, 2013, at 8:11 PM, Derek Rachul <drachul at gmail.com> wrote: > On Mon, Sep 16, 2013 at 4:36 PM, Charles Lepple <clepple at gmail.com> wrote: >> On Sep 12, 2013, at 7:47 PM, Derek Rachul <drachul at gmail.com> wrote: >> >> > I tried reversing the order of the definitions in the config file, and it does

Hi all, I am trying to get a APC Back-UPS CS 500 running on my QNAP 419P Nas. Since on all my work I figure out the following: from Network UPS Tools upscmd 2.4.1 [~] # upscmd -l qnapups Instant commands supported on UPS [qnapups]: beeper.disable - Disable the UPS beeper beeper.enable - Enable the UPS beeper beeper.mute - Temporarily mute the UPS beeper beeper.off - Obsolete (use

On Tue, 3 Jul 2018, rakoi at mail.telekom.sk wrote: > UPS is Eaton 5SC 500i. > Please do not know how to write some parameters permanently to UPS? Read man ups.conf and man usbhid-ups and try setting the required values in ups.conf. For example [Eaton] driver = usbhid-ups port = auto desc = "Eaton 5sc 500i" offdelay = 30 ondelay =

On Jul 2, 2018, at 9:02 AM, icingaj at gmail.com wrote: > > ioctl(12, USBDEVFS_CLAIMINTERFACE, 0xbecf910c) = -1 EBUSY (Resource busy) > ioctl(12, USBDEVFS_GETDRIVER, 0xbecf9024) = 0 > writev(2, [{"Can't claim USB device [0463:fff"..., 62}, {NULL, 0}], 2Can't > claim USB device [0463:ffff]: No such file or directory > ) = 62 > exit_group(1)

[please use reply-all to include the list - the headers are not mangled] On Oct 25, 2016, at 9:53 AM, Tomasz Przychodzie? wrote: > > Hi, > > Another beginner question. I spend hours trying to find the solution for how to configure winnut properly but I' struggling to make it work. I want my QNAP NAS TS-231 to work as a master and send signal to the PC to shut it down during

Hi, I keep getting the following messages (or similar) in my syslog: Nov 23 11:38:08 io kernel: [763936.921566] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -110 Nov 23 11:38:08 io kernel: [763936.972569] usb 3-2: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 5 ret -75 Nov 23 11:38:08 io kernel: [763936.976568] usb 3-2: usbfs: USBDEVFS_CONTROL

Thanks for the libusb version numbers. By the way, which version of NUT are you using? On Dec 31, 2015, at 6:23 PM, Nicholas Leippe <leippe at gmail.com> wrote: > > I haven't cracked open the nut sources yet, but am curious why it should fail to open the usb device after already succeeding many times. > Could it be a USB power management issue? Or simply opening it too many

# ldd /lib64/nut/usbhid-ups linux-vdso.so.1 (0x00007ffdfe3e3000) libusb-0.1.so.4 => /lib64/libusb-0.1.so.4 (0x00007f98526e6000) <-- from libusbp-compat-0.1.5-r2 libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f98524ca000) libc.so.6 => /lib64/libc.so.6 (0x00007f985212f000) libusb-1.0.so.0 => /lib64/libusb-1.0.so.0 (0x00007f9851f17000) <--