similar to: linux sockets on centos (slightly off topic)

I am experiencing intermittent network failures on rsync 3.0.7 built using cygwin for Windows-XP (SP2). I am using GCC v4.4.2 and the latext version of cygwin. The rsync error long indicates things like: rsync: writefd_unbuffered failed to write 4092 bytes to socket [generator]: Connection reset by peer (104)rsync: read error: Connection reset by peer (104) rsync error: error in rsync

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

We have a service that clients use to upload files. We have a couple of clients that are on slow links and so their upload times out. We get errors in the logs that I''d like to get rid of. I was hoping that the recent commit 24b9f66dcdda44378b4053645333ce9ce336b413 would help us, but it does not. After digging in a bit, I have some ideas about why and a patch I''d like comments

Hi all, I''ve got an issue that only ever appears in production mode. I''ve got my app hooked up to amazon''s web service (ECS, using ruby/amazon from http://www.caliban.org/ruby/ruby-amazon.shtml). In the dev environment, everything''s peachy. But in production mode, after I''ve left the app up for a couple of hours (sometimes, minutes), I get an

I would like to remove setsockopt(SO_LINGER), as there does not seem to be a reason for its use. If you know of specific reasons we should keep any of these let me know, or run this patch in local test trees where possible. This is against OpenBSD, but should apply to portable with some fuzz. Index: channels.c =================================================================== RCS file:

Zed: 1) Error: test_more_web_server(HandlersTest): EOFError: end of file reached I solved this changing the following lines in test_handlers.rb:75-76 res = hit([ "http://127.0.0.1:9998/", "http://127.0.0.1:9998/test", I cannot solve the other failures: 1) Failure: test_header_is_too_long(WebServerTest) [./test/test_ws.rb:93:in

Hi, we ran into a little problem with rsync-2.5.5. Setup: you run rsync-2.5.5 as normal rsync over ssh (ie. not connecting to a rsync server). If you start such a rsync but 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

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

All, I see the following message fairly frequently in our nsd.log files: error: failed reading from tcp: Connection reset by peer A quick grep through the source code reveals that this log message comes from server.c, and can come pretty much at any time during a TCP query. Since: - This condition occurs during normal operation, and - There is nothing a server operator can do about it. I

On 8/31/23 10:02, Richard W.M. Jones wrote: > > On Wed, Aug 30, 2023 at 05:21:19PM -0500, Eric Blake wrote: >> 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

On Wed, Aug 30, 2023 at 05:21:19PM -0500, Eric Blake wrote: > 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

On Thu, Aug 31, 2023 at 11:12:59AM +0200, Laszlo Ersek wrote: > On 8/31/23 10:02, Richard W.M. Jones wrote: > > > > On Wed, Aug 30, 2023 at 05:21:19PM -0500, Eric Blake wrote: > >> 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

Every few days I find that dovecot auth is using all my CPU. This is from dovecot 2.2.13, I've just upgraded to 2.2.18 strace -r -p 17956 output: Process 17956 attached 0.000000 lseek(19, 0, SEEK_CUR) = -1 ESPIPE (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,

Does anyone else get these? A Errno::ECONNRESET occurred in facebook#index: Connection reset by peer /usr/lib64/ruby/1.8/net/protocol.rb:133:in `sysread'' Today it was on a user.populate call... I am wondering if it makes sense to catch and retry for this exception. Dave -------------- next part -------------- An HTML attachment was scrubbed... URL:

On 8/31/23 00:21, Eric Blake wrote: > 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. >

On Thu, Aug 31, 2023 at 10:40:53AM +0200, Laszlo Ersek wrote: > On 8/31/23 00:21, Eric Blake wrote: > > 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

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

By default, Mongrel will delete the HTTP request body and short circuit calling any handlers if a request is interrupted or incomplete. Unfortunately, this breaks any attempt to correctly handle a partial PUT. (BTW, PUT is *way* more efficient for uploads compared to POST which requires a MIME parsing step.) So, about a month ago I wrote up some patches to Mongrel 0.3.18 that allowed

On the Mongrel FAQ forum, Josh Wehner was having problems with cygwin (don''t know if he fixed it). http://rubyforge.org/forum/forum.php?thread_id=6978&forum_id=5450 Due that, I manage to install cygwin, ruby and rails on my humble little computer, it compiled worked ok (taste like *nix, so I felt a bit off-road running this). Anyway, tried to pass test for mongrel, and still get 1

On Thu, Dec 16, 2010 at 2:43 PM, <tms3 at tms3.com> wrote: > > On Thursday 16/12/2010 at 2:33 pm, Liam wrote: > > On Thu, Dec 16, 2010 at 1:52 PM, <tms3 at tms3.com> wrote: > >> On Thursday 16/12/2010 at 1:36 pm, Liam wrote: >> >> ... >> >> And when an smb connection is active but the client is idle, does the >> client >> expect