Re: [gt-user] another globusrun-ws failure using fork jobmanager, GT4.0.5

[Adam Kocoloski]

Hi Martin,

On Aug 1, 2007, at 9:14 AM, [EMAIL PROTECTED] wrote:

Adam,
I think the problem in your case is the line
    eval "require $manager_class";
If require fails you'll enter the following if block and because
you did not specify a logfile the condition
if (defined($job_description) && defined($job_description->logfile()))
fails. This is fine but the failing require is not fine.

Please do the following for me:

1. Add a system debug statement before the eval statement
     system("echo $manager_class > /tmp/JOB_MANAGER_CLASS");
     eval "require $manager_class";

What's the content of /tmp/JOB_MANAGER_CLASS after a job submission?

Globus::GRAM::JobManager::fork

2. What are the permissions of
   $GLOBUS_LOCATION/lib/perl/Globus/GRAM/JobManager/*.pm

-rw-r--r-- 1 globus globus 13597 Jul 31 12:13 /usr/local/globus-4.0.5/ lib/perl/Globus/GRAM/JobManager/fork.pm

3. Write the following job description to a file "job.xml":
   <job>
     <executable>/bin/true</executable>
     <extensions>
       <logfile>/tmp/GT_SUBMISSION_PERL_LOG</logfile>
     </extensions>
   </job>
   and submit it using "globusrun-ws -submit -f job.xml"
   What's the content of /tmp/GT_SUBMISSION_PERL_LOG?

Adam

true lives in /usr/bin on Mac OS X, so I changed the path and submitted. The job failed and no logfile was generated. Regards,

smime.p7s
Description: S/MIME cryptographic signature