Re: [Condor-users] SECMAN:2003:TCP connection failed

[Prashant Lal <lalp@xxxxxxxxxxx>]

hi 

Well it seems the installation is not proper either on the fedora or on the winxp because it is not able to connect to Master (fedora).

Just make sure while installing to the fedora u did it the way I am writing it down.

./condor_install (by root)

and then 

hit Enter for the first two questions

The third question will ask you whether your system has a File server installed. This is because Condor supports NFS and can use it to have a centralized network having all the release files installed at one time. So if you have your Condor user's home directory shared and mounted in all the machines with the same name, then you can go for a Network Installation else type "no" and hit Enter

Now just hit Enter unless you reach Step 8.

As this is the first machine, you should select the default value, which should be the name of the local machine. Else, for other machines you have to provide the full name of the Central Manager here. (But I recommend to use the complete name)

Now again hit Enter unless the installation is over. 

Note** ::::: This installation assumes that u r not using NFS.


If u have already has done the same way then perhaps I have never come across the problem you are facing .

cheers

PRashant Lal

On Thu, 2004-07-22 at 00:42, Guy Tel-Zur wrote:
> I installed Condor 6.6.5 on two nodes: on a Fedora core-2 as the central
> manager (is had a problem with MEMORY definition but the solution was found in
> the condor-users archive) and on Win-XP node. On the XP node I get the
> following errors:
>
> MasterLog:
> ==========
> 7/21 20:43:12 Can't send UPDATE_MASTER_AD to collector omer <192.168.1.2:9618>:
> Failed to send UDP update command to collector
> 7/21 20:44:07 DaemonCore: Command received via UDP from host
> <192.168.1.101:4595>
> 7/21 20:44:07 DaemonCore: received command 60001 (DC_PROCESSEXIT), calling
> handler (HandleProcessExitCommand())
> 7/21 20:44:07 Child 2892 died, but not a daemon -- Ignored
> 7/21 20:48:13 Can't connect to <192.168.1.2:9618>:0, errno = 10061
> 7/21 20:48:13 Will keep trying for 10 seconds...
> 7/21 20:48:22 Connect failed for 10 seconds; returning FALSE
> 7/21 20:48:22 ERROR:
> SECMAN:2003:TCP connection to <192.168.1.2:9618> failed
>
> Similar messages also in the SchedLog:
> ======================================
> 7/21 21:09:00 Can't connect to <192.168.1.2:9618>:0, errno = 10061
> 7/21 21:09:00 Will keep trying for 10 seconds...
> 7/21 21:09:10 Connect failed for 10 seconds; returning FALSE
> 7/21 21:09:10 ERROR:
> SECMAN:2003:TCP connection to <192.168.1.2:9618> failed
>
> I don't see any F/W complains about port 9618.
> Does the central manager need to eneble any rlogin/rsh etc' for that to work?
>
> I would appreciate any comment
>
> Guy Tel-Zur
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around 
> http://mail.yahoo.com
> _______________________________________________
> Condor-users mailing list
> Condor-users@xxxxxxxxxxx
> http://lists.cs.wisc.edu/mailman/listinfo/condor-users