On Mon, Dec 04, 2023 at 03:42:34PM +0100, Stefan Kania wrote: > Am 04.12.23 um 15:00 schrieb Ondřej Kuzník: >> Hi Stefan, >> are you trying to use the load balancer before it has had a chance to >> establish its own connections? > > Hi Ondrej, > > setting loglevel to "conns" on both, the ldap-servers and the loadbalancer > I'm getting no entry in the log on the two ldap-server but on the > loadbalancer I see: > --------------- > Dez 04 15:33:54 loadbalancer01 slapd[1519]: lload_listener: listen=14, new > connection fd=29 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: lload_connection_init: connection > connid=4 allocated for socket fd=29 peername=IP=192.168.56.24:50978 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: client_tls_handshake_cb: connid=4 > finished > Dez 04 15:33:54 loadbalancer01 slapd[1519]: connection_read_cb: connection > connid=4 ready to read > Dez 04 15:33:54 loadbalancer01 slapd[1519]: operation_init: received a new > operation, bind request with msgid=1 for client connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: request_bind: connid=4, msgid=1 > no available connection found > Dez 04 15:33:54 loadbalancer01 slapd[1519]: connection_write_cb: considering > writing to live connid=4 what=0 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: connection_write_cb: have > something to write to connection connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: handle_pdus: re-enabled read > event on connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: connection_read_cb: suspended > read event on connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: connection_read_cb: connection > connid=4 ready to read > Dez 04 15:33:54 loadbalancer01 slapd[1519]: operation_init: received a new > operation, unbind request with msgid=2 for client connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: handle_one_request: received > unbind, closing client connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: client_unlink: removing client > connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: connection_read_cb: suspended > read event on connid=4 > Dez 04 15:33:54 loadbalancer01 slapd[1519]: client_destroy: destroying client > connid=4
Are you saying there are really no messages at all between lloadd startup and your client connecting to it? I will say it again: lloadd does not open any connections in response to client activity, they are established as part of its operation and until you have at least one, requests will be rejected with 52 Unavailable. You want to figure out why no connections are being opened (successfully). Regards, -- Ondřej Kuzník Senior Software Engineer Symas Corporation http://www.symas.com Packaged, certified, and supported LDAP solutions powered by OpenLDAP
