search for: timeouts

I have been having broken pipe messages for a while. I think since a network architecture change. But I am not sure because I have not been monitoring the errors closely before. I added this (https://rsync.samba.org/issues.html) rsync-debug.sh script with strace of 100. But I have no idea how to interper this output. I guess between 00:55:41 and 03:06:47 nothing is happening? And then some

From man 2 select: int select(int nfds, fd_set *readfds, fd_set *writefds, fd_set *exceptfds, struct timeval *timeout); So, it is waiting for file descriptor #1 to become available with a 60 second timeout which it is hitting. Use lsof to find out what file descriptor #1 is. On 01/22/2018 10:07 AM, Marc Roos via rsync wrote: > > I have been having broken pipe messages for a while. I

https://bugs.freedesktop.org/show_bug.cgi?id=108906 Bug ID: 108906 Summary: nouveau driver causes system slowdown Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee:

Hi, >From time to time, I see check-all hang during running of lit tests. The hang always happens at the > 90% completion stage and I'm pretty sure all tests have been run and check-all is just waiting for lit/python to exit. I see a single python processing running, taking very little CPU time. An strace of that process shows this: select(0, NULL, NULL, NULL, {0, 50000}) = 0

Every so often, and it seems that it happens only when a call is in progress, all 24 Zap channels get reset. All channels are opened and then timeout. This causes the in-progress calls to terminate. There are no corresponding Red/Yellow alarms on wither the PBX or Asterisk although we do receive a fair amount of Blue Alarms. The Asterisk server is connected to a legacy PBX through a Digium

Hi David, Chandler, I see lldb tests hang often, and then I kill the dotest process. I'd like to stop running check-all too, but I feel it's important when I modify FileCheck. The flakiness that Chandler mentioned makes it time-consuming to verify test results. Joel On Wed, Jan 2, 2019 at 4:41 PM Chandler Carruth via llvm-dev < llvm-dev at lists.llvm.org> wrote: > What

On Saturday 20 April 2019 00:32:43 Pete Biggs wrote: > What ban action do you use? If it's something like iptables-multiport, > then I wonder if the fact that it's detecting the failures as > '[dovecot]' means that it's using the dovecot ports, not the exim > ports, when applying the iptable rule. > > When a host has been banned, can you look at the

here: diff --git a/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c b/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c index 53f5db0003d..efd9cf2b004 100644 --- a/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c +++ b/src/gallium/drivers/nouveau/nouveau_vp3_video_vp.c @@ -365,7 +365,7 @@ nouveau_vp3_fill_picparm_h264_vp(struct nouveau_vp3_decoder *dec, refs[j] = (struct

Hi , I was wondering if anyone else has tried to use the Timeout::timeout method in a backgroundrb Worker and had Timeout raise an exception after the allotted amount of time . I ask because i have written a test script to make sure Timeout would work . I have tested the script by directly feeding it to ruby with : $ ruby test_script.rb and piping the script to the rails console: $

Hi, A feature I've wanted in lit for a while is a having a timeout per test. Attached are patches that implement this idea. I'm e-mailing llvm-dev rather than llvm-commits because I want to gather more feedback on my initial implementation and hopefully some answers to some unresolved issues with my implementation. Currently in lit you can set a global timeout for all of the tests but

This change allows use of untrusted X11 forwarding (which is more secure) without requiring users to choose a finite timeout after which to refuse new connections. This matches the semantics of the X11 security extension itself, which also treat a validity timeout of 0 on an authentication cookie as indefinite. Signed-off-by: Trixie Able <table at inventati.org> --- clientloop.c | 12

The following commit managed to not actually add the --foreground option to the timeout command, just test for it. Add it this time. commit 681488877456b83f039dc518861f29ab4e1857f0 Author: Richard W.M. Jones <rjones@redhat.com> Date: Thu Dec 19 08:21:53 2013 +0000 run: Use timeout --foreground option. If timeout doesn't have this option (RHEL 6) don't use timeout

Hi, I got selected for beta testing SW:TOR and managed to get the installer to work on wine but it keeps crashing when I try with the launcher. It opens for a smidgen then crashes. Here's all the script I get; fixme:iphlpapi:NotifyAddrChange (Handle 0x32e604, overlapped 0x8f8d58): stub fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:winsock:WSALookupServiceBeginW (0x32e628

I've been getting frequent io errors trying to synchronise a local CPAN mirror with the master on ftp.funet.fi, the symptoms being the dreaded rsync: connection unexpectedly closed (0 bytes read so far) rsync error: error in rsync protocol data stream (code 12) at io.c(165) message at the client end. I've replicated this when mirroring from a local CPAN mirror, and the issue seems to

Hi R developers, I observed that system(timeout=) may still return exit code 0, when killing the process due to timeout. In src/unix/sys-unix.c there is #define KILL_SIGNAL1 SIGINT #define KILL_SIGNAL2 SIGTERM #define KILL_SIGNAL3 SIGKILL #define EMERGENCY_TIMEOUT 20 After little bit of debugging I observed that total time of system call is provided timeout value + 20s. That means

https://bugzilla.netfilter.org/show_bug.cgi?id=880 Summary: ipset doesn't refresh the timeout for an existing entry when the table is FULL. Product: ipset Version: unspecified Platform: x86_64 OS/Version: Fedora Status: NEW Severity: normal Priority: P5 Component: default

No progress has been made: cable is UPS - PC 6 - 3 7 - 5 9 - 2 for ./blazer_ser -DDDDD -a infosec 0.000000 send_to_all: SETINFO driver.parameter.port "/dev/ttyS1" 0.000323 debug level is '5' 0.103068 send_to_all: SETINFO device.type "ups" 0.103104 send_to_all: SETINFO driver.version "2.7.3" 0.103118 send_to_all: SETINFO

There's something weird going on for certain non-integer values of argument 'timeout' to base::socketSelect(). For such values, there is no timeout and you effectively end up with an infinite timeout. I can reproduce this on R 3.3.1 on Ubuntu 16.04 and RedHat 6.6, but not on Windows (via Linux Wine). # 1. In R master session > con <- socketConnection('localhost', port

Hi I already wrote about this problem half a year ago but didn't get an answer: http://lists.samba.org/archive/rsync/2009-June/023412.html I'm using rsync 3.0.3 on a NAS. In the parameter list I use --timeout=1800. But still I often have rsync stall much longer than that. Some examples: 2009/12/14 23:14:35 [8707] io timeout after 11670 seconds -- exiting 2009/12/14 23:14:35 [8707]

Fixed in 73470 Best, Tomas On 10/05/2017 06:11 AM, Henrik Bengtsson wrote: > I'd like to follow up/bump the attention to this bug causing the > timeout to fail for socketSelect() on Unix. It is still there in R > 3.4.2 and R-devel. I've identified the bug in the R source code - the > bug is due to floating-point precisions and comparison using >=. See > PR17203