747 2003-02-24 13:51 jobmanager replies success on failed requests 2003-03-10 11:11:30 1 1 1 Unclassified GRAM gt2 Gatekeeper/Jobmanager 1.6 All All RESOLVED FIXED P2 normal --- 1 jfrey@cs.wisc.edu smartin@mcs.anl.gov adesmet@cs.wisc.edu bester@mcs.anl.gov dangulo@cs.uchicago.edu pfc@cs.wisc.edu roy@cs.wisc.edu tannenba@cs.wisc.edu jfrey@cs.wisc.edu 2003-02-24 13:51:48 In our latest CMS testbed run, I found one (probably more, but I haven't looked at enough log files yet) jobmanager that failed to add stderr to the gass cache, but replied to the client (Condor-G) with error 110 (WAITING_TO_COMMIT), which is incorrect. Condor-G was then very confused when it couldn't commit the submission (because the jobmanager has exitted) and couldn't restart it (because the jobmanager has removed the job state file). I think the problem is in globus_l_gram_job_manager_reply() at globus_gram_job_manager_state.c:2144. The code sets failure_code to WAITING_TO_COMMIT if two-phase was requested, even if the request failed (over-writing the existing failure code). bester@mcs.anl.gov 2003-03-10 11:11:30 Update package at ftp://ftp.globus.org/pub/gt2/2.2/2.2.4/updates/src/globus_gram_job_manager-3.7.tar.gz resolves this problem. joe