Re: [Condor-users] Please help to SECMAN:2004 failed to create security session error

[Matthew Farrellee <matt@xxxxxxxxxx>]

On 06/04/2012 10:25 AM, Canan Has wrote:
> Hi all,
>
> I have taken an error for a newly added pc to my condor pool.
> In the CollectorLog of central machine, it is written that:
> 06/04/12 17:21:13 Got QUERY_STARTD_PVT_ADS
> 06/04/12 17:21:13 (Sending 42 ads in response to query)
> 06/04/12 17:21:22 ScheddAd     : Inserting ** "< Tusi , 10.1.142.63 >"
> 06/04/12 17:21:40 StartdAd     : Inserting ** "< slot3@Tusi , 10.1.142.63 >"
> 06/04/12 17:21:40 StartdPvtAd  : Inserting ** "< slot3@Tusi , 10.1.142.63 >"
> 06/04/12 17:21:56 Can't open directory "/home/condor/config" as
> PRIV_UNKNOWN, errno: 2 (No such file or directory)
> 06/04/12 17:21:56 Can't open directory
> "/home/condor2/condor/local/config" as PRIV_UNKNOWN, errno: 2 (No such
> file or directory)
> 06/04/12 17:21:56 Setting maximum accepts per cycle 4.

Make sure you have a condor user&group on the machine. Or you're using 
CONDOR_IDS.


> On the other hand, in StartLog of my machine "Tusi there are many
> SECMAN:2004 errors exist (given below). BTW: I have ben using Condor
> 7.6.6 and the firewall in Tusi is off. What should I do? :
>
> 6/04/12 17:08:36 ** condor_startd.exe (CONDOR_STARTD) STARTING UP
> 06/04/12 17:08:36 ** D:\condor\bin\condor_startd.exe
> 06/04/12 17:08:36 ** SubsystemInfo: name=STARTD type=STARTD(7)
> class=DAEMON(1)
> 06/04/12 17:08:36 ** Configuration: subsystem:STARTD local:<NONE>
> class:DAEMON
> 06/04/12 17:08:36 ** $CondorVersion: 7.6.6 Jan 17 2012 BuildID: 401976 $
> 06/04/12 17:08:36 ** $CondorPlatform: x86_winnt_5.1 $
> 06/04/12 17:08:36 ** PID = 4716
> 06/04/12 17:08:36 ** Log last touched 6/4 16:04:29
> 06/04/12 17:08:36 ******************************************************
> 06/04/12 17:08:36 Using config source: D:\condor\condor_config
> 06/04/12 17:08:36 Using local config sources:
> 06/04/12 17:08:36    D:\condor/condor_config.local
> 06/04/12 17:08:36 DaemonCore: command socket at <10.1.142.63:49183
> <http://10.1.142.63:49183>>
> 06/04/12 17:08:36 DaemonCore: private command socket at
> <10.1.142.63:49183 <http://10.1.142.63:49183>>
> 06/04/12 17:08:36 Setting maximum accepts per cycle 4.
> 06/04/12 17:08:47 VM-gahp server reported an internal error
> 06/04/12 17:08:47 VM universe will be tested to check if it is available
> 06/04/12 17:08:47 History file rotation is enabled.
> 06/04/12 17:08:47   Maximum history file size is: 20971520 bytes
> 06/04/12 17:08:47   Number of rotated history files is: 2
> 06/04/12 17:08:48 slot1: New machine resource allocated
> 06/04/12 17:08:48 slot2: New machine resource allocated
> 06/04/12 17:08:48 slot3: New machine resource allocated
> 06/04/12 17:08:48 slot4: New machine resource allocated
> 06/04/12 17:08:53 CronJobList: Adding job 'mips'
> 06/04/12 17:08:53 CronJobList: Adding job 'kflops'
> 06/04/12 17:08:53 CronJob: Initializing job 'mips'
> (D:\condor/bin/condor_mips.exe)
> 06/04/12 17:08:53 CronJob: Initializing job 'kflops'
> (D:\condor/bin/condor_kflops.exe)
> 06/04/12 17:09:18 attempt to connect to <10.1.144.12:9618
> <http://10.1.144.12:9618>> failed: timed out after 20 seconds.
> 06/04/12 17:09:18 ERROR: SECMAN:2004:Was waiting for TCP auth session to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>, but it failed.
> 06/04/12 17:09:18 Failed to start non-blocking update to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>.
> 06/04/12 17:09:18 ERROR: SECMAN:2004:Was waiting for TCP auth session to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>, but it failed.
> 06/04/12 17:09:18 Failed to start non-blocking update to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>.
> 06/04/12 17:09:18 ERROR: SECMAN:2004:Was waiting for TCP auth session to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>, but it failed.
> 06/04/12 17:09:18 Failed to start non-blocking update to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>.
> 06/04/12 17:09:18 ERROR: SECMAN:2004:Failed to create security session
> to <10.1.144.12:9618 <http://10.1.144.12:9618>> with TCP.
> |SECMAN:2003:TCP connection to <10.1.144.12:9618
> <http://10.1.144.12:9618>> failed.
> 06/04/12 17:09:18 Failed to start non-blocking update to
> <10.1.144.12:9618 <http://10.1.144.12:9618>>.

There might be a firewall issue on 10.1.144.12, except later 
(CollectorLog @17:21:40) you can see Tusi updates are getting through.


Best,


matt