[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: slapd misses TCP state transition on startup



On Wed, 6 Aug 2003, Corey Scholefield wrote:

Upon closer inspection, 1 of the 3 backends was corrupt.  My recover script did not
launch db_recover on the corrupt backend, so the problem remained.

After running db_recover on the problem BDB backend, the normal functionality
has resumed.

A tip-off to the problem was an attempt to launch slapcat against the problem
backend, and slapcat (run in verbose) never got past the opening of the environment
in that data directory.

C

> Startup: slapd starts up, but netstat reports that it is in TCP state CLOSED
> for port 389.  Somehow it has not made the transition to state LISTEN.
>
> Shutdown: slapd no longer listens to the INT signal to shutdown, so I must shut
> it down ungracefully via kill -9.
>
> Version: OpenLDAP 2.1.22
> System: AIX 4.3.3
>
> I am using this slapd with 3 BDB backends, 1 for each of 3 different suffixes.  Today
> we were busy adding 30,000 data records into 1 backend database (for a total of 35,000),
> while doing some functionality testing against another backend.

Corey Scholefield | coreys@uvic.ca | +1.250.472.4549
Systems Administrator | UVic Computing Services
Victoria, B.C. Canada