[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [condor-users] globus -> condor matching problem
- Date: Wed, 29 Oct 2003 08:34:20 -0600
- From: Dan Bradley <dan@xxxxxxxxxxxx>
- Subject: Re: [condor-users] globus -> condor matching problem
Mark Calleja wrote:
WARNING: Be advised:
No resources matched request's constraints
Check the Requirements expression below:
Requirements = (OpSys == "LINUX" && Arch == "INTEL") && (Disk >=
DiskUsage) && ((Memory * 1024) >= ImageSize) && (FileSystemDomain ==
Looks like the FileSystemDomain requirement is the source of trouble here.
Make sure condor_config and the gatekeeper machine's local condor config
file have FILESYSTEM_DOMAIN configured correctly. for example, you
probably want it set to "esc.cam.ac.uk" instead of the full host name.
If your condor_config is not in a standard location, then make sure the
gatekeeper is being invoked with the environment variable CONDOR_CONFIG
correctly set up.
For example, in xinetd.d/globus-gatekeeper, you might need to insert a
line such as the following:
env += CONDOR_CONFIG=/condor/etc/condor_config
Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>