[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Condor-users] No error details in Stork log
- Date: Fri, 09 Jun 2006 22:28:55 +0200
- From: Lamine AOUAD <aouad@xxxxxxx>
- Subject: Re: [Condor-users] No error details in Stork log
Jeff Weber a écrit:
Sometimes Stork does not capture the module error into the error code.
This is a known bug. Two items to look at:
1) does running the Stork module by hand from the command line, with the
same environment seen by the stork_server succeed:
# stork.transfer.gsiftp-file gsiftp://gdx0082/tmp/A_01 file:/tmp/A_01
Yes the stork modules succeed from the command line..
These two files are empty, I only have the message "Job attempt 'Number'
exited by signal 11" in the log file..
What does this status indicate (11) ? The StorkLog file is similar to
that of my previous email..
2) The error seen by stork when running the module will be saved to the
job stdout and stderr files. Ensure your stork submit file has these
output = /path/to/job/stdout/file
err = /path/to/job/stderr/file
And examine those files after the job runs.
On Fri, 2006-06-09 at 00:41 +0200, Lamine AOUAD wrote:
I have trouble with stork_submit.. There is no error in the error_code
from stork_status (error_code = "";)..
globus-url-copy and stork.transfer.xxx-xxx work well from the command line..