Hmmm...well, that's an interesting naming scheme :-) Try adding "-mca oob_base_verbose 10 --report-uri -" on your cmd line and let's see what it thinks is happening
On May 14, 2014, at 9:06 AM, Siegmar Gross <siegmar.gr...@informatik.hs-fulda.de> wrote: > Hi Ralph, > >> What are the interfaces on these machines? > > tyr fd1026 111 ifconfig -a > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 > index 1 > inet 127.0.0.1 netmask ff000000 > bge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 > inet 193.174.24.39 netmask ffffffe0 broadcast 193.174.24.63 > tyr fd1026 112 > > > tyr fd1026 112 ssh sunpc1 ifconfig -a > lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 > index 1 > inet 127.0.0.1 netmask ff000000 > nge0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 > inet 193.174.26.210 netmask ffffffc0 broadcast 193.174.26.255 > tyr fd1026 113 > > > tyr fd1026 113 ssh linpc1 /sbin/ifconfig -a > eth0 Link encap:Ethernet HWaddr 00:14:4F:23:FD:A8 > inet addr:193.174.26.208 Bcast:193.174.26.255 Mask:255.255.255.192 > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:18052524 errors:127 dropped:0 overruns:0 frame:127 > TX packets:15917888 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:4158294157 (3965.6 Mb) TX bytes:12060556809 (11501.8 Mb) > Interrupt:23 Base address:0x4000 > > eth1 Link encap:Ethernet HWaddr 00:14:4F:23:FD:A9 > BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > Interrupt:45 Base address:0xa000 > > lo Link encap:Local Loopback > inet addr:127.0.0.1 Mask:255.0.0.0 > UP LOOPBACK RUNNING MTU:16436 Metric:1 > RX packets:1083 errors:0 dropped:0 overruns:0 frame:0 > TX packets:1083 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:0 > RX bytes:329323 (321.6 Kb) TX bytes:329323 (321.6 Kb) > > tyr fd1026 114 > > > Do you need something else? > > > Kind regards > > Siegmar > > > > >> On May 14, 2014, at 7:45 AM, Siegmar Gross >> <siegmar.gr...@informatik.hs-fulda.de> wrote: >> >>> Hi, >>> >>> I just installed openmpi-1.8.2a1r31742 on my machines (Solaris 10 >>> Sparc, Solaris 10 x86_64, and openSUSE Linux 12.1 x86_64) with >>> Sun C5.12 and still have the following problem. >>> >>> tyr fd1026 102 which mpiexec >>> /usr/local/openmpi-1.8.2_64_cc/bin/mpiexec >>> tyr fd1026 103 mpiexec -np 3 --host tyr,sunpc1,linpc1 hostname >>> [tyr.informatik.hs-fulda.de:12827] [[37949,0],0] CONNECTION >>> REQUEST ON UNKNOWN INTERFACE >>> [tyr.informatik.hs-fulda.de:12827] [[37949,0],0] CONNECTION >>> REQUEST ON UNKNOWN INTERFACE >>> ^CKilled by signal 2. >>> Killed by signal 2. >>> tyr fd1026 104 >>> >>> >>> The command works fine with openmpi-1.6.6rc1. >>> >>> tyr fd1026 102 which mpiexec >>> /usr/local/openmpi-1.6.6_64_cc/bin/mpiexec >>> tyr fd1026 103 mpiexec -np 3 --host tyr,sunpc1,linpc1 hostname >>> tyr.informatik.hs-fulda.de >>> linpc1 >>> sunpc1 >>> tyr fd1026 104 >>> >>> >>> I have reported the problem before and I would be grateful, if >>> somebody could solve it. Please let me know if I can provide any >>> other information. >>> >>> >>> Kind regards >>> >>> Siegmar >>> >>> _______________________________________________ >>> users mailing list >>> us...@open-mpi.org >>> http://www.open-mpi.org/mailman/listinfo.cgi/users >> >> > > _______________________________________________ > users mailing list > us...@open-mpi.org > http://www.open-mpi.org/mailman/listinfo.cgi/users
