none
SMPD not found!

    Pertanyaan

  • I want to assign pi calculation from head to WIN-MGPROO1QCSP:8677.

    But HPC show this message to me:

    Aborting: smpd on WIN-09EFU0M66NK is unable to connect to the smpd service on WIN-MGPROO1QCSP:8677
    Other MPI error, error stack:
    connect failed - The parameter is incorrect.  (errno -2147024809)

    Kamis, 07 April 2016 01.14

Semua Balasan

  • Update: I had identify all of the setup was installed by same version HPC pack, msmpi, msmpi debugger.

    ps. I want to run pi.exe over two nodes through Job manager.

    The first host is Head node, second is compute node.

    This is my command:

    mpi /hosts 2 WIN-09EFUOM66NK 1 WIN-MGPROO1QCSP 1 pi.exe

    Kamis, 07 April 2016 01.43
  • First, have you enabled PI.exe in the firewall allowed list? if not, try run below on all nodes (From the admin console, select all the nodes, run a command):

               HpcFwUtil register myPiApp <path>\pi.exe

    Then if you launch the MPI job from job manager, try this command

              mpiexec <path>\pi.exe

    while set the job Resource type to be Node, and your task resource 2.


    Qiufang Shi

    Kamis, 07 April 2016 02.39
  • I had closed all firewall setting.

    I had tried only pi.exe on my compute node, but it show this error:

    ERROR: Failed RpcCliStartMgr error -2147024809

    Aborting: mpiexec on WIN-09EFU0M66NK is unable to connect to the smpd service on WIN-MGPROO1QCSP:8677
    Other MPI error, error stack:
    connect failed - The parameter is incorrect.  (errno -2147024809)

    Then, I go my compute node check smpd -d. I realize smpd unable to debug.

    I'm sure all msmpi related file installed properly. I don't know why...

    Kamis, 07 April 2016 04.06
  • Can you try to run the MPI ping-pong diagnostics test through the admin console to check whether your system is well configured? 

    Qiufang Shi

    Kamis, 07 April 2016 09.07
  • I got this result in PingPong Latency test.

    • This node did not return diagnostics results. Possible reasons are: there was a network issue, or the files that are required for running the diagnostic test are not available on the node. If this is a custom diagnostic test that you added to the cluster, you need to verify that you have copied to all the nodes the files that are required for running the diagnostic test, especially to any new nodes that have joined the cluster. 

    • Diedit oleh Yu Jie Ang Kamis, 07 April 2016 10.48
    Kamis, 07 April 2016 10.45
  • It looks like a network configuration issue. I suppose you have more than one network available. Thus please provide me more information about:

    1. What your network topology looks like for all the machines. And what topology you configured in the To-do list?

    2. What's you MPI network mask have you configured

    3. Please also run the DNS test and Ping Test

    And share the results with us.


    Qiufang Shi

    Jumat, 08 April 2016 01.27