none
ERRORS WITH MS-MPIV7 RRS feed

  • Question

  • Sir, when i try to run in parallel this errors appears please help i am at an urgent stage in completing my uni assignment.

    Aborting: mpiexec on AS is unable to connect to the smpd manager on localhost:64167 error 1727
    ERROR: Failed to connect to SMPD Manager Instance error 1727

    Sunday, October 9, 2016 3:24 PM

All replies

  • Hi,

    A couple questions:

    1) Which version of MS-MPI are you running?

    2) How did you invoke mpiexec?

    Anh

    Monday, October 10, 2016 3:29 AM
  • 1) version ms-mpi (7.0.12437.6)

    2)$ mpiexec.exe -n 4 simpleFoam.exe -parallel (this command is invoke from a cygin terminal coupled to run a cfd software called openFoam

    Monday, October 10, 2016 3:35 AM
  • Can you try the latest version of MS-MPI (v7.1) and let us know if this fixes the issue

    https://www.microsoft.com/en-us/download/details.aspx?id=52981

    Anh

    Monday, October 10, 2016 3:10 PM
  • Sir, it's still the same i dunno why please help!!!!
    Tuesday, October 11, 2016 1:30 PM
  • when i do testing on the window cmd with the command line:mpiexec -n 1 -host machine1 test : -n 1 -host machine2 test

    The following errors appear:

    ERROR: Failed RpcCliCreateContext error 1722

    Aborting: mpiexec on AS is unable to connect to the smpd service on machine1:8677
    Other MPI error, error stack:
    connect failed - The RPC server is unavailable.  (errno 1722)

    Notes: i've tired turning off my kapersky anti virus and window firewall but still to no avail........please help anyone

    Tuesday, October 11, 2016 2:41 PM
  • Did you start the smpd daemon on each of the hosts (i.e., machine1 and machine2) by  running smpd -d? Also, is there any VPN running?
    Tuesday, October 11, 2016 3:15 PM
  • can u describe the command line in detail as i'm not used to those commands, as for vpn i dont know cuz i dont have an vpn  software installed but in the vpn settings i set both the connection over metered network and connection while roaming to "on" status.

    Tuesday, October 11, 2016 3:34 PM
  • You should open a separate cmd console on each host and run smpd -d before running mpiexec. This will start the smpd daemon.
    Tuesday, October 11, 2016 3:38 PM
  • u mean in each cmd console i should execute smpd first and then followed by execution of mpiexec machine 1, 2.... alternatively....i followed ur advice but when executing smpd -d it shows nothing and just hangs with no indication of error....why?

    Tuesday, October 11, 2016 3:47 PM
  • any advice please i'm basically at the end of y wits here having tried all sorts of solution online.....
    Tuesday, October 11, 2016 3:51 PM
  • you should open another cmd console and execute smpd -d on that console and leave it running and run mpiexec on another console. smpd -d might appear like it's hanging because it doesn't have any output. If you want to see output you can run "smpd -d 3" instead
    Tuesday, October 11, 2016 3:51 PM
  • u mean run smpd -d on one console let it hangs and then run mpiexec -n 1 -host machine1 test : -n 1 -host machine2 test on another console? is that what u meant?

    Tuesday, October 11, 2016 3:56 PM
  • when i enter the command smpd -d 3 the following errors appears:

    [-1:16356] Launching SMPD service.
    [-1:16356] ERROR: smpd service failed to start rpc server, error: 1740
    [-1:16356] ERROR: state machine failed with error 0x800704D9.

    Tuesday, October 11, 2016 3:59 PM
  • The error (1740) indicated you already have another instance of smpd daemon running, or some other service running on the same port (port 8677). Are you running another smpd -d on the same machine, or running the msmpi launch service? You should only have one smpd service (either the smpd -d or msmpi launch service) running at anytime
    Tuesday, October 11, 2016 4:06 PM
  • ok i get it but when i run smpd -d on 1 cmd console and then the command line mpiexec -n 1 -host machine1 test : -n 1 -host machine2 test on another console it still outputs the ERROR: Failed RpcCliCreateContext error 1722

    Aborting: mpiexec on AS is unable to connect to the smpd service on machine1:8677
    Other MPI error, error stack:
    connect failed - The RPC server is unavailable.  (errno 1722)
    Tuesday, October 11, 2016 4:11 PM
  • can you try with just one machine for now:

    1) Run smpd -d 3 on one command console

    2) On the same machine using another command console, run "mpiexec -host localhost -n 1 hostname"

    Tuesday, October 11, 2016 4:29 PM
  • i did what u instructed:

    1)In one command console i entered smpd -d 3

    output message: 

    [-1:13680] Launching SMPD service.
    [-1:13680] smpd listening on port 8677

    then hangs with no indication of errors message

    2)On the sama machine using another command console i entered: mpiexec -host localhost -n 1 host machine1

    Hangs with no indication of output message or errors message.

    Wednesday, October 12, 2016 3:49 AM
  • Any advice or steps sir should i take?
    Wednesday, October 12, 2016 3:52 AM
  • after sometime waiting for the output message for the command:mpiexec -host localhost -n 1 host machine1

    the following error message appears

    Other MPI error, error stack:
    connect failed - The remote procedure call failed and did not execute.  (errno 1727)

    Wednesday, October 12, 2016 4:15 AM
  • the full errors message on step 2 was:

    ERROR: Failed RpcCliCreateContext error 1727

    Aborting: mpiexec on AS is unable to connect to the smpd service on localhost:8677
    Other MPI error, error stack:
    connect failed - The remote procedure call failed and did not execute.  (errno 1727)

    Wednesday, October 12, 2016 4:45 AM
  • Can you rerun the experiment as follows

    1) Open a cmd console and run "smpd -d 3"

    2) In another cmd console (same machine), run "mpiexec -d 3 -host localhost hostname"

    (Note that there's an application hostname within the windows\system32 directory already so please copy and paste the exact command to console)

    If the output is too long to paste here, please send the output to askmpi @ Microsoft.com

    Thanks

    Wednesday, October 12, 2016 4:50 AM
  • C:\Windows\System32\drivers\etc

    is this the hostname within the directory u meant? i mean the path to it?

    Wednesday, October 12, 2016 5:11 AM
  • You shouldn't need to worry about the path and can just execute the command as I have provided.

    Wednesday, October 12, 2016 5:15 AM
  • for the first step in 1)the output command is: 

    [-1:13680] Launching SMPD service.
    [-1:13680] smpd listening on port 8677

    for the second steps the output command is :

    [00:12056] host tree:
    [00:12056]  host: localhost, parent: 0, id: 1
    [00:12056] mpiexec started smpd manager listening on port 60253
    [00:12056] using spn msmpi/localhost to contact server

    Wednesday, October 12, 2016 5:21 AM
  • I think there is a problem with the network configuration, most likely firewall settings.

    1) Do you have any other third party firewall running on your machine?

    2) Can you provide the output of netsh advfirewall firewall show rule name="msmpi-smpd"?

    3) What is the version output when you run mpiexec -help (the first few lines will have the version information)?

    Thanks

    Wednesday, October 12, 2016 6:15 AM
  • 1)I only have window firewall and kapersky anti-virus installed and i tried turning them both off last night and still nothing

    2)the output message for step 2 is 

    Rule Name:                            MSMPI-SMPD
    ----------------------------------------------------------------------
    Enabled:                              Yes
    Direction:                            Out
    Profiles:                             Domain,Private,Public
    Grouping:
    LocalIP:                              Any
    RemoteIP:                             Any
    Protocol:                             Any
    Edge traversal:                       No
    Action:                               Allow

    Rule Name:                            MSMPI-SMPD
    ----------------------------------------------------------------------
    Enabled:                              Yes
    Direction:                            In
    Profiles:                             Domain,Private,Public
    Grouping:
    LocalIP:                              Any
    RemoteIP:                             Any
    Protocol:                             Any
    Edge traversal:                       No
    Action:                               Allow
    Ok.

    3) In step 3 the output message is :


        mpiexec [options] executable [args] [ : [options] exe [args] : ... ]
        mpiexec -configfile <file name>

    Common options:

    -n <num_processes>
    -env <env_var_name> <env_var_value>
    -wdir <working_directory>
    -hosts n host1 [m1] host2 [m2] ... hostn [mn]
    -cores <num_cores_per_host>
    -lines
    -debug [0-3]

    Examples:

        mpiexec -n 4 pi.exe
        mpiexec -hosts 1 server1 master : -n 8 worker

    For a complete list of options, run mpiexec -help2
    For a list of environment variables, run mpiexec -help3

    You can reach the Microsoft MPI team via email at askmpi@microsoft.com

     

       


    Wednesday, October 12, 2016 7:07 AM
  • any advice sir?

    Wednesday, October 12, 2016 8:03 AM
  • In the step 3) output, you're missing the version information, can you provide that information again? (The very first line of the output, it says "Microsoft MPI Startup Program [Version...."

    Do you have access to another machine in another environment that you could try the same experiment?

    Wednesday, October 12, 2016 2:59 PM
  • Microsoft MPI Startup Program [Version 7.1.12437.25]
    Wednesday, October 12, 2016 3:21 PM
  • Are you able to run "mpiexec -n 2 hostname" (without using -host option)?

    Can you look into the setting of Kasperky and see if you can add exclusion for the following? mpiexec.exe, smpd.exe, port 8677, ephemeral ports.

    Do you have access to another machine that you could try running your experiment? (Preferrably one without Kaspersky antivirus)?

    Thanks


    Wednesday, October 12, 2016 3:36 PM
  • i ran it on my cfd software and this output messsage appears : application aborted
    aborting MPI_COMM_WORLD (comm=0x44000000), error 1, comm rank 0

    [1] application aborted
    aborting MPI_COMM_WORLD (comm=0x44000000), error 1, comm rank 1

    [2] application aborted
    aborting MPI_COMM_WORLD (comm=0x44000000), error 1, comm rank 2

    [3] application aborted
    aborting MPI_COMM_WORLD (comm=0x44000000), error 1, comm rank 3
    Wednesday, October 12, 2016 5:28 PM
  • yes im able to run it and it outputs AS

                                                   AS


                           AS is my operating machine stands for asus                         
    Wednesday, October 12, 2016 5:38 PM
  • The application aborted error is a different error from the previous one that you experienced. The error you experienced was mpiexec unable to even start the process management infrastructure to launch the processes. The application aborted error happens after the processes have been launched already. I would suggest contacting the application support to understand why it aborted after being launched
    Wednesday, October 12, 2016 7:00 PM
  • when i run the mpiexec test command on the cmd console it is still the same i dunno why it still outputs the same errors as before.....even if i turn off window firewall and m antivirus it is still the same.....should i check on the window defender too?
    Thursday, October 13, 2016 12:38 PM
  • it still outputs the following errors:

    ERROR: Failed RpcCliCreateContext error 1722

    Aborting: mpiexec on AS is unable to connect to the smpd service on machine1:8677
    Other MPI error, error stack:
    connect failed - The RPC server is unavailable.  (errno 1722)

     
    Thursday, October 13, 2016 12:41 PM
  • Have you tried the experiment using another machine?
    Thursday, October 13, 2016 5:34 PM