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

[Condor-users] The SECMAN error again



[Sorry if this post appears multiple times]

I'm trying to get condor running again after a long pause where our condor
setup "deteriorated".  It was working many months ago.  It's an entirely
Windows XP pool.

D:\>condor -version
$CondorVersion: 7.2.4 Jun 15 2009 BuildID: 159529 $
$CondorPlatform: INTEL-WINNT50 $

The MasterLog on the central manager (136.200.32.102) has this entry many
times:

9/29 15:38:38 attempt to connect to <136.200.32.102:9618> failed:
connect errno = 10061 connection refused.
9/29 15:38:38 ERROR: SECMAN:2004:Was waiting for TCP auth session to
<136.200.32.102:9618>, but it failed.

So the CM can't even talk to other Condor processes on the same machine?

We do run DNS or Active-something with our Windows LAN. I tried running with
ALL_DEBUG = D_FULLDEBUG and D_NETWORK but it didn't throw any more light on
things for me.

Ralph Finch, P.E.
California Dept. of Water Resources
Delta Modeling Section, Bay-Delta Office Room 215-13
1416 9th Street
Sacramento CA  95814
916-653-7552
rfinch@xxxxxxxxxxxx


<<attachment: winmail.dat>>