<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7036.0">
<TITLE>RE: [mpich-discuss] mpiexec and working directory</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2> Hi,<BR>
When you install MPICH2 make sure that you install the latest stable version, 1.0.8. You could also ask your sysadmin to install MPICH2+smpd in another directory so that you can test MPICH2+smpd (1.0.8).<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: mpich-discuss-bounces@mcs.anl.gov [<A HREF="mailto:mpich-discuss-bounces@mcs.anl.gov">mailto:mpich-discuss-bounces@mcs.anl.gov</A>] On Behalf Of Tiago Silva<BR>
Sent: Friday, November 07, 2008 12:26 PM<BR>
To: mpich-discuss@mcs.anl.gov<BR>
Subject: Re: [mpich-discuss] mpiexec and working directory<BR>
<BR>
<BR>
So could that explain this behavior? I need to justify asking a very busy sysadmin to get the daemons on a 25 node cluster.<BR>
<BR>
Tiago<BR>
<BR>
Rajeev Thakur wrote:<BR>
> Oh, you are using SMPD. Can you try with the default MPD process manager?<BR>
> You have to build MPICH2 again for that.<BR>
><BR>
> Rajeev<BR>
><BR>
> <BR>
>> -----Original Message-----<BR>
>> From: mpich-discuss-bounces@mcs.anl.gov<BR>
>> [<A HREF="mailto:mpich-discuss-bounces@mcs.anl.gov">mailto:mpich-discuss-bounces@mcs.anl.gov</A>] On Behalf Of Tiago Silva<BR>
>> Sent: Friday, November 07, 2008 12:18 PM<BR>
>> To: mpich-discuss@mcs.anl.gov<BR>
>> Subject: Re: [mpich-discuss] mpiexec and working directory<BR>
>><BR>
>> Thanks Rajeev, this shows the problem nicely:<BR>
>><BR>
>> [tsilva@admin1 work]$ /n1ge6/mpich2/smpd/bin/mpiexec -nopm -ssh -l -n<BR>
>> 2 pwd /raid1/tsilva /raid1/tsilva<BR>
>> [tsilva@admin1 work]$ /n1ge6/mpich2/smpd/bin/mpiexec -nopm -ssh -l<BR>
>> -wdir /tmp/ -n 2 pwd /raid1/tsilva /raid1/tsilva<BR>
>> [tsilva@admin1 work]$ ls runjob.err<BR>
>> runjob.err<BR>
>> [tsilva@admin1 work]$ /n1ge6/mpich2/smpd/bin/mpiexec -nopm -ssh -l<BR>
>> -wdir /tmp/ -n 2 ls -l runjob.err<BR>
>> ls: runjob.err: No such file or directory<BR>
>> ls: runjob.err: No such file or directory<BR>
>><BR>
>> Could this have anything to do with running mpiexec deamonless<BR>
>> (although mpich was compiled with smpd)?<BR>
>> I noticed the same behavior with my regular setup of also deamonless<BR>
>> mpirun and mpich1. Only after calling mpi_init in the code did the<BR>
>> working dir change from being $home to the local dir.<BR>
>><BR>
>> Cheers,<BR>
>> Tiago<BR>
>><BR>
>> Rajeev Thakur wrote:<BR>
>> <BR>
>>> Can you try these simple commands:<BR>
>>><BR>
>>> mpiexec -l -n 2 pwd <BR>
>>> ## shows if you execute in the dir you think you are in<BR>
>>><BR>
>>> mpiexec -l -wdir /tmp -n 2 pwd <BR>
>>> ## similar to above but shows you moved to /tmp<BR>
>>><BR>
>>> mpiexec -l -n 2 ls -l some_filename <BR>
>>> ## shows if some expected file really is in the working dir<BR>
>>><BR>
>>> <BR>
>>><BR>
>>> <BR>
>>> <BR>
>>>> -----Original Message-----<BR>
>>>> From: mpich-discuss-bounces@mcs.anl.gov<BR>
>>>> [<A HREF="mailto:mpich-discuss-bounces@mcs.anl.gov">mailto:mpich-discuss-bounces@mcs.anl.gov</A>] On Behalf Of<BR>
>>>> tsilva@coas.oregonstate.edu<BR>
>>>> Sent: Friday, November 07, 2008 1:26 AM<BR>
>>>> To: mpich-discuss@mcs.anl.gov<BR>
>>>> Subject: Re: [mpich-discuss] mpiexec and working directory<BR>
>>>><BR>
>>>> Quoting Rajeev Thakur <thakur@mcs.anl.gov>:<BR>
>>>><BR>
>>>> <BR>
>>>> <BR>
>>>>> If you cd to the directory containing the executable, say<BR>
>>>>> <BR>
>>>>> <BR>
>>>> a.out, and<BR>
>>>> <BR>
>>>> <BR>
>>>>> do "mpiexec -n 2 a.out" does it expect to find input<BR>
>>>>> <BR>
>> files in your<BR>
>> <BR>
>>>>> home directory? That's odd.<BR>
>>>>> <BR>
>>>>> <BR>
>>>> That is correct. I have tried another simpler code and the same<BR>
>>>> thing happens.<BR>
>>>><BR>
>>>> <BR>
>>>> <BR>
>>>>>> -----Original Message-----<BR>
>>>>>> From: mpich-discuss-bounces@mcs.anl.gov<BR>
>>>>>> [<A HREF="mailto:mpich-discuss-bounces@mcs.anl.gov">mailto:mpich-discuss-bounces@mcs.anl.gov</A>] On Behalf Of<BR>
>>>>>> <BR>
>> Tiago Silva<BR>
>> <BR>
>>>>>> Sent: Thursday, November 06, 2008 6:02 PM<BR>
>>>>>> To: mpich-discuss@mcs.anl.gov<BR>
>>>>>> Subject: Re: [mpich-discuss] mpiexec and working directory<BR>
>>>>>><BR>
>>>>>> Rajeev Thakur wrote:<BR>
>>>>>> <BR>
>>>>>> <BR>
>>>>>>> 1.0.3 is an ancient version of MPICH2. Try the latest<BR>
>>>>>>> <BR>
>>>>>>> <BR>
>>>>>> version, 1.0.8.<BR>
>>>>>> <BR>
>>>>>> I will ask my systems administrator to do so.<BR>
>>>>>><BR>
>>>>>> <BR>
>>>>>> <BR>
>>>>>>> The parameters to mpiexec are not identical between MPICH-1 and<BR>
>>>>>>> MPICH2. Do mpiexec --help. Make sure you are calling<BR>
>>>>>>> <BR>
>>>>>>> <BR>
>>>>>> MPICH2's mpiexec, not MPICH-1's.<BR>
>>>>>> <BR>
>>>>>> I am actually invoking mpiexec with its full path. Is there any<BR>
>>>>>> incorrect parameter on my mpiexec call?<BR>
>>>>>> I<BR>
>>>>>> <BR>
>>>>>> <BR>
>>>>>>> If your input files are in the same directory as the<BR>
>>>>>>> <BR>
>>>>>>> <BR>
>>>>>> executable, you<BR>
>>>>>> <BR>
>>>>>> <BR>
>>>>>>> should not need to specify anything.<BR>
>>>>>>><BR>
>>>>>>> <BR>
>>>>>>> <BR>
>>>>>> But that is exactly the problem. The executable can't find<BR>
>>>>>> <BR>
>>>>>> <BR>
>>>> the input<BR>
>>>> <BR>
>>>> <BR>
>>>>>> files on the working directory.<BR>
>>>>>><BR>
>>>>>><BR>
>>>>>> <BR>
>>>>>> <BR>
>>>>> <BR>
>>>>> <BR>
>>>><BR>
>>>> <BR>
>>>> <BR>
>>> <BR>
>>> <BR>
>> <BR>
><BR>
> <BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>