Or you can follow the advice in this faq: http://www.open-mpi.org/faq/?category=tcp#tcp-connection-errors
and run: perl -e 'die$!=131' Tim On Sunday 18 November 2007 09:29:25 pm George Bosilca wrote: > There is a good reason for this. The errno is system dependent. As an > example on my Debian cluster errno 131 means "ENOTRECOVERABLE". > Usually, this value is used with mutexes and not with writev. > If you want to know what the 131 means on your specific system, take a > look in /usr/include/errno.h. > > george. > > On Nov 18, 2007, at 8:59 AM, Lydia Heck wrote: > > One of our programs has got stuck - it has not terminated - > > with the error messages: > > mca_btl_tcp_frag_send: writev failed with errno=131. > > > > Searching the openmpi web site did not result in a positive hit. > > What does it mean? > > > > I am running 1.2.1r14096 > > > > Lydia > > > > > > ------------------------------------------ > > Dr E L Heck > > > > University of Durham > > Institute for Computational Cosmology > > Ogden Centre > > Department of Physics > > South Road > > > > DURHAM, DH1 3LE > > United Kingdom > > > > e-mail: lydia.h...@durham.ac.uk > > > > Tel.: + 44 191 - 334 3628 > > Fax.: + 44 191 - 334 3645 > > ___________________________________________ > > _______________________________________________ > > users mailing list > > us...@open-mpi.org > > http://www.open-mpi.org/mailman/listinfo.cgi/users