[Condor-users] condor-g: socket timeout question

[Jim Davies <jim@xxxxxxxxxxxxxx>]

Hi,

I'd be grateful for some help getting condor-g to work:

I've installed and configured GT4 to run on two FC4 servers such that  
I can submit a job from one to the other using globusrun-ws (a.rsl  
from the quick start quide).

######################################################
...
Proxy Verify OK
Your proxy is valid until: Wed Jun 20 22:38:58 2007
[jim@fc4a] globusrun-ws -submit -S -f a.rsl
Delegating user credentials...Done.
Job ID: uid:17df88bc-1f12-11dc-82ea-000c29de8f37
Termination time: 06/21/2007 09:39 GMT
Current job state: StageIn
Current job state: Active
Current job state: CleanUp
Current job state: Done
Destroying job...Done.
Cleaning up any delegated credentials...Done.
######################################################

I have since installed Condor, but when I run condor_submit using the  
following submit content, I get a socket timeout error.

test.sub
######################################################
executable=/bin/date
transfer_executable=false
universe=GLOBUS
grid_resource= gt4  
https://fc4a.testclust:8443/wsrf/services/ManagedJobFactoryService  
Condor
output=test.out
log=test.log
queue
######################################################

The text logged is pre-fixed 'Globus error:', but globusrun-ws runs OK.


"Globus error: java.net.SocketTimeoutException: Read timed out
 Code 0 Subcode 0"


Any ideas?

Jim

Globus version 4.0.4
Condor version 6.8.5
OS: LINUX FC4