Re: current userland slapd no response

["matthew sporleder" <msporleder%gmail.com@localhost>]

On Mon, Sep 15, 2008 at 11:25 PM, Sarton O'Brien 
<bsd-xen%roguewrt.org@localhost> wrote:
> I've just updated kernel and userland which was built 12th September.
>
> Slapd launches but stalls when queried. Attempting to kill slapd results in:
>
> slap_listener_activate(7):
> ^Cdaemon: shutdown requested and initiated.
> connection_closing: readying conn=0 sd=11 for close
> connection_close: deferring conn=0 sd=11
> connection_closing: readying conn=1 sd=12 for close
> connection_close: deferring conn=1 sd=12
> connection_closing: readying conn=2 sd=13 for close
> connection_close: deferring conn=2 sd=13
> connection_closing: readying conn=3 sd=14 for close
> connection_close: deferring conn=3 sd=14
> connection_closing: readying conn=4 sd=16 for close
> connection_close: deferring conn=4 sd=16
> connection_closing: readying conn=5 sd=17 for close
> connection_close: deferring conn=5 sd=17
> connection_closing: readying conn=6 sd=18 for close
> connection_close: deferring conn=6 sd=18
> connection_closing: readying conn=7 sd=19 for close
> connection_close: deferring conn=7 sd=19
> connection_closing: readying conn=8 sd=20 for close
> connection_close: deferring conn=8 sd=20
> connection_closing: readying conn=9 sd=21 for close
> connection_close: deferring conn=9 sd=21
> connection_closing: readying conn=10 sd=22 for close
> connection_close: deferring conn=10 sd=22
> connection_closing: readying conn=11 sd=23 for close
> connection_close: deferring conn=11 sd=23
> connection_closing: readying conn=12 sd=24 for close
> connection_close: deferring conn=12 sd=24
> connection_closing: readying conn=13 sd=25 for close
> connection_close: deferring conn=13 sd=25
> connection_closing: readying conn=14 sd=26 for close
> connection_close: deferring conn=14 sd=26
> connection_closing: readying conn=15 sd=27 for close
> connection_close: deferring conn=15 sd=27
> slapd shutdown: waiting for 33 threads to terminate
>
> I imagine it's a threads issue. I'm updating/building/installing as we speak
> but only saw one change to libpthread.
>
> Anyone know what might be causing this?
>


That's a pretty normal shutdown message (assuming you have a bunch of
open connections, anyway).  Can you try starting slapd with -d -1 and
seeing if someone obvious comes up?