[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: [Condor-users]Can no longer talk to condor_starter
- Date: Tue, 9 Aug 2005 09:47:50 +1000
- From: "Philip Crawford" <p.crawford@xxxxxxxxxxx>
- Subject: RE: [Condor-users]Can no longer talk to condor_starter
I'm also having this problem on a new batch of systems which I recently
installed using 6.6.10 on Windows XP SP2. They have Windows Firewall on,
Condor is showing up in the exceptions list on Windows Firewall, I have set
the connector to use TCP on the whole pool, (about 20 systems all up, with
11 being either DP (1 system) or hyperthreading with 2 vm's ).
I've set the TCP connection cache to 100 on all systems after reading the
UPDATE_COLLECTOR_WITH_TCP = True
COLLECTOR_SOCKET_CACHE_SIZE = 100
>From the way I understand the manual this should be sufficient.
The working systems are all P4's, the new systems are Celerons. I'm
submitting from a P4. Should this make a difference on Architecture?
Any help with this would be appreciated.
[mailto:condor-users-bounces@xxxxxxxxxxx] On Behalf Of XXXXXX
Sent: Friday, 5 August 2005 10:35 PM
Subject: [Condor-users]Can no longer talk to condor_starter
I found that sometimes the job i submited didn't be executed,although some
machines' state are Unclaimed.Then i check the log file of job.it show me
07 (001.000.000) 08/02 23:13:39 Shadow exception!
Can no longer talk to condor_starter on execute machine
0 - Run Bytes Sent By Job
0 - Run Bytes Received By Job
What's the matter with my pool?
How can i deal with this problem?
Condor-users mailing list