search for: epipe

...eeping...) poll(0xFFBEF4B8, 2, 60000) = 1 poll(0xFFBEF218, 1, 60000) = 1 read(7, " ?\0\0\b", 4) = 4 poll(0xFFBEF218, 1, 60000) = 1 read(7, " r s y n c : c o n n e".., 63) = 63 poll(0xFFBEE0E8, 1, 60000) = 1 write(1, " ?\0\0\b r s y n c : c".., 67) Err#32 EPIPE Received signal #13, SIGPIPE [ignored] write(2, " r s y n c : w r i t e".., 81) Err#32 EPIPE Received signal #13, SIGPIPE [ignored] sigaction(SIGUSR1, 0xFFBEDAF8, 0xFFBEDB78) = 0 sigaction(SIGUSR2, 0xFFBEDAF8, 0xFFBEDB78) = 0 getpid() = 7970 [7969] Received signal #18, S...

...interrupt the pulling process with Ctrl-C, the process on the other side may start to allocate all memory on the remote machine. As fa as we have analyzed the problem, the remote rsync process wants to issue a error message that it could not write 4096 bytes, receives a SIGPIPE and errno is set to EPIPE in the fwrite call (line 279 in log.c). Then exit_cleanup is called which in turn will call the same routine again and will of course get EPIPE again and the loop continues (as long as we have memory to recursivly call the same functions again and again). As a quick workaround we have the followin...

With python 3, we have a nicer way to handle socket.error with errno set to EPIPE (or ESHUTDOWN). This is also more correct since in some cases (that I could not reproduce yet with v2v), using e[0] with BrokenPipeError will fail with: >>> OSError(errno.EPIPE, "Broken pipe")[0] Traceback (most recent call last): File "<stdin>", line 1, in &l...

https://bugzilla.mindrot.org/show_bug.cgi?id=2469 Bug ID: 2469 Summary: ssh connection hangs indefinitely on EPIPE Product: Portable OpenSSH Version: 7.1p1 Hardware: All OS: Solaris Status: NEW Severity: major Priority: P5 Component: ssh Assignee: unassigned-bugs at mindrot.org Reporter: tomas.kuthan at...

...e in libnbd CI when a poorly-written > >> eval script did not consume all of stdin during .pwrite. As behaving > >> as a data sink can be a somewhat reasonable feature of a > >> quickly-written sh or eval plugin, we should not be so insistent as > >> treating an EPIPE failure as an immediate return of EIO to the client. > > > > I was thinking about this over night, and came to the conclusion that > > it's always fine to ignore EPIPE errors. > > Interesting; I formed the opposite impression! > > > For example a script might...

...her transient failure in libnbd CI when a poorly-written >> eval script did not consume all of stdin during .pwrite. As behaving >> as a data sink can be a somewhat reasonable feature of a >> quickly-written sh or eval plugin, we should not be so insistent as >> treating an EPIPE failure as an immediate return of EIO to the client. > > I was thinking about this over night, and came to the conclusion that > it's always fine to ignore EPIPE errors. Interesting; I formed the opposite impression! > For example a script might > be processing the input data...

Remove the printing of harmless ERRORS like ECONNRESET, EPIPE. For more details, see http://oss.oracle.com/bugzilla/show_bug.cgi?id=865 The ocfs2 kernel source code in git tree don't have function "ocfs2_file_sendfile", so this bug only exists in ocfs2-1.2 branch. -------------- next part -------------- Index: fs/ocfs2/file.c ================...

...hen a socket is closed on the other end? From Andrew Gierth ( andrew at erlenstar.demon.co.uk): AFAIK: If the peer calls close() or exits, without having messed with SO_LINGER, then our calls to read() should return 0. It is less clear what happens to write() calls in this case; I would expect EPIPE, not on the next call, but the one after. If the peer reboots, or sets l_onoff = 1, l_linger = 0 and then closes, then we should get ECONNRESET (eventually) from read(), or EPIPE from write(). I should also point out that when write() returns EPIPE, it also raises the SIGPIPE signal - you nev...

I hit another transient failure in libnbd CI when a poorly-written eval script did not consume all of stdin during .pwrite. As behaving as a data sink can be a somewhat reasonable feature of a quickly-written sh or eval plugin, we should not be so insistent as treating an EPIPE failure as an immediate return of EIO to the client. Signed-off-by: Eric Blake <eblake at redhat.com> --- I probably need to add unit test coverage of this before committing (although proving that I win the data race on a client process exiting faster than the parent can write enough data t...

...> I hit another transient failure in libnbd CI when a poorly-written > eval script did not consume all of stdin during .pwrite. As behaving > as a data sink can be a somewhat reasonable feature of a > quickly-written sh or eval plugin, we should not be so insistent as > treating an EPIPE failure as an immediate return of EIO to the client. I was thinking about this over night, and came to the conclusion that it's always fine to ignore EPIPE errors. For example a script might be processing the input data gradually and then encounter an error and want to exit immediately. We a...

...IPE (Illegal seek) 0.000057 getsockname(19, {sa_family=AF_LOCAL, NULL}, [2]) = 0 0.000043 epoll_ctl(15, EPOLL_CTL_ADD, 19, {EPOLLIN|EPOLLPRI|EPOLLERR|EPOLLHUP, {u32=850618928, u64=140128453618224}}) = 0 0.000040 write(19, "VERSION\tauth-worker\t1\t0\nDBHASH\t5"..., 97) = -1 EPIPE (Broken pipe) 0.000035 --- SIGPIPE {si_signo=SIGPIPE, si_code=SI_USER, si_pid=17956, si_uid=108} --- 0.000020 epoll_wait(15, {{EPOLLIN|EPOLLHUP, {u32=850618928, u64=140128453618224}}}, 14, 12614) = 1 0.000031 read(19, "", 8192) = 0 0.000026 epoll_ctl(15, EPOLL_C...

Folks, I have been working on a problem with the usbhid-ups driver and the MGE / Eaton Ellipse series UPS. There seems to be light at the end of the tunnel. For whatever reason, these devices seem to trigger error 'EPIPE' randomly. So far, the response to this of the usbhid-ups (and previously, newhidups) driver is to reconnect. Most of the time this will succeed on the first try and nothing will be logged to the syslog. At times however, this will take several tries before this succeeds, causing a lo...

...tten > >>>> eval script did not consume all of stdin during .pwrite. As behaving > >>>> as a data sink can be a somewhat reasonable feature of a > >>>> quickly-written sh or eval plugin, we should not be so insistent as > >>>> treating an EPIPE failure as an immediate return of EIO to the client. > >>> > >>> I was thinking about this over night, and came to the conclusion that > >>> it's always fine to ignore EPIPE errors. > >> > >> Interesting; I formed the opposite impression! &g...

Since we upgraded to Rails 1.0 and lighty last week we''ve had the rails application crash daily with the following error in the production.log file: Errno::EPIPE (Broken pipe): /usr/local/lib/ruby/1.8/mysql.rb:1042:in `flush'' /usr/local/lib/ruby/1.8/mysql.rb:1042:in `write'' /usr/local/lib/ruby/1.8/mysql.rb:462:in `write'' /usr/local/lib/ruby/1.8/mysql.rb:436:in `command'' /usr/local/lib/ruby/1.8/mysql.rb...

This small example will make icecast unusable after few seconds. The problem resides on EPIPE received when trying to send the first (58) bytes of the vorbis predata. Change the URL for your own, and try it in a LAN. I have no idea on the reasons of these errors, altough I suspect it's related to the fact that the headers are sent in blocking state and then we change to non-blockin...

1. On my Windows development system everything is fine. 2. On my Linux production server I get an Errno::EPIPE (Broken pipe) error when sending an email using Action Mailer. The specific situation is this: a) Rails 1.1.2 b) The application is running UTF8, but I want to send my emails as ISO-8859-1. c) Sending UTF-8 emails works fine. d) Delivery method is SMTP. e) When using this code ------------- def...

...> I hit another transient failure in libnbd CI when a poorly-written > eval script did not consume all of stdin during .pwrite. As behaving > as a data sink can be a somewhat reasonable feature of a > quickly-written sh or eval plugin, we should not be so insistent as > treating an EPIPE failure as an immediate return of EIO to the client. > > Signed-off-by: Eric Blake <eblake at redhat.com> > --- > > I probably need to add unit test coverage of this before committing > (although proving that I win the data race on a client process exiting > faster than...

I have a rails app serving up XML on an infrequent basis. This is being run with mongrel and mysql. I''ve found that if the app does not get exercised for longer than a few hours it goes dead ("Lost Connection to MySQL") and starts throwing Errno::EPIPE errors. It seems that the mysql connection gets timed out for inactivity or something like that. It can be restarted with ''mongrel_rails restart -P /path/to/the/mongrel.pid'' ... but that''s not really a solution. My collaborator expects the app to be there when he is work...

...transient failure in libnbd CI when a poorly-written > > eval script did not consume all of stdin during .pwrite. As behaving > > as a data sink can be a somewhat reasonable feature of a > > quickly-written sh or eval plugin, we should not be so insistent as > > treating an EPIPE failure as an immediate return of EIO to the client. > > > > Signed-off-by: Eric Blake <eblake at redhat.com> > > --- > > > > I probably need to add unit test coverage of this before committing > > (although proving that I win the data race on a client pr...

...doesn't really tell me anything, so I have someone can tell me what is happening here. I have included the tail below. Thank you in advance! Jonathan [pid 16545] rt_sigaction(SIGTERM, {0x8056330, [TERM], SA_RESTART}, <unfinished ...> [pid 16546] <... sendmsg resumed> ) = -1 EPIPE (Broken pipe) [pid 16545] <... rt_sigaction resumed> {SIG_DFL}, 8) = 0 [pid 16546] --- SIGPIPE (Broken pipe) @ 0 (0) --- [pid 16545] rt_sigaction(SIGPIPE, {SIG_IGN}, <unfinished ...> [pid 16546] write(2, "\1Ffd_send(-1) failed: Broken pip"..., 34 <unfinished ...> [pid 1...