Re: [gt-user] Defining GPT_TCP_PORT_RANGE for the client

Thu, 30 Oct 2008 18:02:49 -0700 

Hi Charles,
To confirm that it is the right results I am seeing, I have changed the a.rsl to execute /bin/env, rather than /bin/date. 

[EMAIL PROTECTED] ~]$ cat a.rsl


&(executable="/bin/env")(stdout="https://grid1.ramscommunity.org:40050/dev/stdout 
")


[EMAIL PROTECTED] ~]$ globusrun -r grid2 -f a.rsl

globus_gram_client_callback_allow successful

GRAM Job submission failed because data transfer to the server failed  
(error code 10)



I get this in the connection still blocking:

_CONDOR_ANCESTOR_25558=25559:1225414117:1237204608
_CONDOR_ANCESTOR_4681=4690:1224643119:1216157824
_CONDOR_ANCESTOR_4690=25558:1225414117:1826572179
LD_LIBRARY_PATH=
_CONDOR_SCRATCH_DIR=/scratch/condor/execute/dir_25558
_CONDOR_SLOT=1
_CONDOR_HIGHPORT=9670
GLOBUS_GRAM_MYJOB_CONTACT=URLx-nexus://grid2.ramscommunity.org:40002/
GLOBUS_GRAM_JOB_CONTACT=https://grid2.ramscommunity.org:40001/28012/1225414113/
_CONDOR_LOWPORT=9620
LOGNAME=yoichi
GLOBUS_LOCATION=/usr/local/globus

X509_USER_PROXY=/home/yoichi/.globus/job/grid2.ramscommunity.org/ 
28012.1225414113/x509_up

HOME=/home/yoichi


So, this is the confirmation that the jobs are submitted and they are  
ran. The gram log gets cleaned up a little while later.



This must be the envs of the condor user's process for this job. Is  
this what you wanted to see?



It does not get the GLOBUS_TCP_PORT_RANGE I have set in BASH env via / 
etc/profile. Probably this did not get started up as a BASH shell  
process. It seems it got only those define in the condor_config file  
(except for the requester details). Do I need to set it somewhere else  
so it gets it? Does it need it?


Thanks,
Yoichi

--------------------------------------------------------------------------
Yoichi Takayama, PhD
Senior Research Fellow
RAMP Project
MELCOE (Macquarie E-Learning Centre of Excellence)
MACQUARIE UNIVERSITY

Phone: +61 (0)2 9850 9073
Fax: +61 (0)2 9850 6527
www.mq.edu.au
www.melcoe.mq.edu.au/projects/RAMP/
--------------------------------------------------------------------------
MACQUARIE UNIVERSITY: CRICOS Provider No 00002J


This message is intended for the addressee named and may contain  
confidential information.  If you are not the intended recipient,  
please delete it and notify the sender. Views expressed in this  
message are those of the individual sender, and are not necessarily  
the views of Macquarie E-Learning Centre Of Excellence (MELCOE) or  
Macquarie University.


On 31/10/2008, at 6:50 AM, Charles Bacon wrote:


Okay, let's try another test.

grid1$ grid-proxy-init
grid1$ globus-gass-server -o -e -p 40050
[server address here]
<control does not return>


Create a file called a.rsl with these contents, replacing your GASS  
server url as appropriate:


grid1$ cat a.rsl

&(executable="/bin/date")(stdout="https://grid1.whatever:40050/dev/stdout 
")


grid1$ globusrun -r grid2 -f a.rsl
globus_gram_client_callback_allow successful
GRAM Job submission successful
GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE
GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE



Do you get any output from your GASS server?  Whether you do or not,  
please then log into grid2 and run:


grid2$ grid-proxy-init
grid2$ globus-url-copy file:///etc/group https://grid1.whatever:40050/dev/stdout


again replacing your GASS server url from grid1 as appropriate.  Do  
you get any output from your GASS server?



Charles

On Oct 30, 2008, at 12:20 AM, Yoichi Takayama wrote:


Hi Charles,

root uses /root for $HOME, as does other system users.


yoichi, condor, globus are all regular linux users and their $HOME  
are all under /home, which is an NFS mount, on grid1 and grid4, but  
not on grid2, which has a real /home and it exports it for other  
hosts to share it.


Is this a problem?


Should I have it on some other host or some other place and let  
grid2 to mount it also as a shared file system?




[EMAIL PROTECTED] ~]# su - yoichi
[EMAIL PROTECTED] ~]$ myproxy-logon -s grid2
Enter MyProxy pass phrase:
A credential has been received for user yoichi in /tmp/x509up_u500.

[EMAIL PROTECTED] ~]$ grid-cert-diagnostics

Checking Environment Variables
==============================
Checking if X509_CERT_DIR is set... no
Checking if X509_USER_CERT is set... no
Checking if X509_USER_KEY is set... no
Checking if X509_USER_PROXY is set... no

Checking Security Directories
=======================
Determining trusted cert path... /etc/grid-security/certificates
Checking for cog.properties... found
  WARNING: If the cog.properties file contains security properties,

           Java apps will ignore the security paths described in  
the GSI

           documentation

Checking trusted certificates...
================================
Getting trusted certificate list...
Checking CA file /etc/grid-security/certificates/51a418bb.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
51a418bb.0"... ok




(grid-proxy-init gives the same results as below, but gass works  
after grid-proxy-init but not just after myproxy-logon???)
(also, it that a problem to have cog.properties? This has just one  
line in it: tcp.port.range=40000,41000)



[EMAIL PROTECTED] ~]$ grid-proxy-init

Your identity: /O=Grid/OU=GlobusTest/OU=simpleCA- 
grid2.ramscommunity.org/OU=ramscommunity.org/CN=Yoichi Takayama

Enter GRID pass phrase for this identity:
Creating proxy ................................ Done
Your proxy is valid until: Fri Oct 31 03:24:30 2008

[EMAIL PROTECTED] ~]$ grid-cert-diagnostics

Checking Environment Variables
==============================
Checking if X509_CERT_DIR is set... no
Checking if X509_USER_CERT is set... no
Checking if X509_USER_KEY is set... no
Checking if X509_USER_PROXY is set... no

Checking Security Directories
=======================
Determining trusted cert path... /etc/grid-security/certificates
Checking for cog.properties... found
  WARNING: If the cog.properties file contains security properties,

           Java apps will ignore the security paths described in  
the GSI

           documentation

Checking trusted certificates...
================================
Getting trusted certificate list...
Checking CA file /etc/grid-security/certificates/51a418bb.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
51a418bb.0"... ok




(grid2 has 2 extra CAs i.e. 1c3f2ca8.0 and d1b603c3.0)


[EMAIL PROTECTED] ~]$ myproxy-logon -s grid2
Enter MyProxy pass phrase:
A credential has been received for user yoichi in /tmp/x509up_u500.
[EMAIL PROTECTED] ~]$ grid-cert-diagnostics
Checking Environment Variables
==============================
Checking if X509_CERT_DIR is set... no
Checking if X509_USER_CERT is set... no
Checking if X509_USER_KEY is set... no
Checking if X509_USER_PROXY is set... no

Checking Security Directories
=======================
Determining trusted cert path... /etc/grid-security/certificates
Checking for cog.properties... found
  WARNING: If the cog.properties file contains security properties,

           Java apps will ignore the security paths described in  
the GSI

           documentation

Checking trusted certificates...
================================
Getting trusted certificate list...
Checking CA file /etc/grid-security/certificates/1c3f2ca8.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
1c3f2ca8.0"... ok

Checking CA file /etc/grid-security/certificates/d1b603c3.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
d1b603c3.0"... ok

Checking CA file /etc/grid-security/certificates/51a418bb.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
51a418bb.0"... ok


[EMAIL PROTECTED] ~]$ grid-proxy-init

Your identity: /O=Grid/OU=GlobusTest/OU=simpleCA- 
grid2.ramscommunity.org/OU=ramscommunity.org/CN=Yoichi Takayama

Enter GRID pass phrase for this identity:

Creating  
proxy 
 ..................................................................  
Done

Your proxy is valid until: Fri Oct 31 03:37:04 2008


[EMAIL PROTECTED] ~]$ grid-cert-diagnostics

Checking Environment Variables
==============================
Checking if X509_CERT_DIR is set... no
Checking if X509_USER_CERT is set... no
Checking if X509_USER_KEY is set... no
Checking if X509_USER_PROXY is set... no

Checking Security Directories
=======================
Determining trusted cert path... /etc/grid-security/certificates
Checking for cog.properties... found
  WARNING: If the cog.properties file contains security properties,

           Java apps will ignore the security paths described in  
the GSI

           documentation

Checking trusted certificates...
================================
Getting trusted certificate list...
Checking CA file /etc/grid-security/certificates/1c3f2ca8.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
1c3f2ca8.0"... ok

Checking CA file /etc/grid-security/certificates/d1b603c3.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
d1b603c3.0"... ok

Checking CA file /etc/grid-security/certificates/51a418bb.0... ok

Verifying certificate chain for "/etc/grid-security/certificates/ 
51a418bb.0"... ok





(from the previous actions, both servers have valid grid-proxy  
credentials)



I meant that because I had to try globus-url-copy on both servers  
before, as you asked, I had already used grid-proxy-init on both  
servers at this point. So, to try globus-job-run on both servers  
then, the credentials were still valid on both servers.




[EMAIL PROTECTED] .globus]$ /usr/bin/env (same as /bin/env)

[EMAIL PROTECTED] ~]$ ls -l /bin/env
-rwxr-xr-x 1 root root 18284 May 25 01:19 /bin/env
[EMAIL PROTECTED] ~]$ ls -l /usr/bin/env
lrwxrwxrwx 1 root root 13 Jun 28 07:05 /usr/bin/env -> ../../bin/env

MANPATH=/usr/local/pegasus/2.0.2/man
HOSTNAME=grid1.ramscommunity.org
SHELL=/bin/bash
TERM=xterm-color
CATALINA_HOME=/usr/local/apache-tomcat-6.0.18
HISTSIZE=1000
GLOBUS_PATH=/usr/local/globus
GLOBUS_LOCATION=/usr/local/globus
PERL5LIB=/usr/local/pegasus/2.0.2/lib/perl
ANT_HOME=/usr/local/apache-ant-1.7.1
USER=yoichi
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:
LD_LIBRARY_PATH=/usr/local/globus/lib
LIBPATH=/usr/local/globus/lib:/usr/lib:/lib
MAIL=/var/spool/mail/yoichi

PATH=/usr/kerberos/bin:/usr/local/pegasus/2.0.2/bin:/usr/local/ 
globus/bin:/usr/local/globus/sbin:/nfs/software/condor/7.0.4/bin:/ 
nfs/software/condor/7.0.4/sbin:/usr/local/bin:/bin:/usr/bin:/usr/ 
java/jdk1.6.0_07/bin:/usr/local/apache-ant-1.7.1/bin:/nfs/software/ 
montage/bin:/home/yoichi/bin

CONDOR_LOCATION=/nfs/software/condor/7.0.4
CONDOR_CONFIG=/nfs/software/condor/7.0.4/etc/condor_config
INPUTRC=/etc/inputrc
PWD=/home/yoichi/.globus
JAVA_HOME=/usr/java/jdk1.6.0_07
LANG=en_US.UTF-8
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SHLVL=1
HOME=/home/yoichi
GLOBUS_TCP_PORT_RANGE=40000,41000
DYLD_LIBRARY_PATH=/usr/local/globus/lib
LOGNAME=yoichi

CLASSPATH=/usr/local/pegasus/2.0.2/lib/xmlParserAPIs.jar:/usr/local/ 
pegasus/2.0.2/lib/cryptix-asn1.jar:/usr/local/pegasus/2.0.2/lib/ 
mysql-connector-java-5.0.5-bin.jar:/usr/local/pegasus/2.0.2/lib/ 
preservcsl.jar:/usr/local/pegasus/2.0.2/lib/java-getopt-1.0.9.jar:/ 
usr/local/pegasus/2.0.2/lib/postgresql-8.1dev-400.jdbc3.jar:/usr/ 
local/pegasus/2.0.2/lib/puretls.jar:/usr/local/pegasus/2.0.2/lib/ 
cryptix32.jar:/usr/local/pegasus/2.0.2/lib/exist.jar:/usr/local/ 
pegasus/2.0.2/lib/commons-logging.jar:/usr/local/pegasus/2.0.2/lib/ 
xmldb.jar:/usr/local/pegasus/2.0.2/lib/jce-jdk13-125.jar:/usr/local/ 
pegasus/2.0.2/lib/pegasus.jar:/usr/local/pegasus/2.0.2/lib/ 
log4j-1.2.8.jar:/usr/local/pegasus/2.0.2/lib/xmlrpc.jar:/usr/local/ 
pegasus/2.0.2/lib/accessors.jar:/usr/local/pegasus/2.0.2/lib/ 
commons-pool.jar:/usr/local/pegasus/2.0.2/lib/cog-jglobus.jar:/usr/ 
local/pegasus/2.0.2/lib/xercesImpl.jar:/usr/local/pegasus/2.0.2/lib/ 
globus_rls_client.jar:/usr/local/pegasus/2.0.2/lib/jakarta-oro.jar:/ 
usr/local/pegasus/2.0.2/lib/exist-optional.jar:/usr/local/pegasus/ 
2.0.2/lib/junit.jar:/usr/local/pegasus/2.0.2/lib/cryptix.jar:/usr/ 
local/pegasus/2.0.2/lib/resolver.jar:/usr/local/pegasus/2.0.2/lib/ 
wings.jar

LESSOPEN=|/usr/bin/lesspipe.sh %s
SHLIB_PATH=/usr/local/globus/lib
G_BROKEN_FILENAMES=1
PEGASUS_HOME=/usr/local/pegasus/2.0.2
MONTAGE_LOCATION=/nfs/software/montage
_=/usr/bin/env
OLDPWD=/home/yoichi


[EMAIL PROTECTED] ~]$ env
HOSTNAME=grid2.ramscommunity.org
SHELL=/bin/bash
TERM=xterm-color
HISTSIZE=1000
GLOBUS_PATH=/usr/local/globus
GLOBUS_LOCATION=/usr/local/globus
ANT_HOME=/usr/local/apache-ant-1.7.1
USER=yoichi
LS_COLORS=no=00:fi=00:di=01;34:ln=01;36:pi=40;33:so=01;35:bd=40;33;01:cd=40;33;01:or=01;05;37;41:mi=01;05;37;41:ex=01;32:*.cmd=01;32:*.exe=01;32:*.com=01;32:*.btm=01;32:*.bat=01;32:*.sh=01;32:*.csh=01;32:*.tar=01;31:*.tgz=01;31:*.arj=01;31:*.taz=01;31:*.lzh=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.gz=01;31:*.bz2=01;31:*.bz=01;31:*.tz=01;31:*.rpm=01;31:*.cpio=01;31:*.jpg=01;35:*.gif=01;35:*.bmp=01;35:*.xbm=01;35:*.xpm=01;35:*.png=01;35:*.tif=01;35:
LD_LIBRARY_PATH=/usr/local/globus/lib
LIBPATH=/usr/local/globus/lib:/usr/lib:/lib
MAIL=/var/spool/mail/yoichi

PATH=/usr/kerberos/bin:/usr/local/globus/bin:/usr/local/globus/ 
sbin:/nfs/software/condor/7.0.4/bin:/nfs/software/condor/7.0.4/ 
sbin:/usr/local/bin:/bin:/usr/bin:/usr/java/jdk1.6.0_07/bin:/usr/ 
local/apache-ant-1.7.1/bin:/home/yoichi/bin

CONDOR_LOCATION=/nfs/software/condor/7.0.4
CONDOR_CONFIG=/nfs/software/condor/7.0.4/etc/condor_config
INPUTRC=/etc/inputrc
PWD=/home/yoichi
JAVA_HOME=/usr/java/jdk1.6.0_07
LANG=en_US.UTF-8
SSH_ASKPASS=/usr/libexec/openssh/gnome-ssh-askpass
SHLVL=1
HOME=/home/yoichi
GLOBUS_TCP_PORT_RANGE=40000,41000
DYLD_LIBRARY_PATH=/usr/local/globus/lib
LOGNAME=yoichi
LESSOPEN=|/usr/bin/lesspipe.sh %s
SHLIB_PATH=/usr/local/globus/lib
G_BROKEN_FILENAMES=1
_=/bin/env


(Is this correct?? Is the server address correct?)


[EMAIL PROTECTED] ~]$ globus-job-run grid2.ramscommunity.org/jobmanager- 
fork "/bin/env > env.out"
GRAM Job submission failed because data transfer to the server  
failed (error code 10)

[EMAIL PROTECTED] ~]$ sudo locate env.out
[EMAIL PROTECTED] ~]$

(does not find it on grid1)

[EMAIL PROTECTED] ~]$ sudo locate env.out
[EMAIL PROTECTED] ~]$

(does not find it on grid2, either)

[EMAIL PROTECTED] ~]# locate env.out
[EMAIL PROTECTED] ~]#

(it is not on grid4, either)

(from the log, I can't tell where it is. If the intermediate  
results was save on /home/yoichi/.globus/job/ 
grid2.ramscommunity.org/ somewhere, the temporary directory may  
have been already wiped out).


[EMAIL PROTECTED] ~]$ cat gram_job_mgr_20617.log
10/30 16:00:06 JM: TARGET_GLOBUS_LOCATION = /usr/local/globus
10/30 16:00:06 JM: Security context imported

10/30 16:00:06 JM: Adding new callback contact (url=https://grid1.ramscommunity.org:40002/ 
, mask=1048575)

10/30 16:00:06 JM: Added successfully

10/30 16:00:06 Pre-parsed RSL string: &("rsl_substitution" =  
("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001"; ) ) 
("stderr" = $("GLOBUSRUN_GASS_URL") # "/dev/stderr" )("stdout" = $ 
("GLOBUSRUN_GASS_URL") # "/dev/stdout" )("executable" = "/bin/env >  
env.out" )

10/30 16:00:06
<<<<<Job Request RSL

&("rsl_substitution" = ("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001 
" ) )("stderr" = $("GLOBUSRUN_GASS_URL") # "/dev/stderr" )("stdout"  
= $("GLOBUSRUN_GASS_URL") # "/dev/stdout" )("executable" = "/bin/ 
env > env.out" )

>>>>>Job Request RSL
10/30 16:00:06
<<<<<Job Request RSL (canonical)

&("rslsubstitution" = ("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001 
" ) )("stderr" = $("GLOBUSRUN_GASS_URL") # "/dev/stderr" )("stdout"  
= $("GLOBUSRUN_GASS_URL") # "/dev/stdout" )("executable" = "/bin/ 
env > env.out" )

>>>>>Job Request RSL (canonical)

10/30 16:00:06 JM: Evaluating RSL Value10/30 16:00:06 JM: Evaluated  
RSL Value to GLOBUSRUN_GASS_URL10/30 16:00:06 JM: Evaluating RSL  
Value10/30 16:00:06 JM: Evaluated RSL Value to https://grid1.ramscommunity.org:4000110/30 
 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_MAKE_SCRATCHDIR

10/30 16:00:06
<<<<<Job RSL

&("environment" = ("HOME" "/home/yoichi" ) ("LOGNAME" "yoichi" ) ) 
("rslsubstitution" = ("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001 
" ) )("stderr" = $("GLOBUSRUN_GASS_URL") # "/dev/stderr" )("stdout"  
= $("GLOBUSRUN_GASS_URL") # "/dev/stdout" )("executable" = "/bin/ 
env > env.out" )

>>>>>Job RSL
10/30 16:00:06
<<<<<Job RSL (post-eval)

&("environment" = ("HOME" "/home/yoichi" ) ("LOGNAME" "yoichi" ) ) 
("rslsubstitution" = ("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001 
" ) )("stderr" = "https://grid1.ramscommunity.org:40001/dev/ 
stderr" )("stdout" = "https://grid1.ramscommunity.org:40001/dev/stdout 
" )("executable" = "/bin/env > env.out" )

>>>>>Job RSL (post-eval)
Adding default RSL of proxy_timeout = 60
Adding default RSL of dry_run = no
Adding default RSL of gram_my_job = collective
Adding default RSL of job_type = multiple
Adding default RSL of count = 1
Adding default RSL of stdin = /dev/null
Adding default RSL of directory = $(HOME)
10/30 16:00:06
<<<<<Job RSL (post-validation)

&("directory" = $("HOME") )("stdin" = "/dev/null" )("count" = "1" ) 
("job_type" = "multiple" )("gram_my_job" = "collective" )("dry_run"  
= "no" )("proxy_timeout" = "60" )("environment" = ("HOME" "/home/ 
yoichi" ) ("LOGNAME" "yoichi" ) )("rslsubstitution" =  
("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001"; ) ) 
("stderr" = "https://grid1.ramscommunity.org:40001/dev/stderr"; ) 
("stdout" = "https://grid1.ramscommunity.org:40001/dev/stdout"; ) 
("executable" = "/bin/env > env.out" )

>>>>>Job RSL (post-validation)
10/30 16:00:06
<<<<<Job RSL (post-validation-eval)

&("directory" = "/home/yoichi" )("stdin" = "/dev/null" )("count" =  
"1" )("job_type" = "multiple" )("gram_my_job" = "collective" ) 
("dry_run" = "no" )("proxy_timeout" = "60" )("environment" =  
("HOME" "/home/yoichi" ) ("LOGNAME" "yoichi" ) )("rslsubstitution"  
= ("GLOBUSRUN_GASS_URL" "https://grid1.ramscommunity.org:40001"; ) ) 
("stderr" = "https://grid1.ramscommunity.org:40001/dev/stderr"; ) 
("stdout" = "https://grid1.ramscommunity.org:40001/dev/stdout"; ) 
("executable" = "/bin/env > env.out" )

>>>>>Job RSL (post-validation-eval)
10/30 16:00:06 JMI: Getting RSL output value
10/30 16:00:06 JMI: Processing output positions
10/30 16:00:06 JMI: Getting RSL output value
10/30 16:00:06 JMI: Processing output positions

10/30 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_REMOTE_IO_FILE_CREATE

10/30 16:00:06 JM: Opening output destinations

10/30 16:00:06 JM: stdout goes to /home/yoichi/.globus/job/ 
grid2.ramscommunity.org/20617.1225342806/stdout
10/30 16:00:06 JM: stderr goes to /home/yoichi/.globus/job/ 
grid2.ramscommunity.org/20617.1225342806/stderr

10/30 16:00:06 JM: Opening https://grid1.ramscommunity.org:40001/dev/stdout
10/30 16:00:06 JM: Opened GASS handle 1.

10/30 16:00:06 JM: exiting  
globus_l_gram_job_manager_output_destination_open()

10/30 16:00:06 JM: Opening https://grid1.ramscommunity.org:40001/dev/stderr
10/30 16:00:06 JM: Opened GASS handle 2.

10/30 16:00:06 JM: exiting  
globus_l_gram_job_manager_output_destination_open()

10/30 16:00:06 stdout or stderr is being used, starting to poll
10/30 16:00:06 JM: Finished opening output destinations

10/30 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_OPEN_OUTPUT

10/30 16:00:06 JM: GSSAPI type is GSI.. relocating proxy

10/30 16:00:06 JMI: testing job manager scripts for type fork exist  
and permissions are ok.
10/30 16:00:06 JMI: completed script validation: job manager type  
is fork.
10/30 16:00:06 JMI: in  
globus_gram_job_manager_script_proxy_relocate()

10/30 16:00:06 JMI: cmd = proxy_relocate
Thu Oct 30 16:00:06 2008 JM_SCRIPT: New Perl JobManager created.

Thu Oct 30 16:00:06 2008 JM_SCRIPT: Using jm supplied job dir: / 
home/yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806

Thu Oct 30 16:00:06 2008 JM_SCRIPT: proxy_relocate(enter)

10/30 16:00:06 JMI: while return_buf = GRAM_SCRIPT_X509_USER_PROXY  
= /home/yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806/ 
x509_up
10/30 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_PROXY_RELOCATE
10/30 16:00:06 JM: Relocated Proxy to /home/yoichi/.globus/job/ 
grid2.ramscommunity.org/20617.1225342806/x509_up

10/30 16:00:06 JM: before sending to client: rc=0 (Success)

10/30 16:00:06 Job Manager State Machine (exiting):  
GLOBUS_GRAM_JOB_MANAGER_STATE_TWO_PHASE
10/30 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_TWO_PHASE
10/30 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_TWO_PHASE_COMMITTED
10/30 16:00:06 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_STAGE_IN
10/30 16:00:06 JMI: testing job manager scripts for type fork exist  
and permissions are ok.
10/30 16:00:06 JMI: completed script validation: job manager type  
is fork.

10/30 16:00:06 JMI: in globus_gram_job_manager_submit()

10/30 16:00:06 JMI: local stdout filename = /home/yoichi/.globus/ 
job/grid2.ramscommunity.org/20617.1225342806/stdout.
10/30 16:00:06 JMI: local stderr filename = /home/yoichi/.globus/ 
job/grid2.ramscommunity.org/20617.1225342806/stderr.

10/30 16:00:06 JMI: cmd = submit
10/30 16:00:06 JMI: returning with success
Thu Oct 30 16:00:07 2008 JM_SCRIPT: New Perl JobManager created.

Thu Oct 30 16:00:07 2008 JM_SCRIPT: Using jm supplied job dir: / 
home/yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806

10/30 16:00:07 JMI: while return_buf = GRAM_SCRIPT_ERROR = 5

10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_SUBMIT

10/30 16:00:07 JM: in globus_gram_job_manager_reporting_file_create()
10/30 16:00:07 JM: not reporting job information
10/30 16:00:07 JM: in globus_gram_job_manager_history_file_create()

10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED

10/30 16:00:07 closing destination 
https://grid1.ramscommunity.org:40001/dev/stdout

10/30 16:00:07 JM: exiting  
globus_l_gram_job_manager_output_destination_close()

10/30 16:00:07 closing destination 
https://grid1.ramscommunity.org:40001/dev/stderr

10/30 16:00:07 JM: exiting  
globus_l_gram_job_manager_output_destination_close()
10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_CLOSE_OUTPUT

10/30 16:00:07 JM: NOT empty client callback list.

10/30 16:00:07 JM: sending callback of status 4 (failure code 5) to https://grid1.ramscommunity.org:40002/ 
.
10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_TWO_PHASE
10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_TWO_PHASE_COMMITTED
10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_FILE_CLEAN_UP
10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_SCRATCH_CLEAN_UP
10/30 16:00:07 JMI: testing job manager scripts for type fork exist  
and permissions are ok.
10/30 16:00:07 JMI: completed script validation: job manager type  
is fork.

10/30 16:00:07 JMI: cmd = cache_cleanup
Thu Oct 30 16:00:07 2008 JM_SCRIPT: New Perl JobManager created.

Thu Oct 30 16:00:07 2008 JM_SCRIPT: Using jm supplied job dir: / 
home/yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806
Thu Oct 30 16:00:07 2008 JM_SCRIPT: Using jm supplied job dir: / 
home/yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806

Thu Oct 30 16:00:07 2008 JM_SCRIPT: cache_cleanup(enter)

Thu Oct 30 16:00:07 2008 JM_SCRIPT: Cleaning files in job dir /home/ 
yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806
Thu Oct 30 16:00:07 2008 JM_SCRIPT: Removed 4 files from /home/ 
yoichi/.globus/job/grid2.ramscommunity.org/20617.1225342806

Thu Oct 30 16:00:07 2008 JM_SCRIPT: cache_cleanup(exit)

10/30 16:00:07 Job Manager State Machine (entering):  
GLOBUS_GRAM_JOB_MANAGER_STATE_FAILED_CACHE_CLEAN_UP

10/30 16:00:07 JM: in globus_gram_job_manager_reporting_file_remove()
10/30 16:00:07 JM: exiting globus_gram_job_manager.

--------------------------------------------------------------------------
Yoichi Takayama, PhD
Senior Research Fellow
RAMP Project
MELCOE (Macquarie E-Learning Centre of Excellence)
MACQUARIE UNIVERSITY

Phone: +61 (0)2 9850 9073
Fax: +61 (0)2 9850 6527
www.mq.edu.au
www.melcoe.mq.edu.au/projects/RAMP/
--------------------------------------------------------------------------
MACQUARIE UNIVERSITY: CRICOS Provider No 00002J


This message is intended for the addressee named and may contain  
confidential information.  If you are not the intended recipient,  
please delete it and notify the sender. Views expressed in this  
message are those of the individual sender, and are not necessarily  
the views of Macquarie E-Learning Centre Of Excellence (MELCOE) or  
Macquarie University.


On 30/10/2008, at 6:21 AM, Charles Bacon wrote:


On Oct 28, 2008, at 7:58 PM, Yoichi Takayama wrote:


[EMAIL PROTECTED] ~]# su - yoichi
[EMAIL PROTECTED] ~]$ myproxy-logon -s grid2
Enter MyProxy pass phrase:
A credential has been received for user yoichi in /tmp/x509up_u500.
[EMAIL PROTECTED] ~]$ globus-gass-server -r -w -p 40001
Error: Failed to initialize gass server library

(my-proxy credential does not seem to work.)



Wait, what?  What's the output of grid-cert-diagnostics if you  
have a myproxy cred instead of a g-p-i cred?



(I have set up the local certificate files in ~yoichi/.globus  
when I tried the grid-proxy before)



Umm ... are there still certificates in there?  Are there also  
certificates in /etc/grid-security/certificates?  It's cleaner if  
you can do things entirely at the systems level and not in your  
~/.globus directory.  Confusing security mixups can happen,  
especially if they're not all sharing home directories.



(succeeded)


Well, so much for that theory.


(from the previous actions, both servers have valid grid-proxy  
credentials)



I'm not sure what you mean from previous actions and proxy creds;  
aren't the gatekeepers running on /etc/grid-security/hostcert/ 
key.pem?



Anyway, let's see grid-cert-diagnostics from both grid1 and grid2  
and see if there's anything funny going on.  I'd also like to see  
the results of /usr/bin/env from your submission to jobmanager- 
fork.  Because you can't get the output files back, just submit a  
shell script or something that runs /usr/bin/env > env.out, then  
send that.



Charles









Attachment:
smime.p7s

Description: S/MIME cryptographic signature






















					Reply via email to