Displaying 20 results from an estimated 5000 matches similar to: "A lot of EAGAIN (Resource temporarily unavailable) using nutdrv_qx"
2018 Jul 02
4
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,
2007 Jun 26
2
bcmxcp_usb and powerware 5115
Hello, ppl!
I try configure NUT for communicate with my Powerware 5115 UPS.
As root I run '/lib/nut/bcmxcp_usb -DDDD -u root -a ups', but driver
can't connect to my UPS.
Some output:
Network UPS Tools - BCMXCP UPS driver 0.10 (2.0.4)
debug level is '4'
usb_set_debug: Setting debugging level to 3 (on)
usb_os_init: Found USB VFS at /dev/bus/usb
usb_os_find_busses: Found 001
2014 Nov 06
0
nutdrv_atcl_usb
On Nov 5, 2014, at 4:39 PM, jani <jani.talikka at gmail.com> wrote:
> The output of the ldd command is:
> root at minime:~# ldd /lib/nut/nutdrv_atcl_usb
> linux-gate.so.1 (0xb7722000)
> libusb-0.1.so.4 => /lib/i386-linux-gnu/libusb-0.1.so.4 (0xb76fe000)
> libpthread.so.0 => /lib/i386-linux-gnu/i686/cmov/libpthread.so.0 (0xb76e2000)
>
2008 Jan 25
3
Bug#462468: nut: megatec_usb ups not detected since 2.2.1 update anymore
Hi Sven,
2008/1/25, Sven Koch <haegar at sdinet.de>:
> Package: nut
> Version: 2.2.1-1
> Severity: normal
>
> I am using a Mustec PowerMust 1000 USB, connected with a USB cable to
> the PC.
>
> With nut 2.2.0-2.1 everything works without problems - but since the
> 2.2.1-1 update the "upsdrvctl start" from the init script just fails,
> executing the
2011 Oct 03
2
patch: Replace many usleep and some sleep calls with nanosleep
Description: Replace many usleep and some sleep calls with nanosleep.
usleep is stated in its manual page as removed by POSIX.
Contrary to its predecessors, nanosleep semantics is well
defined. The replacement, which is mostly in drivers, is
untested. Supplements http://bugs.debian.org/633791.
Last-Update: Sat, 13 Aug 2011 14:04:48 +0300
Index:
2019 Jun 09
0
[PATCH libnbd] states: In recv_into_rbuf and send_from_wbuf loop until EAGAIN.
Previously we performed a single call to recv(2) or send(2) (or the
GnuTLS equivalents), and even if more data/space was immediately
available to receive/send we would return to poll. Instead of this,
loop until the socket returns EAGAIN.
---
generator/states.c | 91 ++++++++++++++++++++++------------------------
1 file changed, 43 insertions(+), 48 deletions(-)
diff --git a/generator/states.c
2019 Jul 30
0
[PATCH 01/13] amdgpu: remove -EAGAIN handling for hmm_range_fault
hmm_range_fault can only return -EAGAIN if called with the block
argument set to false, so remove the special handling for it.
Signed-off-by: Christoph Hellwig <hch at lst.de>
---
drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c | 23 +++--------------------
1 file changed, 3 insertions(+), 20 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/amdgpu_ttm.c
2016 Oct 28
0
Data Stale at random intervals
Hi Charles,
I've been monitoring for the past few days and NUT has been running solid. Tested and everything's working as it should. Thanks for all of your help on this, great to have it running well again and learned lot.
________________________________
From: Daniel Shields <grungelizard9 at hotmail.com>
Sent: Tuesday, October 25, 2016 8:01 PM
To: Charles Lepple
Subject:
2017 Apr 08
2
usbhid-ups: Failed to open device, skipping. (Permission denied)
Charles Lepple writes:
> On Sun, Apr 2, 2017 at 2:59 AM, Sam Varshavchik <mrsam at courier-mta.com>
> wrote:
> > Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite
> > UPS.
> >
> > I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb
> > gives:
> >
> > Bus 006 Device 002: ID 09ae:3016 Tripp
2019 Aug 28
2
[PATCH nbdkit] freebsd: In nbdkit_nanosleep, fallback to calling nanosleep(2).
Rather than failing to compile on platforms which lack POLLRDHUP such
as FreeBSD, simply fallback to the old method of sleeping.
This leaves the porting suggestions as a comment in case someone wants
to implement a better solution for particular platforms.
---
server/public.c | 38 ++++++++++++++++++++++++--------------
1 file changed, 24 insertions(+), 14 deletions(-)
diff --git
2005 May 08
0
EAGAIN when handling file uploads
Hey guys,
There''s a new ticket (1268) which covers someone getting EAGAIN from
cgi.rb when handling file uploads. So stdin.read is raising EAGAIN
and nothing is retrying, the error makes its way all the way up to the
controller. Is this something that we want to fix, or shall we just
report it to the cgi.rb maintainers?
http://dev.rubyonrails.org/ticket/1268
--
Cheers
Koz
2014 Jan 15
0
EAGAIN in dict proxy
Hello,
We?re using a custom program to manage quotas talking to dovecot via the dovecot dict proxy protocol over a unix socket:
plugin {
quota = dict:User quota::proxy:/var/run/auth_proxy_dovecot/quotasocket:quota
}
Dovecot gets slammed with quota requests periodically, seemingly because Thunderbird thought it would be a good idea to hardcode having a quota check at 45 seconds past the
2024 Nov 11
4
[PATCH 1/2] nouveau: handle EBUSY and EAGAIN for GSP aux errors.
From: Dave Airlie <airlied at redhat.com>
The upper layer transfer functions expect EBUSY as a return
for when retries should be done.
Fix the AUX error translation, but also check for both errors
in a few places.
Fixes: eb284f4b3781 ("drm/nouveau/dp: Honor GSP link training retry timeouts")
Signed-off-by: Dave Airlie <airlied at redhat.com>
---
2013 Nov 29
2
nsd 4.0 EAGAIN loop in sendmmsg(2)
On NetBSD 6.99.28-CURRENT, nsd 3.2.16 works fine, however nsd 4.0.0 is
spinning chewing CPU. The logs show:
Nov 28 23:07:00 xxx nsd[466]: sendmmsg failed: Resource temporarily
unavailable
ktruss shows it getting EAGAIN from sendmmsg(2) over and over again.
According to the man page:
[EAGAIN|EWOULDBLOCK]
The socket is marked non-blocking and the requested
2006 Aug 08
0
EAGAIN error in production.log
Hello,
I''m seeing quite a few of the following errors in my production log:
Errno::EAGAIN (Resource temporarily unavailable):
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/cgi_process.rb:184:
in `write''
/usr/local/lib/ruby/gems/1.8/gems/actionpack-1.12.3/lib/action_controller/cgi_process.rb:184:
in `out''
2020 Mar 24
0
Re: generator under Cygwin fails with: Fatal error: exception Unix.Unix_error(Unix.EAGAIN, "fork", "")
On 3/22/20 5:07 PM, sdaau wrote:
> Hi all,
>
> Copy of:
>
> generator under Cygwin fails with: Fatal error: exception Unix.Unix_error(Unix.EAGAIN, "fork", "") · Issue #45 · libguestfs/libguestfs
> https://github.com/libguestfs/libguestfs/issues/45
>
> ... since I realised late I shouldn't post on GitHub issues.
That could be a bug in the Cygwin
2016 Feb 13
2
nutdrv_qx - Device not supported
Hi
I have the RCT 3KVA Axpert solar hybrid inverter. It is also known as the
MPP Solar PIP-MS series, the IPS-4000WM and the Voltronic Axpert MKS. I am
trying to monitor the inverter using NUT on a Raspberry Pi (I have tried
Ubuntu as well with the same results). I have tried most of the drivers
with no success. The inverter came with the ViewPower software so I
assumed that my best chance
2003 Aug 07
2
nvi dying with "Resource temporarily unavailable"
Since I upgraded to FreeBSD 4.8 (from 4.5) I've noticed occasional failures
of nvi. It will suddenly die as a key is pressed, emitting:
Error: input: Resource temporarily unavailable
and you are staring at your command prompt.
I googled for this message and found that people here and there have been
complaining of this since about FreeBSD 4.2, but that absolutely none of
them have received
2007 Sep 18
7
[Bug 1365] New: sftp exits immediately after connection (fgets EAGAIN)
http://bugzilla.mindrot.org/show_bug.cgi?id=1365
Summary: sftp exits immediately after connection (fgets EAGAIN)
Product: Portable OpenSSH
Version: 4.7p1
Platform: All
OS/Version: Linux
Status: NEW
Keywords: patch
Severity: normal
Priority: P2
Component: sftp
AssignedTo: bitbucket at
2014 Nov 07
0
nutdrv_qx and Best Power equipment
> Sure enough, it turned off after about 30 seconds (t=228). I unplugged it for about five seconds, and it came back on three minutes after I plugged it back in. However, the bypass bit inversion might be responsible for this:
>
> 228.304623 send: 'Q1'
> 228.515426 read: '(119.0 119.0 000.0 000 60.0 13.5 XX.X 00001010'
> 228.515494 ups_infoval_set: non