[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

problems with remote staging of mpi pgms

To: mpich-g@globus.org
Subject: problems with remote staging of mpi pgms
From: guna kosh <platezz_a@yahoo.co.uk>
Date: Thu, 10 Mar 2005 06:04:01 +0000 (GMT)
Delivered-to: glbs-mpich-g-outgoing@mailbouncer.mcs.anl.gov
Delivered-to: glbs-mpich-g@mailbouncer.mcs.anl.gov
Sender: owner-mpich-g@globus.org

We are facing a small problem regarding running an MPI
program in a remote machine and displaying its results
in the job submitting node.
All other programs (script files and normal C
programs) are working fine with remote staging of
executables. 
The procedure followed by us for running mpi pgm is:
1. writing the code with mpi statements.(say ex.c)
2. compiling using <MPICH-Install-dir>/bin/mpicc ex.c
-o ex
3. globusrun -r a1 '&(executable=<valid path of ex>)
(stdout="<FQDN>/dev/stdout")
The following log file is created in machine a1.
3/10 11:11:49 JMI: Getting RSL output value
3/10 11:11:49 JMI: Processing output positions
3/10 11:11:49 JMI: Getting RSL output value
3/10 11:11:49 JMI: Processing output positions
3/10 11:11:49 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_REMOTE_IO_FILE_CREATE
3/10 11:11:49 JM: Opening output destinations
3/10 11:11:49 JM: stdout goes to
x-gass-cache://btts4.stp.cdac.ernet.in/2115.1110433309/dev/stdout
3/10 11:11:49 JM: stderr goes to
x-gass-cache://btts4.stp.cdac.ernet.in/2115.1110433309/dev/stderr
3/10 11:11:49 JM: Opening
https://btts2.stp.cdac.ernet.in:2001/dev/stdout
3/10 11:11:49 JM: Opened GASS handle 1.
3/10 11:11:49 JM: exiting
globus_l_gram_job_manager_output_destination_open()
3/10 11:11:49 JM: Opening
https://btts2.stp.cdac.ernet.in:2001/dev/stderr
3/10 11:11:49 JM: Opened GASS handle 2.
3/10 11:11:49 JM: exiting
globus_l_gram_job_manager_output_destination_open()
3/10 11:11:49 stdout or stderr is being used, starting
to poll
3/10 11:11:49 JM: Finished opening output destinations
3/10 11:11:49 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_OPEN_OUTPUT
3/10 11:11:49 JM: GSSAPI type is GSI.. relocating
proxy
3/10 11:11:49 JMI: testing job manager scripts for
type fork exist and permissions are ok.
3/10 11:11:49 JMI: completed script validation: job
manager type is fork.
3/10 11:11:49 JMI: in
globus_gram_job_manager_script_proxy_relocate()
3/10 11:11:49 JMI: cmd = proxy_relocate
Thu Mar 10 11:11:50 2005 JM_SCRIPT: New Perl
JobManager created.
Thu Mar 10 11:11:50 2005 JM_SCRIPT:
proxy_relocate(enter)
3/10 11:11:50 JMI: while return_buf =
GRAM_SCRIPT_X509_USER_PROXY =
/home/budania/.globus/.gass_cache/local/md5/fc/902bcb6cbe1d0c66880fd95d800ed7/md5/65/e2c681db1feaf32e44b3c4a7ad117c/data
3/10 11:11:50 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_PROXY_RELOCATE
3/10 11:11:50 JM: Relocated Proxy to
/home/budania/.globus/.gass_cache/local/md5/fc/902bcb6cbe1d0c66880fd95d800ed7/md5/65/e2c681db1feaf32e44b3c4a7ad117c/data
3/10 11:11:50 JM: before sending to client: rc=0
(Success)
3/10 11:11:50 Job Manager State Machine (exiting):
GLOBUS_GRAM_JOB_MANAGER_STATE_TWO_PHASE
3/10 11:11:50 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_TWO_PHASE
3/10 11:11:50 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_TWO_PHASE_COMMITTED
3/10 11:11:50 JM: NOT empty client callback list.
3/10 11:11:50 JM: sending callback of status 64
(failure code 0) to
https://btts2.stp.cdac.ernet.in:1743/.
3/10 11:11:50 JMI: testing job manager scripts for
type fork exist and permissions are ok.
3/10 11:11:50 JMI: completed script validation: job
manager type is fork.
3/10 11:11:50 JMI: in
globus_gram_job_manager_script_stage_in()
3/10 11:11:50 JMI: cmd = stage_in
3/10 11:11:51 JMI: returning with success
3/10 11:11:51 globus_gram_job_manager_query_callback()
not a literal URI match
3/10 11:11:51 JM : in
globus_l_gram_job_manager_query_callback, query=cancel
3/10 11:11:51 JM : reply: (status=64 failure code=0
(Success))
3/10 11:11:51 JM : sending reply:
protocol-version: 2^M
status: 64^M
failure-code: 0^M
job-failure-code: 0^M
^@3/10 11:11:51 -------------------
Thu Mar 10 11:11:52 2005 JM_SCRIPT: New Perl
JobManager created.
Thu Mar 10 11:11:52 2005 JM_SCRIPT: stage_in(enter)
Thu Mar 10 11:11:53 2005 JM_SCRIPT: stage_in(exit)
3/10 11:11:53 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED
3/10 11:11:53 closing destination
https://btts2.stp.cdac.ernet.in:2001/dev/stdout
3/10 11:11:53 JM: exiting
globus_l_gram_job_manager_output_destination_close()
3/10 11:11:53 closing destination
https://btts2.stp.cdac.ernet.in:2001/dev/stderr
3/10 11:11:53 JM: exiting
globus_l_gram_job_manager_output_destination_close()
3/10 11:11:53 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_CLOSE_OUTPUT
3/10 11:11:53 JM: in
globus_gram_job_manager_history_file_create()
3/10 11:11:53 JM: NOT empty client callback list.
3/10 11:11:53 JM: sending callback of status 4
(failure code 8) to
https://btts2.stp.cdac.ernet.in:1743/.
3/10 11:11:53 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_TWO_PHASE
3/10 11:11:53 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_TWO_PHASE_COMMITTED
3/10 11:11:53 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_FILE_CLEAN_UP
3/10 11:11:53 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_SCRATCH_CLEAN_UP
3/10 11:11:53 JMI: testing job manager scripts for
type fork exist and permissions are ok.
3/10 11:11:53 JMI: completed script validation: job
manager type is fork.
3/10 11:11:53 JMI: cmd = cache_cleanup
Thu Mar 10 11:11:54 2005 JM_SCRIPT: New Perl
JobManager created.
Thu Mar 10 11:11:54 2005 JM_SCRIPT:
cache_cleanup(enter)
Thu Mar 10 11:11:54 2005 JM_SCRIPT:
cache_cleanup(exit)
3/10 11:11:54 Job Manager State Machine (entering):
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_CACHE_CLEAN_UP
3/10 11:11:54 JM: in
globus_gram_job_manager_reporting_file_remove()
3/10 11:11:54 JM: exiting globus_gram_job_manager.

Please help us to solve this..

guna kosh
C-DAC Pune,
India

Send instant messages to your online friends http://uk.messenger.yahoo.com

Follow-Ups:
- Re: problems with remote staging of mpi pgms
  - From: Karonis Nicholas <karonis@niu.edu>

Prev by Date: doubts on mpich g2 regarding process spawing in 2 machines
Next by Date: Re: problems with remote staging of mpi pgms
Previous by thread: doubts on mpich g2 regarding process spawing in 2 machines
Next by thread: Re: problems with remote staging of mpi pgms
Index(es):
- Date
- Thread