Thanks! Works as advertised ... now.
I tried it without the quotes but with two \; and this works as well.
Not sure to whom to communicate it to but http://www.mpi-forum.org
should update their web site.
Thanks again,
John
On Sun, Apr 14, 2013 at 12:15 PM, Ralph Castain wrote:
> Well, first
Well, first thing is that the example is garbage - cannot work as written. I've
attached corrected versions.
Even with those errors, though, it got thru comm_connect just fine for me IF
you put quotes around the entire port. With the corrected versions, I get this:
$ mpirun -n 1 ./server
server
Yep, I saw both semi-colons but the client process hangs at:
MPI_Comm_connect( port_name, MPI_INFO_NULL, 0, MPI_COMM_WORLD, &server );
---John
On Sat, Apr 13, 2013 at 10:05 PM, Ralph Castain wrote:
> Did you see that there are two semi-colon's in that line? They both need to
> be protected f
Did you see that there are two semi-colon's in that line? They both need to be
protected from the shell. I would just put quotes around the whole thing.
Other than that, it looks okay to me...I assume you are using a 1.6 series
release?
On Apr 13, 2013, at 4:54 PM, John Chludzinski
wrote:
>
After I replaced ";" with "\;" in the server name I got passed the
ABORT problem. Now the client and server deadlock until I finally get
(on the client side):
mpirun noticed that the job aborted, but has no info as to the process
that caused that situation.
---
Sorry: The previous post was intended for another group, ignore it.
With regards to the client-server problem:
$ mpirun -n 1 client
3878879232.0;tcp://192.168.1.4:37625+3878879233.0;tcp://192.168.1.4:38945:300
[jski:01882] [[59199,1],0] ORTE_ERROR_LOG: Not found in file
dpm_orte.c at line 158
[j
After I "source mpi.ksk", PATH is unchanged but LD_LIBRARY_PATH is there:
$ print $LD_LIBRARY_PATH
/usr/lib64/openmpi/lib/
Why does PATH loose its change?
---John
On Sat, Apr 13, 2013 at 12:55 PM, Ralph Castain wrote:
> You need to pass in the port info that the server printed - just co
You need to pass in the port info that the server printed - just copy/paste the
line below "server available at".
On Apr 12, 2013, at 10:58 PM, John Chludzinski
wrote:
> Found the following client-server example (code) on
> http://www.mpi-forum.org and I'm trying to get it to work. Not sure
>
Found the following client-server example (code) on
http://www.mpi-forum.org and I'm trying to get it to work. Not sure
what argv[1] should be for the client? The output from the server
side is:
server available at
4094230528.0;tcp://192.168.1.4:55803+4094230529.0;tcp://192.168.1.4:51618: