next up previous contents
Next: Temporary LB Failures Up: JOB Error Messages Previous: Cannot retrieve output (UI_DIR_NOT_FOUND)   Contents

Getting debug help

In case of strange problem, you can use the --debug option and check the debug output to understand the problem and try a solution. An example of debug output is given below.

$ edg-job-list-match --debug simple.jdl

#### Debug Message #### - Vo file loaded:
/opt/edg/etc/atlas/edg_wl_ui.conf
 [
  LBAddresses = "boszwijn.nikhef.nl:9000";
  VirtualOrganisation = "atlas";
  NSAddresses = "boszwijn.nikhef.nl:7772"
 ]
#### End Debug ####
#### Debug API #### - The function 'NS::init' has been calledr
 with the following parameter(s):
>> boszwijn.nikhef.nl
>> 7772
>> 0
#### End Debug ####
#### Debug API #### - The function 'NS::ns_match' has been called with the following parameter(s):
>> [ requirements = ( other.GlueCEStateStatus == "Production" ); 
   RetryCount = 3; JobType = "normal"; Executable = "simple.sh";
   StdOutput = "simple.out"; OutputSandbox = { "simple.out","simple.err" };
   VirtualOrganisation = "atlas";
   rank =  -other.GlueCEStateEstimatedResponseTime;
   Type = "job"; StdError = "simple.err";
   DefaultRank =  -other.GlueCEStateEstimatedResponseTime;
   InputSandbox = { "/home/userx/edg2/myjobs/simple.sh" } ]
#### End Debug ####
Connecting to host boszwijn.nikhef.nl, port 7772
===================== edg-job-list-match failure ======================
 No Computing Element matching your job requirements has been found!
 Try again modifying your job description file.
======================================================================
                           *** Log file created ***
Possible Errors and Debug messages have been printed in the following file:
/tmp/edg-job-list-match_10009_7022_1066032488.log



luvisetto 2003-12-17