Am 11.12.23 um 18:10 schrieb Ondřej Kuzník:
On Wed, Dec 06, 2023 at 08:11:52PM +0100, Stefan Kania wrote:
Hi Ondrej,
I restarted with a new test.
Now I'm having 2 loadbalancer one is configured via cn=config and one over
slapd.conf. Both are configured exactly the same. Same binduser, same
On Wed, Dec 06, 2023 at 08:11:52PM +0100, Stefan Kania wrote:
> Hi Ondrej,
>
> I restarted with a new test.
> Now I'm having 2 loadbalancer one is configured via cn=config and one over
> slapd.conf. Both are configured exactly the same. Same binduser, same
> ldap-server same everything.
> For my
Am 07.12.23 um 17:40 schrieb Quanah Gibson-Mount:
My question was more, once you add the database config block, if you
ldapsearch the cn=config database it generates, does it match what you
get from slatpest conversion.
Now I understand :-). so that's what I did now
adding
--
--On Thursday, December 7, 2023 5:23 PM +0100 Stefan Kania
wrote:
I added:
--
database config
rootdn "cn=admin,cn=config"
rootpw config
--
to the slapd.conf. After adding slapd is still working with slapd.conf
then I converted the slapd.conf with:
slaptest -F
Am 06.12.23 um 22:12 schrieb Quanah Gibson-Mount:
--On Wednesday, December 6, 2023 8:11 PM +0100 Stefan Kania
wrote:
Hi Ondrej,
I restarted with a new test.
Now I'm having 2 loadbalancer one is configured via cn=config and one
over slapd.conf. Both are configured exactly the same. Same
--On Wednesday, December 6, 2023 8:11 PM +0100 Stefan Kania
wrote:
Hi Ondrej,
I restarted with a new test.
Now I'm having 2 loadbalancer one is configured via cn=config and one
over slapd.conf. Both are configured exactly the same. Same binduser,
same ldap-server same everything.
For my
Hi Ondrej,
I restarted with a new test.
Now I'm having 2 loadbalancer one is configured via cn=config and one
over slapd.conf. Both are configured exactly the same. Same binduser,
same ldap-server same everything.
For my test I started tcpdump on the loadbalancer and on the two
ldap-server.
Am 04.12.23 um 16:19 schrieb Ondřej Kuzník:
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.
I Know: Starting the loadbalancer
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
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
On Mon, Dec 04, 2023 at 02:34:57PM +0100, Stefan Kania wrote:
> Hello Ondrej,
>
> if I get:
> --
> root@loadbalancer01:~# ldapsearch -x -D
> uid=repl-user,ou=users,dc=example,dc=net -W
> Enter LDAP Password:
> ldap_bind: Server is unavailable (52)
> additional info: no
Now I did a check with tcpdump. Starting tcpdump on both systems I see,
that the tcp connection is established. But now packages send when doing
a ldapsearch.
Am 04.12.23 um 11:52 schrieb Ondřej Kuzník:
On Mon, Dec 04, 2023 at 11:40:29AM +0100, Stefan Kania wrote:
Hi to all,
when I setup
Hello Ondrej,
if I get:
--
root@loadbalancer01:~# ldapsearch -x -D
uid=repl-user,ou=users,dc=example,dc=net -W
Enter LDAP Password:
ldap_bind: Server is unavailable (52)
additional info: no connections available
--
The log on the loadbalancer is showing:
On Mon, Dec 04, 2023 at 11:40:29AM +0100, Stefan Kania wrote:
> Hi to all,
>
> when I setup the loadbalancer lloadd via slapd.conf everything is working
> fine. Here my slapd.conf
> [...]
>
> As soon as I change to cn=config with the following configuration:
> [...]
>
> -
> The
Hi to all,
when I setup the loadbalancer lloadd via slapd.conf everything is
working fine. Here my slapd.conf
-
TLSCertificateFile /opt/symas/etc/openldap/example-net-cert.pem
TLSCertificateKeyFile /opt/symas/etc/openldap/example-net-key.pem
TLSCACertificateFile
15 matches
Mail list logo
