Re: [OMPI users] Problem with sending messages from one of the machines

2010-11-11 Thread Jeff Squyres
On Nov 11, 2010, at 3:23 PM, Krzysztof Zarzycki wrote: > No, unfortunately specification of interfaces is a little more complicated... > eth0/1/2 is not common for both machines. Can you define "common"? Do you mean that eth0 on one machine is on a different network then eth0 on the other mac

Re: [OMPI users] Problem with sending messages from one of the machines

2010-11-11 Thread Krzysztof Zarzycki
No, unfortunately specification of interfaces is a little more complicated... eth0/1/2 is not common for both machines. I've tried to play with (oob/btl)_tcp_ if_include, but actually... I don't know exactly how. Anyway, do you have any ideas how to further debug the communication problem? Chee

Re: [OMPI users] Problem with sending messages from one of the machines

2010-11-11 Thread Ralph Castain
There are two connections to be specified: -mca oob_tcp_if_include xxx -mca btl_tcp_if_include xxx On Nov 11, 2010, at 12:04 PM, Krzysztof Zarzycki wrote: > Hi, > I'm working with Grzegorz on the mentioned problem. > If I'm correct on checking the firewall settings, "iptables --list" shows an

Re: [OMPI users] Problem with sending messages from one of the machines

2010-11-11 Thread Jeff Squyres
On Nov 11, 2010, at 2:04 PM, Krzysztof Zarzycki wrote: > I'm working with Grzegorz on the mentioned problem. > If I'm correct on checking the firewall settings, "iptables --list" shows an > empty list of rules. > The second host does not have iptables installed at all. > > So what can be a next

Re: [OMPI users] Problem with sending messages from one of the machines

2010-11-11 Thread Krzysztof Zarzycki
Hi, I'm working with Grzegorz on the mentioned problem. If I'm correct on checking the firewall settings, "iptables --list" shows an empty list of rules. The second host does not have iptables installed at all. So what can be a next reason of this problem? By the way, how can I enforce mpirun to

Re: [OMPI users] Problem with sending messages from one of the machines

2010-11-11 Thread Jeff Squyres
I'd check the firewall settings. The stack trace indicates that the one host is trying to connect to the other (Open MPI initiates non-blocking TCP connections that can be polled on later). On Nov 10, 2010, at 12:46 PM, David Zhang wrote: > Have you double checked your firewall settings, TCP/

Re: [OMPI users] memcpy overlap in ompi_ddt_copy_content_same_ddt and glibc 2.12

2010-11-11 Thread Jed Brown
On Thu, Nov 11, 2010 at 12:36, Number Cruncher wrote: > However as commented here: > https://bugzilla.redhat.com/show_bug.cgi?id=638477#c86 the valgrind memcpy > implementation is overlap-safe. > Yes, of course. That's how the bug in Open MPI was originally detected. Of course you can't do pr

Re: [OMPI users] memcpy overlap in ompi_ddt_copy_content_same_ddt and glibc 2.12

2010-11-11 Thread Number Cruncher
On 11/11/10 10:56, Jed Brown wrote: On Thu, Nov 11, 2010 at 11:45, Number Cruncher mailto:number.crunc...@ntlworld.com>> wrote: Having just replaced the memcpy with Linus safe forward-copy version from https://bugzilla.redhat.com/show_bug.cgi?id=638477#c38 I can report no more

Re: [OMPI users] memcpy overlap in ompi_ddt_copy_content_same_ddt and glibc 2.12

2010-11-11 Thread Number Cruncher
On 10/11/10 21:17, Jed Brown wrote: I think any software that ignores the ISO warning "If copying takes place between objects that overlap, the behavior is undefined" needs fixing. Absolutely, it is incorrect and should be fixed. Having just replaced the memcpy with Linus safe

Re: [OMPI users] EXTERNAL: Re: Creating 64-bit objects?

2010-11-11 Thread Nysal Jan
I believe the libtool version (<2.2.8) used to make the 1.4.3 and 1.5 tarball does not have this fix. I have opened a ticket to get this fixed - https://svn.open-mpi.org/trac/ompi/ticket/2626 --Nysal On Wed, Nov 10, 2010 at 7:08 PM, Price, Brian M (N-KCI) < brian.m.pr...@lmco.com> wrote: > Than

Re: [OMPI users] Creating 64-bit objects?

2010-11-11 Thread Nysal Jan
Jeff, Yes the issue was reported to exist on both 1.4.3 and 1.5. I have created a ticket to get this fixed - https://svn.open-mpi.org/trac/ompi/ticket/2626 We can patch libtool locally as you suggested. --Nysal On Wed, Nov 10, 2010 at 7:21 PM, Jeff Squyres wrote: > Nysal -- > > Does the same is