Hi Alan,
My NSINTERADDR records are correct. I did notice that my
DOMAINORIGIN value was not, but after correcting it and recycling TCPIP,
it still exhibits the same behavior.
Dave
-----Original Message-----
From: Alan Altmark <[email protected]>
Reply-to: The IBM z/VM Operating System <[email protected]>
To: [email protected]
Subject: Re: LDAP Initialization
Date: Thu, 1 Oct 2009 17:54:07 -0400
On Thursday, 10/01/2009 at 05:26 EDT, Dave Keeton
<[email protected]> wrote:
> Can anyone tell me why it takes EXACTLY 4 minutes for LDAPSRV to go from
"ready
> for requests" to actually LISTENING on the interfaces?
>
> 14:10:57 LDAPSRV *8 091001 21:10:57.790088 GLD1004I LDAP server is
ready for
> requests
> 14:14:57 LDAPSRV *8 091001 21:14:57.798419 GLD1059I Listening for
requests on
> ...
>
> It's the same every time - 4 minutes down to the second.
How odd. On my system, I get these as the last two entries:
091001 19:07:26.040878 GLD1059I Listening for requests on 127.0.0.1 port
389.
091001 19:07:26.919681 GLD1004I LDAP server is ready for requests.
(preceeded by GLD1059I for each active IP interface.)
Perhaps it is trying to do some reverse DNS lookup for itself that is
retrying and failing every time you start the server? Are your
NSINTERADDR entries in TCPIP DATA good?
Alan Altmark
z/VM Development
IBM Endicott
