none
Aborting: mpiexec on %HOSTNAME% is unable to connect to the msmpi service on 1:86 RRS feed

  • Question

  • Hi,

    I got three Windows Server 2008 R2 in a vmware vsx server to install a HPC cluster.

    I installed Microsoft HPC Pack 2008 R2 on this machines and configured a cluster.

    One machine is head node, broker node, work node and containes the sql server.

    The other machines are work nodes.

    I made dns, domain, network configuration and mpi ping pong test. All tests completed succesfully.

    As next I tried:

    C:\Users\oks>mpiexec.exe -host 1 localhost hostname

    Aborting: mpiexec on %HOSTNAME% is unable to connect to the msmpi service on 1:86
    77
    Other MPI error, error stack:
    ConnectFailed(961): unable to connect to 1 on port 8677, exhausted all endpoints

    ConnectFailed(952): unable to connect to 1 on port 8677, A socket operation was
    attempted to an unreachable network.  (errno 10051)

    C:\Users\oks>

    C:\Users\oks>route print
    ===========================================================================
    Interface List
     11...00 50 56 ba 00 82 ......Intel(R) PRO/1000 MT Network Connection
      1...........................Software Loopback Interface 1
     12...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter
     13...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
    ===========================================================================

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0     172.21.16.23    172.21.16.201    266
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    306
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    306
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    306
          172.21.16.0    255.255.252.0         On-link     172.21.16.201    266
        172.21.16.201  255.255.255.255         On-link     172.21.16.201    266
        172.21.19.255  255.255.255.255         On-link     172.21.16.201    266
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    306
            224.0.0.0        240.0.0.0         On-link     172.21.16.201    266
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    306
      255.255.255.255  255.255.255.255         On-link     172.21.16.201    266
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0     172.21.16.23  Default
    ===========================================================================

    IPv6 Route Table
    ===========================================================================
    Active Routes:
     If Metric Network Destination      Gateway
      1    306 ::1/128                  On-link
     11    266 fe80::/64                On-link
     11    266 fe80::30a3:a20d:dfed:a1bd/128
                                        On-link
      1    306 ff00::/8                 On-link
     11    266 ff00::/8                 On-link
    ===========================================================================
    Persistent Routes:
      None

    C:\Users\oks>ipconfig /all

    ...

    ...

    ...

    Ethernet adapter Enterprise:

    Connection-specific DNS Suffix . :

    Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connection

    Physical Address. . . . . . . . . : 00-50-56-BA-00-82

    DHCP Enabled. . . . . . . . . . . : No

    Autoconfiguration Enabled . . . . : Yes

    Link-local IPv6 Address . . . . . : fe80::30a3:a20d:dfed:a1bd%11(Preferred)

    IPv4 Address. . . . . . . . . . . : 172.21.16.201(Preferred)

    Subnet Mask . . . . . . . . . . . : 255.255.252.0

    Default Gateway . . . . . . . . . : 172.21.16.23

    DHCPv6 IAID . . . . . . . . . . . : 234901590

    DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-16-FC-9D-37-00-50-56-BA-00-81

    DNS Servers . . . . . . . . . . . : 172.21.16.2

    172.21.16.4

    NetBIOS over Tcpip. . . . . . . . : Disabled

    I got the same error, if I use the hostname instead localhost.

    Firewall is enabled for domain network. msmpisvc.exe is enable in firewall rules for domain network.

    oks is member of the local admin group.

    Where is problem?

    Does anyone have an idea?

    Regards

    Manfred

    Monday, April 23, 2012 2:06 PM

All replies

  • Hi,

    If you simply wants a diagnostic, you can try the diagnostics from the Cluster Manager. Doing "-host 1" is not a valid input for mpiexec (do you happen to have a host has name 1?)

    Thanks.

    Michael

    Monday, April 30, 2012 4:48 PM
  • It seemed your command is wrong. You should use -hosts instead of -host

    Try with:

    mpiexec.exe -hosts 1 localhost hostname

    For more information about mpiexec.exe, run mpiexec -?

    It will tell you:

    -hosts n host1 [m1] host2 [m2] ... hostn [mn]

    Friday, May 11, 2012 9:40 PM