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

[condor-users] Flocking problems

I have a two condor pools and would like to allow each pool equal access to the other's resources. One pool consists of a 16 machines in the 192.168.0 name space (let's call this pool A). The 16 machines are attached to a central manager that is open to the world. All the nodes in the other pool (say pool B) are visible to the world. I've configured both pools to using the FLOCK_TO/FLOCK_FROM config flags but still I'm having some problems.

Jobs are submitted from pool B will only execute on the World node of pool A. It looks like jobs match to the internal node but then the jobs are not allowed to execute. The state regular changes from Unclaimed to Matched, as indicated in the log file snippet below. Does this have anything to do with the fact that pool A's nodes are mostly private ips? Any help with this would be appreciated.


4/6 11:11:06 DaemonCore: Command received via UDP from host <>
4/6 11:11:06 DaemonCore: received command 440 (MATCH_INFO), calling handler (command_match_info)
4/6 11:11:06 vm1: match_info called
4/6 11:11:06 vm1: Received match <>#7165628803
4/6 11:11:06 vm1: State change: match notification protocol successful
4/6 11:11:06 vm1: Changing state: Unclaimed -> Matched
4/6 11:13:06 vm1: State change: match timed out
4/6 11:13:06 vm1: Changing state: Matched -> Owner
4/6 11:13:06 vm1: State change: IS_OWNER is false
4/6 11:13:06 vm1: Changing state: Owner -> Unclaimed


Jim Wilgenbusch

Computational Science & Information Technology
Florida State University
150-E Dirac Science Center Library
Tallahassee, Florida 32306-4120

Voice: 850.645.0307
Fax: 850.644.0098
Condor Support Information:
To Unsubscribe, send mail to majordomo@xxxxxxxxxxx with
unsubscribe condor-users <your_email_address>