[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Condor-users] Condor-G - condor_advertise


Using job-delegate tells me the problem is with the container on the remote site.
For some reason, the remote container did not handle the job delegation as expected.
I restarted the container and everything went smoothly.

Thannks so much!

PS: Is there a way to monitor the status of the condor pool real-time? Do we have
to run condor_status everytime we want to see the nodes' status?


From: Jaime Frey <jfrey@xxxxxxxxxxx>
Reply-To: Condor-Users Mail List <condor-users@xxxxxxxxxxx>
To: Condor-Users Mail List <condor-users@xxxxxxxxxxx>
Subject: Re: [Condor-users] Condor-G - condor_advertise
Date: Thu, 8 Sep 2005 11:01:03 -0500

On Sep 8, 2005, at 8:39 AM, duane waktu wrote:

Do you get the same error if you don't use matchmaking (i.e. specify the gatekeeper url directly in the submit file)?

Yes, specifying the remote gatekeeper directly in the submit file gives me the same error:

OK. That means the problem has nothing to do with matchmaking. Next, let's find out if the problem is related to Condor-G. Try submitting a job to the same machine with globusrun-ws using the -job-delegate option.

|            Jaime Frey            |  Public Split on Whether        |
|        jfrey@xxxxxxxxxxx         |  Bush Is a Divider              |
|  http://www.cs.wisc.edu/~jfrey/  |         -- CNN Scrolling Banner |

_______________________________________________ Condor-users mailing list Condor-users@xxxxxxxxxxx https://lists.cs.wisc.edu/mailman/listinfo/condor-users

Is your PC infected? Get a FREE online computer virus scan from McAfee® Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963