Hi Gonçalo,
> There are a lot of SAM jobs failing with:
>
> ---*---
>
> + glite-wms-job-submit -a --vo ops -o testjob.jid testjob.jdl
> Warning - --vo option ignored
> Connecting to the service
> https://wms201.cern.ch:7443/glite_wms_wmproxy_server
> error: globus_ftp_client: the server responded with an error
> 421 Service not available, closing control connection
> Error - The job has been successfully registered (the JobId is:
> https://wms201.cern.ch:9000/GgW3ocae14xNQzIBWAaHgA), but an error
> occurred while transferring files:
> The following error(s) occured while transferring the ISB file(s):
> - /tmp/ISBfiles_3r50xwY0tjIW3fCMcxED_w_0.tar.gz
> to:
> gsiftp://wms201.cern.ch:2811/var/glite/SandboxDir/Gg/https_3a_2f_2fwms201.cern.ch_3a9000_2fGgW3ocae14xNQzIBWAaHgA/input/ISBfiles_3r50xwY0tjIW3fCMcxED_w_0.tar.gz
> - ErrorCode: 256
> Unknown error 256
> To complete the operation, the following InputSandbox files need to be
> transferred:
> ==========================================================================================================
>
> InputSandbox file : /tmp/ISBfiles_3r50xwY0tjIW3fCMcxED_w_0.tar.gz
> Destination :
> gsiftp://wms201.cern.ch:2811/var/glite/SandboxDir/Gg/https_3a_2f_2fwms201.cern.ch_3a9000_2fGgW3ocae14xNQzIBWAaHgA/input/ISBfiles_3r50xwY0tjIW3fCMcxED_w_0.tar.gz
>
> -----------------------------------------------------------------------------
>
> then start the job by issuing a submissiong with the option:
> --start https://wms201.cern.ch:9000/GgW3ocae14xNQzIBWAaHgA
> + set +x
> Job submission failed! Check the Resource Broker
>
> ---*---
>
> Can you please check?
Note: as far as SAM is concerned, those jobs do not count,
so your availability is not affected.
But yes, we will look into why wms201 often refuses jobs with
such GridFTP complaints. The machine is more highly loaded
since a few days, which coincided with the rise of such errors:
http://wmsmon.cern.ch/monitoring/monitoring.html
|