[Condor-users] Issue with connecting nodes to pool/master

[<Robert.Wright@xxxxxxxxx>]

Title: Issue with connecting nodes to pool/master

Ladies/Gentlemen,

Preface the below with the fact that I am new to the condor community and
to the program it self.

So like any good newb I had a home project in mind and found condor.. Now I
have two projects. The original and the installation and config of condor
;)

So I have the master up and running, it runs the test scripts which my
machine supports and all is well. However, when I attempt to join a node
(192.168.1.101) to the master (192.168.1.102) both condor_status scripts
hang. Reviewing the logs only shows an entry on the node and not the
master. Yet both are effected. If I stop the node's condor_status, the
master's status script responds correctly.

6/19 08:08:40 ---------- Started Negotiation Cycle ----------
6/19 08:08:40 Phase 1:  Obtaining ads from collector ...
6/19 08:08:40   Getting all public ads ...
6/19 08:08:40 Can't connect to <192.168.1.102:9618>:0, errno = 113
6/19 08:08:40 Will keep trying for 10 seconds...
6/19 08:08:50 Connect failed for 10 seconds; returning FALSE
6/19 08:08:50 Couldn't fetch ads: communication error
6/19 08:08:50 Aborting negotiation cycle

I did a quick cat/grep against all the log files on the master and nothing
is being logged pertaining to 101's attempted connection.

Master (.102) hosts.allow is set to ALL:192.168.1.101, so to my knowledge
this should not be an issue. I am assuming that I have overlooked a config
in which I must spec out which machine is allowed to join? the closet
thing I found was flocking... and while I do not believe this is right I
did try and play around with that.

Any help or a finger pointing in the right direction would be greatly
appreciated.

-Bob