Hi, I can't reproduce your behavior here. To track this down:
* Does the same happen with jobs submitted to Fork instead of Condor? * If you look into the GT container logfile after the restart: - Do you see the jobs being recovered in the logfile? - Do you see the jobs finish in the container logfile? Martin ----- Original Message ----- From: [EMAIL PROTECTED] To: [email protected] Sent: Friday, June 13, 2008 8:42:13 PM GMT -06:00 US/Canada Central Subject: [gt-user] Testing Condor-G and GT4 Hi, I have a question about condor-G - GT Communication. Here is my scenario : I have 5 jobs that i submitted to Globus via Condor-G. When those jobs execute at Globus resource (Condor), I shutdown the Globus Container. The status of the jobs were : 473.0 tonny PENDING Condor blade3.bagong.grid /home/grid/mahasis 474.0 tonny PENDING Condor blade3.bagong.grid /home/grid/mahasis 475.0 tonny PENDING Condor blade3.bagong.grid /home/grid/mahasis 476.0 tonny ACTIVE Condor blade3.bagong.grid /home/grid/mahasis 477.0 tonny PENDING Condor blade3.bagong.grid /home/grid/mahasis and 60 seconds after that, Those job were succesfully executed. But I didn't started globus immediately. I started globus container after 120 seconds. At this condition what will Condor-G do ? In my case The Job status didn't changed, although Condor-G probes the globus to update those jobs status. Does Anybody know why this condition can happen ? Thanks Tonny
