Print

Print


Douglas McNab wrote:

> We were also noticing a  'cannot download .BrokerInfo from' error.  Once 
> we tracked what was wrong we noticed that the job was running using our 
> specified EDG_WL_SCRATCH of /tmp but not adding a wms job string 
> directory so it tried to run the job directly from /tmp.  This caused 
> problems when there were multiple WMS jobs on a node when it tried to 
> globus-url-copy and got a Permission Denied.
> 
> It looks like the latest WMS upgrade to the job wrapper has removed the 
> following:
> 
> #if [ ${__job_type} -eq 0 -o ${__job_type} -eq 3 ]; then # normal or 
> interactive
>   newdir="${__jobid_to_filename}"
>   mkdir ${newdir}
>   cd ${newdir}
> #elif [ ${__job_type} -eq 1 -o ${__job_type} -eq 2 ]; then # MPI (LSF or 
> PBS)
> #fi

No, that code is still there.  Taken from an example job wrapper:

-----------------------------------------------------------------------------------
[...]
__jobid_to_filename="https_3a_2f_2fgswms01.cern.ch_3a9000_2faxltvyYyqlycG6j-S3i8fw"
[...]
jw_newdir="${__jobid_to_filename}"
[...]
if [ ${__job_type} -eq 1 -o ${__job_type} -eq 2 ]; then
   # MPI (LSF or PBS)
   mkdir -p .mpi/${jw_newdir}
   if [ $? != 0 ]; then
     fatal_error "Cannot create .mpi/${jw_newdir} directory"
   fi
   cd .mpi/${jw_newdir}
else #if [ ${__job_type} -eq 0 -o ${__job_type} -eq 3 ]; then
   mkdir ${jw_newdir}
   if [ $? != 0 ]; then
     fatal_error "Cannot create ${jw_newdir} directory"
   fi
   cd ${jw_newdir}
fi
jw_workdir="`pwd`"
[...]
-----------------------------------------------------------------------------------

If you see evidence to the contrary, the used WMS would be misconfigured.