search for: timeout

...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 timeout is generated? What does this 'select(1, [0], [], NULL, {60, 0}) = 0 (Timeout)' mean? Commandline =========== rsync -avH --del --rsync-path=/usr/local/sbin/rsync-debug.sh --one-file-system --exclude-from=/home/backup/excluded-dirs --include-from=/home/backup/included-dirs --timeout=...

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 think since a > n...

...interaction between the nouveau driver and the hardware on this system will randomly (I don't know the trigger) cause a severe slowdown, making the machine unusable. I'm appending the results of "journalctl -l | grep nouveau" in case this is helpful. Mostly it consists of "timeout" warnings, but there is a "FAULT" in there with an "at" value that I didn't previously find in bugzilla. Nov 29 00:24:50 localhost.localdomain kernel: fb: switching to nouveaufb from EFI VGA Nov 29 00:24:50 localhost.localdomain kernel: nouveau 0000:21:00.0: NVIDIA GP...

...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 (Timeout) select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) select(0, NULL, NULL, NULL,...

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 TE110P. Here are some configurations: /etc/zaptel.c...

...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 (Timeout) >> select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) >> select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) >> select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) >> select(0, NULL, NULL, NULL, {0, 50000}) = 0 (Timeout) >> select(0, NULL, NULL, NULL, {0, 50000...

...165 188.165.238.157 203.2.118.130 209.166.164.71 210.6.94.23 211.72.92.124 27.156.139.95 27.156.176.146 41.164.192.74 45.227.253.100 45.227.253.99 49.87.109.233 52.38.234.254 [root at ollie2 ~]# ipset list Name: fail2ban-sshd Type: hash:ip Revision: 4 Header: family inet hashsize 1024 maxelem 65536 timeout 3600000 Size in memory: 120 References: 0 Number of entries: 0 Members: Name: fail2ban-dovecot Type: hash:ip Revision: 4 Header: family inet hashsize 1024 maxelem 65536 timeout 3600000 Size in memory: 3768 References: 0 Number of entries: 41 Members: 185.211.245.198 timeout 4294522 [snip] 45.227.2...

...loads h264 files in vdpau mode instead of asserting ... But may be it will mess up things differently ..... I also run into this error: [ 5486.914351] nouveau 0000:01:00.0: disp: ERROR 1 [PUSHBUFFER_ERR] 02 [] chid 0 mthd 0000 data 00000400 [ 5488.914339] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5494.140509] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5496.144313] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5498.220935] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5500.232161] nouveau 0000:01:00.0: DRM: core notifier timeout [ 5502.263648] nouveau 0000:01:00.0: DRM: c...

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 sc...

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 timeo...

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 +++++++++--- ssh_config...

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...

...onW Unhandled dwOption 3 fixme:wininet:InternetSetOptionW Option 95 STUB fixme:wininet:InternetSetOptionW Option 39 STUB fixme:wininet:InternetSetOptionW Option 37 STUB fixme:winhttp:WinHttpGetIEProxyConfigForCurrentUser returning no proxy used fixme:winsock:WSAIoctl ignoring keepalive interval and timeout fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixme:winsock:WSAIoctl ignoring keepalive interval and timeout fixme:threadpool:RtlQueueWorkItem Flags 0x4 not supported fixm...

...the client end. I've replicated this when mirroring from a local CPAN mirror, and the issue seems to be that the server is timing out after it has sent the file list to the client but before the client has started transferring files. Despite what the documentation says about the default IO timeout being infinite (0), inspection of the code would seem to indicate otherwise: [io.c] /** If no timeout is specified then use a 60 second select timeout */ #define SELECT_TIMEOUT 60 : tv.tv_sec = io_timeout?io_timeout:SELECT_TIMEOUT; tv.tv_usec = 0; I haven't crawled through the initialisation...

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 p...

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 AssignedTo:...

..._to_all: SETINFO driver.version "2.7.3" 0.103118 send_to_all: SETINFO driver.version.internal "1.56" 0.103131 send_to_all: SETINFO driver.name "blazer_ser" 0.103141 Trying megatec protocol... 0.103687 send: 'Q1' 1.105456 read: timeout 1.105823 blazer_status: short reply 1.106058 Status read 1 failed 1.106825 send: 'Q1' 2.108171 read: timeout 2.108295 blazer_status: short reply 2.108338 Status read 2 failed 2.108638 send: 'Q1' 3.109987 read: timeout 3.1102...

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...

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] rsync error: timeout in data send/receive (code 30) at io.c(239) [sender=3.0.3pre1] 2009/12/14 00:20:04 [19046] io timeou...

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 (https://bugs.r-project.org/bugzilla3/show_bug.cgi?id=17203) > fo...