[mpich-discuss] MPICH 2 on Window 7 home premium
Koh Voon Li
kohvoonli at gmail.com
Sun Feb 13 20:48:08 CST 2011
Hi,
Thanks Jayesh, it seem work for me now. Here is the message I got by running
a simple command.
C:\>mpiexec -hosts 2 WIN7-PC 3 user-PC 3 c:\program files
\fds\fds5\bin\fds5_mpi_win_64.exe
Process 2 of 5 is running on WIN7-PC
Process 1 of 5 is running on WIN7-PC
Process 5 of 5 is running on user-PC
Process 0 of 5 is running on WIN7-PC
Process 4 of 5 is running on user-PC
Process 3 of 5 is running on user-PC
Fire Dynamics Simulator
Version: 5.5.3; MPI Enabled; OpenMP Disabled
SVN Revision Number: 7031
Compile Date: Fri, 29 Oct 2010
Consult FDS Users Guide Chapter, Running FDS, for further instructions.
Hit Enter to Escape...
job aborted:
rank: node: exit code[: error message]
0: WIN7-PC: 123
1: WIN7-PC: 0: process 1 exited without calling finalize
2: WIN7-PC: 0: process 2 exited without calling finalize
3: user-PC: 0: process 3 exited without calling finalize
4: user-PC: 0: process 4 exited without calling finalize
5: user-PC: 0: process 5 exited without calling finalize
But when I tried to run a job, I got error message as below:
D:\>mpiexec -hosts 2 WIN7-PC 3 user-PC 3 "c:\program
files\fds\fds5\bin\fds5_mpi
_win_64.exe" "\\WIN7-PC\Project\Paradigm\FDS\V16\paradigmv4-16.fds"
Process 5 of 5 is running on user-PC
Process 0 of 5 is running on WIN7-PC
Process 1 of 5 is running on WIN7-PC
Process 2 of 5 is running on WIN7-PC
Process 3 of 5 is running on user-PC
Process 4 of 5 is running on user-PC
Mesh 1 is assigned to Process 0
Mesh 2 is assigned to Process 1
Mesh 3 is assigned to Process 2
Mesh 4 is assigned to Process 3
Mesh 5 is assigned to Process 3
Mesh 6 is assigned to Process 4
Mesh 7 is assigned to Process 5
forrtl: severe (29): file not found, unit 4, file
C:\Windows\system32\Paradigmv4
-16.smv
Image PC Routine Line Source
fds5_mpi_win_64.e 0000000140589BE8 Unknown Unknown Unknown
fds5_mpi_win_64.e 0000000140584CC9 Unknown Unknown Unknown
fds5_mpi_win_64.e 000000014053CA3D Unknown Unknown Unknown
fds5_mpi_win_64.e 000000014051AE17 Unknown Unknown Unknown
fds5_mpi_win_64.e 000000014051A6E1 Unknown Unknown Unknown
fds5_mpi_win_64.e 00000001404EB76F Unknown Unknown Unknown
fds5_mpi_win_64.e 00000001402FFF2D Unknown Unknown Unknown
fds5_mpi_win_64.e 00000001404A8E58 Unknown Unknown Unknown
fds5_mpi_win_64.e 000000014059338C Unknown Unknown Unknown
fds5_mpi_win_64.e 000000014056C055 Unknown Unknown Unknown
kernel32.dll 000000007725F56D Unknown Unknown Unknown
ntdll.dll 0000000077392CC1 Unknown Unknown Unknown
Fatal error in PMPI_Barrier: Other MPI error, error stack:
PMPI_Barrier(476).........................: MPI_Barrier(MPI_COMM_WORLD)
failed
MPIR_Barrier(82)..........................:
MPIC_Sendrecv(164)........................:
MPIC_Wait(513)............................:
MPIDI_CH3i_Progress_wait(215).............: an error occurred while handling
an
event returned by MPIDU_Sock_Wait()
MPIDI_CH3I_Progress_handle_sock_event(420):
MPIDU_Sock_wait(2606).....................: The specified network name is no
lon
ger available. (errno 64)
Fatal error in PMPI_Barrier: Other MPI error, error stack:
PMPI_Barrier(476).........................: MPI_Barrier(MPI_COMM_WORLD)
failed
MPIR_Barrier(82)..........................:
MPIC_Sendrecv(164)........................:
MPIC_Wait(513)............................:
MPIDI_CH3i_Progress_wait(215).............: an error occurred while handling
an
event returned by MPIDU_Sock_Wait()
MPIDI_CH3I_Progress_handle_sock_event(420):
MPIDU_Sock_wait(2606).....................: The specified network name is no
lon
ger available. (errno 64)
job aborted:
rank: node: exit code[: error message]
0: WIN7-PC: 123
1: WIN7-PC: 123
2: WIN7-PC: 123
3: user-PC: 29: process 3 exited without calling finalize
4: user-PC: 123: Fatal error in PMPI_Barrier: Other MPI error, error stack:
PMPI_Barrier(476).........................: MPI_Barrier(MPI_COMM_WORLD)
failed
MPIR_Barrier(82)..........................:
MPIC_Sendrecv(164)........................:
MPIC_Wait(513)............................:
MPIDI_CH3i_Progress_wait(215).............: an error occurred while handling
an
event returned by MPIDU_Sock_Wait()
MPIDI_CH3I_Progress_handle_sock_event(420):
MPIDU_Sock_wait(2606).....................: The specified network name is no
lon
ger available. (errno 64)
5: user-PC: 123: Fatal error in PMPI_Barrier: Other MPI error, error stack:
PMPI_Barrier(476).........................: MPI_Barrier(MPI_COMM_WORLD)
failed
MPIR_Barrier(82)..........................:
MPIC_Sendrecv(164)........................:
MPIC_Wait(513)............................:
MPIDI_CH3i_Progress_wait(215).............: an error occurred while handling
an
event returned by MPIDU_Sock_Wait()
MPIDI_CH3I_Progress_handle_sock_event(420):
MPIDU_Sock_wait(2606).....................: The specified network name is no
lon
ger available. (errno 64)
Is it something has to do with my working directory? As I noticed 1 of the
error message I got as highlighted in yellow above said file not found on my
Window directory.
Thanks.
Regards,
Koh
On Sat, Feb 12, 2011 at 10:48 PM, Jayesh Krishna <jayesh at mcs.anl.gov> wrote:
> Hi,
> Yes, you need to have the same username/password on both the machines (Or
> use a domain user).
> Let us know if it works.
>
> Regards,
> Jayesh
>
> ----- Original Message -----
> From: "Koh Voon Li" <kohvoonli at gmail.com>
> To: "Jayesh Krishna" <jayesh at mcs.anl.gov>
> Cc: mpich-discuss at mcs.anl.gov
> Sent: Friday, February 11, 2011 7:00:17 PM
> Subject: Re: MPICH 2 on Window 7 home premium
>
> Hi,
>
> Thanks for the replies. The Windows username and password are different
> between two machine. Do I need to create the same username & password
> between them so that I able to get access between it?
> Thanks.
>
> Regards,
> Koh
>
>
> On Fri, Feb 11, 2011 at 9:26 PM, Jayesh Krishna < jayesh at mcs.anl.gov >
> wrote:
>
>
> Hi,
> Do you have the same Windows username/password on both the machines ?
>
>
> Regards,
> Jayesh
>
> ----- Original Message -----
> From: "Koh Voon Li" < kohvoonli at gmail.com >
> To: "Jayesh Krishna" < jayesh at mcs.anl.gov >
>
>
>
> Cc: mpich-discuss at mcs.anl.gov
> Sent: Thursday, February 10, 2011 7:59:38 PM
> Subject: Re: MPICH 2 on Window 7 home premium
>
> Yes. I able registered on both machine. But when I tried to just launch
> simply command I got error message as stated below:
>
>
>
> C:\>mpiexec -hosts 2 WIN7-PC 1 user-PC 1 "c:\program
> files\fds\fds5\bin\fds5_mpi
> _win_64.exe"
> abort: Unable to connect to user-PC
>
>
> For your information, I have turned off both Window firewall. But still
> failed to launch any job.
>
>
> On Thu, Feb 10, 2011 at 11:52 PM, Jayesh Krishna < jayesh at mcs.anl.gov >
> wrote:
>
>
> Hi,
> Is the username/password valid on the second machine (Do you have the same
> Windows username/password on the second machine ? )? If so, you should be
> able to run your job. Are you able to run your job now ?
> Registration of username/password is local to the machine. MPICH2 does not
> automatically register the same username on all the nodes. If you would like
> to register username/password on each machine you should register the
> credentials on each (Type "mpiexec -register" on each). However, to launch
> your job you need to have the username/password registered only on the
> machine/node where you launch your job.
>
> Let us know the results.
>
> Regards,
> Jayesh
>
> ----- Original Message -----
> From: "Koh Voon Li" < kohvoonli at gmail.com >
>
>
>
> To: "Jayesh Krishna" < jayesh at mcs.anl.gov >
> Sent: Thursday, February 10, 2011 9:30:16 AM
> Subject: Re: MPICH 2 on Window 7 home premium
>
> Hi,
>
> Thanks for the reply. I was able to registered 2 username on 1 of my
> computer, but I got error message on my 2nd computer when I try to validate
> user on it.
>
> Here is the error message.
> FAIL: Unable to read the credentials from the registry.
>
> Thanks,
>
> Regards,
> KOH
>
>
>
> On Thu, Feb 10, 2011 at 10:10 PM, Jayesh Krishna < jayesh at mcs.anl.gov >
> wrote:
>
>
> Hi,
>
>
> >> Credentials for USER-PC\WIN 7 rejected connecting to user-PC
> >> Aborting: Unable to connect to user-PC
>
> From the error message it looks like you haven't registered a valid
> username/password with mpiexec. Please register a valid Windows
> username/password with mpiexec using the "-register" option (Type "mpiexec
> -register" at the command prompt and mpiexec will prompt you for the
> username/password). Once the registration is complete validate it using the
> "-validate" option (Type "mpiexec -validate" at the command prompt). If you
> have registered a valid Windows username/password the validate option should
> return SUCCESS.
> Let us know the results.
>
> Regards,
> Jayesh
>
>
> ----- Original Message -----
> From: "Koh Voon Li" < kohvoonli at gmail.com >
>
> To: jayesh at mcs.anl.gov
>
>
>
> Sent: Thursday, February 10, 2011 2:59:35 AM
> Subject: Fwd: MPICH 2 on Window 7 home premium
>
>
> Hi Jayesh,
>
> Sorry for bothering. Attached here is the smpd log in debug mode.
> Million Thanks.
>
>
> Regards,
> KOH
>
>
>
> ---------- Forwarded message ----------
> From: Koh Voon Li < kohvoonli at gmail.com >
> Date: Thu, Feb 10, 2011 at 3:30 PM
> Subject: MPICH 2 on Window 7 home premium
> To: jayesh at mcs.anl.gov
>
>
> Hi Jayesh,
>
>
> I am trying to running parallel FDS (Fire Dynamic Simulator) via 2 PC by
> using a config file
>
>
> here is my config file
>
> exe "C:\Program Files\FDS\FDS5\bin\fds5_mpi_win_64.exe" "ParadigmV4-13.fds"
> wdir "\\USER-PC\Project\Paradigm\"
> hosts
> user-PC 6
> WIN7-PC 6
>
>
> This is the error message I got from the command prompt.
>
> C:\>mpiexec -file config.txt
> Credentials for USER-PC\WIN 7 rejected connecting to user-PC
> Aborting: Unable to connect to user-PC
>
>
> I used a cross over cable to connect both PCs and I think my setting for
> the IP address is correct as I can ping each other computer in the command
> prompt.
> I tried to turned off both firewall but it failed.
> Thanks,
>
>
> Regards,
> Koh
>
>
>
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20110214/131120e9/attachment.htm>
More information about the mpich-discuss
mailing list