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

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

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 device will be created. No any programs from NUT package is not running. When I run: /lib/nut/usbhid-ups

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

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

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)

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 =

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

Oh, and I forgot to mention that "echo $SHELL" returns /bin/sh for me. Thank you. Regards, Kevin Mychal M. Ong Sr Infrastructure Engineer, Microsoft Technology Services - Messaging Global Infrastructure Operations Ingram Micro Inc. 4F Three World Square, 22 Upper McKinley Hill, Fort Bonifacio Taguig City, Philippines 1634 Direct +1-716-633-3600 ext. 33996 Mobile

[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

I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. It happens several times a day that I get a message about Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 Apr 3 16:41:54 kernel: [422586.041057] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 3 ret

I've got it ! Actually, it was obvious. A question of rights on the USB port. As soon as the process has the right rights (?) on the port, it runs smoothly. Sorry for the useless post... Regards, Pierre Boullier ----- Original Message ----- From: Pierre Boullier To: nut-upsuser at lists.alioth.debian.org Sent: Friday, November 12, 2010 3:18 PM Subject: usbhid-ups and APC Smart-UPS 1500

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

On Apr 3, 2014, at 3:40 PM, Adam Pribyl wrote: > I have nut 2.6.4-2.3+deb7u1 on debian 7 32bit, with UPS Eaton Nova AVR 1250 connected via USB. Which kernel version? > It happens several times a day that I get a message about > > Apr 3 16:41:49 kernel: [422581.049671] usb 5-1: usbfs: USBDEVFS_CONTROL failed cmd usbhid-ups rqt 161 rq 1 len 4 ret -110 > Apr 3 16:41:54 kernel:

No one knows anything about this? I've seen some references to this before, but no solutions? If there is more detailed information I can get from command line, please let me know what to run. Thanks! > Message: 1 > Date: Sat, 26 Apr 2014 13:43:11 -0700 > From: Everett Tsang <snufflebear87 at hotmail.com> > To: "nut-upsuser at lists.alioth.debian.org" >

Hi, my nut version is 2.2.2-6.4, debian lenny The ups we use is a tripplite OMNIVS1000 USB The drivers i tried are tripplite_usb and usbhid-ups, googled very long about the problems, but didn't get it to run. Does someone has experiences or similar problems? lsusb and lsmod are all right in /etc/udev/rules.d/52_nut-usbups.rules I found one line according to the modell ---- # Tripp Lite -

Hello ! I'm totally new with Linux, just migrating from NetWare. Our brand new server runs SuSE Linux Enterprise Server 11 Service Pack 1 SLED11 ships with NUT 2.2.2-69.11 I'm trying to setup NUT to communicate with our UPS over the USB cable. First, I've tried with a "standard" ups.conf. Error message : device is (or not yet) supported. Second attempt, including productid

Hi, Self-reply ftw, is it something to do with the permissions of the device that is created when the UPS is plugged in? I remember that Debian does have a pretty strict permissions structure, so do I have to fiddle the permissions of something in /dev? I'll try updating nut-server to version 2.6.4-2.3+deb7u1 in wheezy backports and report back - initial attempt to install from wheezy

NUT 2.6.5-4 Eaton 3S550 Windows 7 Pro x64 usbhid-ups is crashing if it is started without debugging. This UPS worked fine on my test system with the same OS, but since moving it to the system where it will be used, it's refusing to function with NUT. Looks like it is working with the Windows built-in drivers though. Thanks. -------------- next part -------------- A non-text attachment was

On 5/30/2017 10:47 PM, Charles Lepple wrote: > On May 22, 2017, at 11:13 AM, Mike <the.lists at mgm51.com> wrote: >> >> On 5/21/2017 10:39 AM, Charles Lepple wrote: [snip] > Even though the CPS sub-driver has been written already, I would like to take a look at the raw "explore" mode output: > >