-
Notifications
You must be signed in to change notification settings - Fork 0
/
part0001.9.html
765 lines (763 loc) · 47.2 KB
/
part0001.9.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
<!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: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2> Hi,<BR>
Did you get a chance to look at the setup ?<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov [<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A>] On Behalf Of mpich2<BR>
Sent: Thursday, September 11, 2008 12:09 PM<BR>
To: undisclosed-recipients:<BR>
Subject: Re: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> | Owner: jayesh <BR>
Type: bug | Status: assigned<BR>
Priority: major | Component: mpich2 <BR>
Resolution: | Keywords: <BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
<BR>
<BR>
Comment (by Ayer, Timothy C.):<BR>
<BR>
Jayesh,<BR>
<BR>
I apologize for the delay. I hope to get back to this soon but other items have taken higher priority.<BR>
<BR>
Thanks,<BR>
Tim<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C.<BR>
Sent: Wednesday, August 13, 2008 4:10 PM<BR>
To: Jayesh Krishna; Ayer, Timothy C.<BR>
Cc: mpich2-maint@mcs.anl.gov<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
Will do.<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>]<BR>
Sent: Wednesday, August 13, 2008 4:02 PM<BR>
To: timothy.ayer@pw.utc.com<BR>
Cc: mpich2-maint@mcs.anl.gov<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
<BR>
Hi,<BR>
I just cross-verified the timestamps of the dlls and they look alright.<BR>
Make sure that you have the date/timestamps right on all the hosts involved.<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov [<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A><BR>
<<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A>> ] On Behalf Of mpich2<BR>
Sent: Wednesday, August 13, 2008 2:53 PM<BR>
To: undisclosed-recipients:<BR>
Subject: Re: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> | Owner:<BR>
jayesh<BR>
Type: bug | Status:<BR>
assigned<BR>
Priority: major | Component:<BR>
mpich2<BR>
Resolution: | Keywords:<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
<BR>
<BR>
Comment (by Ayer, Timothy C.):<BR>
<BR>
That's a bummer I thought for sure that must be it....oh well. I will pursue the other two options.<BR>
<BR>
Thanks,<BR>
Tim<BR>
<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov [<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A><BR>
<<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A>> ]<BR>
On Behalf Of mpich2<BR>
Sent: Wednesday, August 13, 2008 3:50 PM<BR>
Subject: Re: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
------------------------------------------------------------+---------------<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> |<BR>
Owner:<BR>
jayesh<BR>
Type: bug |<BR>
Status:<BR>
assigned<BR>
Priority: major |<BR>
Component:<BR>
mpich2<BR>
Resolution: |<BR>
Keywords:<BR>
<BR>
<BR>
------------------------------------------------------------+---------------<BR>
<BR>
<BR>
Comment (by Jayesh Krishna):<BR>
<BR>
Hi,<BR>
I spoke too soon. We have discontinued supporting sshm channel and that<BR>
is the reason that you have an old version of sshm related dlls in your<BR>
system32 directory.<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov [<A HREF="mailto:owner-">mailto:owner-</A> <<A HREF="mailto:owner-">mailto:owner-</A>> mpich2-bugs@mcs.anl.gov]<BR>
On Behalf Of mpich2<BR>
Sent: Wednesday, August 13, 2008 2:38 PM<BR>
To: undisclosed-recipients:<BR>
Subject: Re: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> |<BR>
Owner:<BR>
jayesh<BR>
Type: bug |<BR>
Status:<BR>
assigned<BR>
Priority: major |<BR>
Component:<BR>
mpich2<BR>
Resolution: |<BR>
Keywords:<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
<BR>
<BR>
Comment (by Jayesh Krishna):<BR>
<BR>
Hi,<BR>
Hmmm... This looks like the problem that I mentioned in my email.<BR>
*sshm*.dll s should have the same datestamp as other dlls (should not be<BR>
from 2005!).<BR>
Please try the following,<BR>
<BR>
# Uninstall MPICH2 on the hosts involved in your job.<BR>
# Manually delete the MPICH2 dlls from windows\system32 directory (Please<BR>
be careful! Make sure that you delete only mpich2*.dll & mpe*.dll) #<BR>
Re-install MPICH2 1.0.7 (stable version) on the hosts/nodes .<BR>
# Re-compile cpi.c/fpi.c and try running your job.<BR>
<BR>
Let us know the results.<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov<BR>
[<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A><BR>
<<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A>> ]<BR>
On Behalf Of mpich2<BR>
Sent: Wednesday, August 13, 2008 2:11 PM<BR>
To: undisclosed-recipients:<BR>
Subject: Re: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> |<BR>
Owner:<BR>
jayesh<BR>
Type: bug |<BR>
Status:<BR>
assigned<BR>
Priority: major |<BR>
Component:<BR>
mpich2<BR>
Resolution: |<BR>
Keywords:<BR>
<BR>
------------------------------------------------------------+-----------<BR>
------------------------------------------------------------+----<BR>
<BR>
<BR>
Comment (by Ayer, Timothy C.):<BR>
<BR>
Hi Jayesh,<BR>
<BR>
Great to hear from you. I will try your suggestions (icpi.c and slow<BR>
response).<BR>
<BR>
Also here is the output you requested. I have been wondering why the<BR>
dates on mpich2sshm.dll and mpich2sshmp.dll seem so old (from 2005)???<BR>
...I should have mentioned it sooner.<BR>
<BR>
Thanks,<BR>
Tim<BR>
<BR>
<BR>
C:\WINDOWS\system32>dir c:\windows\system32\mpe*.dll<BR>
Volume in drive C is System<BR>
Volume Serial Number is D8B5-0657<BR>
<BR>
Directory of c:\windows\system32<BR>
<BR>
04/04/2008 05:46 PM 135,168 mpe.dll<BR>
1 File(s) 135,168 bytes<BR>
0 Dir(s) 4,497,502,208 bytes free<BR>
<BR>
C:\WINDOWS\system32><BR>
<BR>
<BR>
C:\WINDOWS\system32>dir dir c:\windows\system32\mpich2*.dll<BR>
Volume in drive C is System<BR>
Volume Serial Number is D8B5-0657<BR>
<BR>
Directory of C:\WINDOWS\system32<BR>
<BR>
<BR>
Directory of C:\WINDOWS\system32<BR>
<BR>
04/04/2008 05:28 PM 1,110,016 mpich2.dll<BR>
04/04/2008 05:47 PM 151,552 mpich2mpe.dll<BR>
04/04/2008 05:23 PM 159,744 mpich2mpi.dll<BR>
04/04/2008 06:31 PM 1,159,168 mpich2mt.dll<BR>
04/04/2008 06:42 PM 1,351,680 mpich2mtp.dll<BR>
04/04/2008 05:43 PM 1,306,624 mpich2p.dll<BR>
04/04/2008 05:55 PM 1,093,632 mpich2shm.dll<BR>
04/04/2008 06:03 PM 1,294,336 mpich2shmp.dll<BR>
11/23/2005 02:33 AM 1,032,192 mpich2sshm.dll<BR>
<<<<<<<<<<<<<<<<<BR>
11/23/2005 02:36 AM 1,294,336 mpich2sshmp.dll<BR>
<<<<<<<<<<<<<<<<<BR>
04/04/2008 06:14 PM 1,122,304 mpich2ssm.dll<BR>
04/04/2008 06:22 PM 1,343,488 mpich2ssmp.dll<BR>
12 File(s) 12,419,072 bytes<BR>
0 Dir(s) 4,497,502,208 bytes free<BR>
<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov<BR>
[<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A><BR>
<<A HREF="mailto:owner-mpich2-bugs@mcs.anl.gov">mailto:owner-mpich2-bugs@mcs.anl.gov</A>> ]<BR>
On Behalf Of mpich2<BR>
Sent: Wednesday, August 13, 2008 2:58 PM<BR>
Subject: Re: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------+-------------<BR>
--<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> |<BR>
Owner:<BR>
jayesh<BR>
Type: bug |<BR>
Status:<BR>
assigned<BR>
Priority: major |<BR>
Component:<BR>
mpich2<BR>
Resolution: |<BR>
Keywords:<BR>
<BR>
<BR>
<BR>
------------------------------------------------------------+-------------<BR>
--<BR>
<BR>
<BR>
Comment (by Jayesh Krishna):<BR>
<BR>
Hi,<BR>
The logs sent by you show that the communication btw the process<BR>
managers on the hosts is good. The problem looks to be with the<BR>
communication btw the MPI processes.<BR>
<BR>
# Can you try compiling icpi.c (MPICH2\examples) and run the program in<BR>
your setup (Make sure that the problem is not related to fortran<BR>
bindings).<BR>
# I have seen that some times that the uninstall/install of MPICH2 does<BR>
not result in the dlls being updated correctly (This has lead to some<BR>
wierd-difficult-to-debug hangs in our tests. This is not usual but it<BR>
does<BR>
not hurt to check for it though). To make sure that you have the right<BR>
dlls try listing the MPICH2 dlls in your windows system32 directory on<BR>
both the hosts,<BR>
<BR>
>>> dir c:\windows\system32\mpich2*.dll<BR>
>>> dir c:\windows\system32\mpe*.dll<BR>
<BR>
Send us the results for verification (Sanity check- they should have<BR>
the<BR>
same datestamp)<BR>
<BR>
# Also when running fpi.exe using your setup try leaving the job (or<BR>
may<BR>
be specify a timeout of 10 mins or so) for 10mins or so and see if it<BR>
reports any errors. You might want to run netstat (or use "Process<BR>
explorer" from microsoft and check the TCP/IP tab in the<BR>
process->properties) to see what happens to the connections btw the MPI<BR>
processes from both hosts.<BR>
<BR>
(PS: The MPICH2 1.1.0a1 release<BR>
<BR>
<BR>
(<A HREF="http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=dow">http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=dow</A><BR>
<<A HREF="http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=dow">http://www.mcs.anl.gov/research/projects/mpich2/downloads/index.php?s=dow</A>><BR>
nloads) is aimed at MPICH2 devs and not for production machines. )<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Tuesday, August 05, 2008 9:20 AM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
Please find attached the output from the smpd -d procs. Also, the<BR>
output<BR>
from the mpiexec just so you can see what I typed.<BR>
<BR>
H:\>mpiexec.exe -map v:\\10.30.73.170\temp -hosts 2 10.30.73.170<BR>
10.30.73.34 v:\fpi.exe<BR>
Process 0 of 2 is alive<BR>
Enter the number of intervals: (0 quits)<BR>
Process 1 of 2 is alive<BR>
Before bcast 1 of 2 is alive<BR>
10<BR>
Before bcast 0 of 2 is alive<BR>
100<BR>
<BR>
<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 5:10 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
The socket/channel connection between the MPI processes take place<BR>
during<BR>
MPI_Bcast() (not before that in fpi.f).<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 4:00 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
The firewall has been disabled.<BR>
<BR>
The inputs were from me entering values for estimating pi...I wanted to<BR>
make sure the program ran through all the logic.<BR>
<BR>
I will send the other debug output a little later.<BR>
<BR>
Also, as an fyi, we have been running MPICH on thousands of PC's for<BR>
years now. The other strange part is that over a year ago I did<BR>
successfully run MPICH2 on over 30 processors. My first thought was<BR>
the<BR>
firewall as well.<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 4:46 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
# Do you have windows firewall (or any firewall) running on these<BR>
machines<BR>
?<BR>
# Why do I see two inputs (10 & 100) in the mpiexec debug output ?<BR>
# Can you send us the debug output of smpd along with mpiexec ?<BR>
# Can you check the status of the remote smpd from each host ?<BR>
--- On host A, run "smpd -status IPAddressOf_hostB"<BR>
--- On host B, run "smpd -status IPAddressOf_hostA"<BR>
<BR>
(PS: I just tried running fpi.exe in a shared drive across two 32-bit<BR>
windows XP machines in our lab but did not get any errors/hang)<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 3:11 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
This is the same fpi.f which comes with the installation with the<BR>
exception that I have added print statements.<BR>
<BR>
The setup is homogenous (both 32-bit). The output is attached.<BR>
<BR>
Thanks for your help.<BR>
<BR>
Tim<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 3:48 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
# Are you running fpi.exe (fpi.f) provided with MPICH2 (Have you<BR>
modified<BR>
the program ?)?<BR>
# I am assuming that the setup is not heterogeneous (MPICH2 currently<BR>
does<BR>
not support running jobs across machines with different data models<BR>
eg:<BR>
You cannot run your MPI job across 32-bit and 64-bit machines)<BR>
# Please provide us with the debug/verbose output when running fpi.exe.<BR>
Start smpd on both the machines in debug mode (1. Stop any instances of<BR>
smpd running on the system, smpd -stop 2. Start smpd in debug mode,<BR>
smpd<BR>
-d) and run mpiexec in verbose mode (mpiexec.exe -verbose -map<BR>
y:\\IPAddressOf_hostA\temp -hosts 2 IPAddressOf_hostA IPAddressOf_hostB<BR>
y:\fpi.exe)<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 2:21 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
Thanks, here is the output (note: I have not included IP address or<BR>
actual hostnames in this email but did use them in testing)<BR>
<BR>
# mpiexec.exe -map y:\\IPAddressOf_hostA\temp -hosts 2<BR>
IPAddressOf_hostA<BR>
IPAddressOf_hostB y:\fpi.exe<BR>
<BR>
OUTPUT:<BR>
Process 0 of 2 is alive<BR>
Enter the number of intervals: (0 quits)<BR>
Process 1 of 2 is alive<BR>
Before bcast 1 of 2 is alive<BR>
10<BR>
Before bcast 0 of 2 is alive<BR>
<BR>
# mpiexec.exe -map y:\\IPAddressOf_hostA\temp hostname<BR>
<BR>
XXXXXX (hostname of hostA)<BR>
<BR>
<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 3:13 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
The command hostname (c:\windows\system32\hostname.exe)<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 2:11 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
You have "hostname" at the end of the second line...what is that<BR>
referring<BR>
to?<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 2:47 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
What is the error message (output) that you get when you run mpiexec ?<BR>
Pls provide us with the output of the following commands (Make sure<BR>
that<BR>
you specify ipaddresses of the hosts involved),<BR>
<BR>
# mpiexec.exe -map y:\\IPAddressOf_hostA\temp -hosts 2<BR>
IPAddressOf_hostA<BR>
IPAddressOf_hostB y:\fpi.exe<BR>
# mpiexec.exe -map y:\\IPAddressOf_hostA\temp hostname<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 1:25 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
No this does not work...the behavior is the same. The UNC's<BR>
should/have<BR>
worked regardless of whether a user a user is logged in. We have never<BR>
relied on drive network drive mappings since they are intermittently an<BR>
"interactive" feature.<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 2:02 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Cc: mpich2-maint@mcs.anl.gov<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
You should try,<BR>
<BR>
mpiexec.exe -map y:\\hostA\temp -hosts 2 hostA hostB y:\fpi.exe<BR>
<<A HREF="file://hosta/temp/fpi.exe <file://hosta/temp/fpi.exe">file://hosta/temp/fpi.exe <file://hosta/temp/fpi.exe</A>> ><BR>
<BR>
Let us know if it works for you.<BR>
<BR>
(PS: The shared drive is accessible across machines because the drive<BR>
is<BR>
accessible/mapped by the user logged on to the machines. SMPD runs as a<BR>
service logged on as "Local System" and does not - should not- have<BR>
access<BR>
to drives shared by users)<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 12:50 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
The exe can be directly accessed from hostB by executing<BR>
\\hostA\temp\fpi.exe, that is, you could type it directly into a<BR>
command<BR>
prompt from hostB if you wanted. Note also that \temp directory is a<BR>
shared location. I am not sure physically how this is setup on our<BR>
network but this has worked with out any "mapping" for MPICH (MPICH1).<BR>
<BR>
Note: I did try: mpiexec.exe -map y:\\hostA\temp -hosts 2 hostA hostB<BR>
\\hostA\temp\fpi.exe but that still hangs in the MPI_Bcast call.<BR>
<BR>
The interesting part is that it gets through the initialization:<BR>
<BR>
call MPI_INIT( ierr )<BR>
call MPI_COMM_RANK( MPI_COMM_WORLD, myid, ierr )<BR>
call MPI_COMM_SIZE( MPI_COMM_WORLD, numprocs, ierr )<BR>
<BR>
<BR>
All execute.<BR>
<BR>
Thanks,<BR>
Tim<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 1:33 PM<BR>
To: 'Ayer, Timothy C.'<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
How (what mechanism) does hostB access data (exe) in hostA ?<BR>
<BR>
Regards,<BR>
Jayesh<BR>
<BR>
_____<BR>
<BR>
From: Ayer, Timothy C. [<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A> <<A HREF="mailto:timothy.ayer@pw.utc.com">mailto:timothy.ayer@pw.utc.com</A>> ]<BR>
Sent: Monday, August 04, 2008 12:31 PM<BR>
To: Jayesh Krishna<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
Thanks Jayesh for the quick reply. This is a network availabe UNC path<BR>
-<BR>
why do I need to map a drive?<BR>
<BR>
I am familiar with the machines file - I was just using the command<BR>
line<BR>
for debugging.<BR>
<BR>
_____<BR>
<BR>
From: Jayesh Krishna [<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A> <<A HREF="mailto:jayesh@mcs.anl.gov">mailto:jayesh@mcs.anl.gov</A>> ]<BR>
Sent: Monday, August 04, 2008 10:56 AM<BR>
To: timothy.ayer@pw.utc.com<BR>
Cc: mpich2-maint@mcs.anl.gov<BR>
Subject: RE: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
<BR>
Hi,<BR>
If you are running your executable from a shared network drive you<BR>
need<BR>
to map (see "--map" option of mpiexec in the window's developer's<BR>
guide)<BR>
the network drive with mpiexec when launching your job.<BR>
Also make sure that you have turned the windows firewall (or any<BR>
other<BR>
firewalls) off on the machines involved in the job.<BR>
Try specifying the ip addresses of the machines instead of the<BR>
hostnames.<BR>
Let us know the results.<BR>
<BR>
(PS: Instead of the "-hosts" option you could try using the<BR>
"-machinefile"<BR>
option available with mpiexec. See the window's developer's guide for<BR>
details.)<BR>
<BR>
Regards,<BR>
Jayesh<BR>
-----Original Message-----<BR>
From: owner-mpich2-bugs@mcs.anl.gov [<A HREF="mailto:owner-">mailto:owner-</A> <<A HREF="mailto:owner-">mailto:owner-</A>><BR>
mpich2-bugs@mcs.anl.gov]<BR>
On Behalf Of mpich2<BR>
Sent: Monday, August 04, 2008 9:33 AM<BR>
To: undisclosed-recipients:<BR>
Subject: [mpich2-maint] #36: MPICH2 fpi.exe hanging on Windows XP<BR>
<BR>
<BR>
-----------------------------------------------------------+------------<BR>
-----------------------------------------------------------+----<BR>
Reporter: "Ayer, Timothy C." <timothy.ayer@pw.utc.com> |<BR>
Type:<BR>
bug<BR>
Status: new |<BR>
Priority:<BR>
major<BR>
Component: mpich2 |<BR>
<BR>
-----------------------------------------------------------+------------<BR>
-----------------------------------------------------------+----<BR>
<BR>
<BR>
I am testing MPICH2 MPICH2-1.0.7 Windows XP (sp2). I have installed<BR>
it<BR>
on<BR>
2<BR>
hosts (hostA, hostB) and trying to run the fpi.exe built with<BR>
fmpich2.lib.<BR>
The code is hanging in a MPI_Bcast call. The fpi.exe source is<BR>
attached.<BR>
<BR>
The following tests work fine from hostA, both prompt for a number of<BR>
intervals, accept input, and produce and estimate of PI<BR>
<BR>
mpiexec.exe -hosts 2 hostA hostA \\hostA\temp\fpi.exe<BR>
<\\hostA\temp\fpi.exe><BR>
<BR>
mpiexec.exe -hosts 2 hostB hostB \\hostA\temp\fpi.exe<BR>
<\\hostA\temp\fpi.exe><BR>
<BR>
<BR>
<BR>
The following test hangs when submitted from hostA (in MPI_Bcast).<BR>
It<BR>
does prompt for input (number of intervals) but once entered it hangs.<BR>
I<BR>
have launched the smpd process using smpd -d but see no output from<BR>
the<BR>
smpd after I enter an interval value<BR>
<BR>
mpiexec.exe -hosts 2 hostA hostB \\hostA\temp\fpi.exe<BR>
<\\hostA\temp\fpi.exe><BR>
<BR>
<BR>
Any suggestions would be appreciated. Also let me know if you want<BR>
me<BR>
to<BR>
send debug output.<BR>
<BR>
Thanks,<BR>
Tim<BR>
<BR>
_____________________<BR>
Timothy C. Ayer<BR>
High Performance Technical Computing<BR>
United Technologies - Pratt & Whitney<BR>
timothy.ayer@pw.utc.com<BR>
(860) 565 - 5268 v<BR>
(860) 565 - 2668 f<BR>
<BR>
<<fpi.f>><BR>
<BR>
<BR>
--<BR>
Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/36<BR>
<<A HREF="https://trac.mcs.anl.gov/projects/mpich2/ticket/36">https://trac.mcs.anl.gov/projects/mpich2/ticket/36</A>> ><BR>
<BR>
--<BR>
Ticket URL:<BR>
<https://trac.mcs.anl.gov/projects/mpich2/ticket/36#comment:><BR>
<BR>
--<BR>
Ticket URL:<BR>
<https://trac.mcs.anl.gov/projects/mpich2/ticket/36#comment:><BR>
<BR>
--<BR>
Ticket URL:<BR>
<https://trac.mcs.anl.gov/projects/mpich2/ticket/36#comment:><BR>
<BR>
--<BR>
Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/36#comment:><BR>
<BR>
--<BR>
Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/36#comment:><BR>
<BR>
--<BR>
Ticket URL: <https://trac.mcs.anl.gov/projects/mpich2/ticket/36#comment:><BR>
<BR>
</FONT>
</P>
</BODY>
</HTML>