Phil and Kevin, That update to sockio.c did the trick. The errors didn't always happen, but it was consistent enough that I would probably have seen it again by now if that weren't the solution.
Thanks! Elaine -----Original Message----- From: Phil Carns [mailto:[email protected]] On Behalf Of Phil Carns Sent: Friday, April 03, 2009 11:24 AM To: Kevin Harms Cc: Elaine Quarles; [email protected] Subject: Re: [Pvfs2-developers] Is there a patch for flow proto errors? I agree with Kevin. That brecv problem is probably the root problem that led to the flow protocol errors. I can't find that particular error message in 2.7.1 or trunk though, though. I know it used to be in there but was updated at some point. If this is a reproducable problem, you may be able to simply take src/io/bmi/bmi_tcp/sockio.c from trunk and drop it in place in your code to see if that fixes it. There have been some updates here and there regarding how it handles blocking and nonblocking calls, but I believe it is API compatible with 2.7.1. -Phil Kevin Harms wrote: > Elaine, > > I think this error means that some code is trying to perform a > blocking read on non-blocking socket and there is no data present. You > are running 2.7.1? > > kevin > > On Mar 30, 2009, at 2:28 PM, Elaine Quarles wrote: > >> It is occurring on both the client and server sides. The server side >> has an >> additional message: >> >> [E 03/30 15:18] Error: BMI_sockio_brecv: Resource temporarily unavailable >> [E 03/30 15:18] handle_io_error: flow proto error cleanup started on >> 0x487d8f0, error_code: -1073741959 >> [E 03/30 15:18] handle_io_error: flow proto 0x487d8f0 canceled 1 >> operations, >> will clean up. >> [E 03/30 15:18] handle_io_error: flow proto 0x487d8f0 error cleanup >> finished, error_code: -1073741959 >> >> - Elaine >> >> -----Original Message----- >> From: Phil Carns [mailto:[email protected]] On Behalf Of Phil Carns >> Sent: Monday, March 30, 2009 3:15 PM >> To: Elaine Quarles >> Cc: [email protected] >> Subject: Re: [Pvfs2-developers] Is there a patch for flow proto errors? >> >> Hi Elaine, >> >> That error code corresponds to a broken pipe error from TCP, so it is >> probably a side effect of something else going wrong (for example, >> possibly a server or client crashing, or a peer hitting some other error >> and closing the socket unexpectedly). >> >> Are you seeing this on the server side or the client side? >> >> -Phil >> >> Elaine Quarles wrote: >>> I am getting the following errors while working with PVFS 2.7.1 code. I >>> have found a couple of old threads from the mailing list that report >>> these same errors but I can't find the solution. Can anyone point me to >>> a patch that fixes it? >>> >>> >>> >>> [E 11:58:31.476712] handle_io_error: flow proto error cleanup started on >>> 0xd6a2c98, error_code: -1073741973 >>> >>> [E 11:58:31.476884] handle_io_error: flow proto 0xd6a2c98 canceled 0 >>> operations, will clean up. >>> >>> [E 11:58:31.476893] handle_io_error: flow proto 0xd6a2c98 error cleanup >>> finished, error_code: -1073741973 >>> >>> >>> >>> Thanks, >>> >>> Elaine Quarles >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> Pvfs2-developers mailing list >>> [email protected] >>> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers >> >> _______________________________________________ >> Pvfs2-developers mailing list >> [email protected] >> http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers > _______________________________________________ Pvfs2-developers mailing list [email protected] http://www.beowulf-underground.org/mailman/listinfo/pvfs2-developers
