[mpich-discuss] Problem while running example program Cpi with morethan 1 task

[Thejna Tharammal]

 Hi Pavan,
Thank you for the reply,
 I ran them from k1 itself,
Now I went back one step and configured 1.2.1p1 and 1.3b1 with
--with-device=ch3:sock option, then no errors are showing up with cpi (I
used hydra for both)
I am attaching the files - results , (with 6 hosts,48 processes)
But when I use -verbose option I see some strange messages.
I used mpiexec -n 48 ./cpi & 
mpiexec -verbose -n 48 ./cpi
Thanks,
Thejna
----------------original message-----------------
From: "Pavan Balaji" balaji at mcs.anl.gov
To: "Thejna Tharammal" ttharammal at marum.de
CC: mpich-discuss at mcs.anl.gov
Date: Tue, 07 Sep 2010 20:33:00 -0500
-------------------------------------------------
 
 
> 
> Sorry for the delay in getting back to this.
> 
> On 09/03/2010 07:43 AM, Thejna Tharammal wrote:
>> Ok, I tried that,
>>
>> No.of hosts 1:
>> -bash-3.2$ mpiexec -n 7 ./cpi
>> Process 1 of 7 is on k1
>> Process 4 of 7 is on k1
>> Process 5 of 7 is on k1
>> Process 2 of 7 is on k1
>> Process 6 of 7 is on k1
>> Process 0 of 7 is on k1
>> Process 3 of 7 is on k1
>> pi is approximately 3.1415926544231239, Error is 0.0000000008333307
>> wall clock time = 0.000198
>> APPLICATION TERMINATED WITH THE EXIT STRING: Terminated (signal 15)
> 
> It looks like even on node is having problems. Are you executing the 
> mpiexec from k1? Can you try executing it from k1?
> 
> Thanks,
> 
> -- Pavan
> 
> -- 
> Pavan Balaji
> http://www.mcs.anl.gov/~balaji
> 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: result_cpi
Type: application/octet-stream
Size: 1376 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20100908/ab8bb8fa/attachment-0002.obj>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: verbose_cpi
Type: application/octet-stream
Size: 168234 bytes
Desc: not available
URL: <http://lists.mcs.anl.gov/pipermail/mpich-discuss/attachments/20100908/ab8bb8fa/attachment-0003.obj>