[Pvfs2-users] "Remote Endpoint is Closed" error
atchley at myri.com
Wed Aug 25 13:21:24 EDT 2010
On Aug 25, 2010, at 11:38 AM, Scott Atchley wrote:
> On Aug 25, 2010, at 11:02 AM, Joshua Randall wrote:
>>> Can you try repeating your experiment with the OMX_FATAL_ERRORS environment variable set to 0?
>> With OMX_FATAL_ERRORS=0 and MX_IMM_ACK=1, the servers now start and connect to each other. Perhaps someone should add the need for OMX_FATAL_ERRORS=0 to the FAQ entry that discusses MX_IMM_ACK (or perhaps it can be set programmatically via the API?). In any case, thanks for the help in getting the servers started!
> I will forward this to the Open-MX developers and ask that they look into why Open-MX is not accepting the MX error handler setting.
The Open-MX developers have fixed this and it will be in the next release.
In bmi_mx, I change the default MX error handler from MX_ERRORS_ARE_FATAL to MX_ERRORS_RETURN before calling mx_init() (in case mx_init() fails). In Open-MX, they only implemented the error handler change if it happened after mx_init().
More information about the Pvfs2-users