> Ah yes of course. Here is 1 run of their web app load test, it is 6 minutes > long, and it should mostly be only the test it self. I will start looking for > > We encountered 2 "Can not contact ldap server" errors during this run. > > 2 cant contact ldap server errors in this run below. >
These errors are only shown on the client, yes? Is there any evidence of a failed connection in the access log? > After the run I bumped up these from 4096, > > net.ipv4.tcp_max_syn_backlog = 6144 > net.core.somaxconn = 6144 > > Yet we still get the ldap errors (this one and the start tls request error > previously mentioned.) > > Should I bump up the nsslapd-listen-backlog-size, > net.ipv4.tcp_max_syn_backlog, net.core.somaxconn more ? > We encountered a similar issue recently with another load test, where the load tester wasn't averaging it's connections, it would launch 10,000 connections at once and hope they all worked. With your load test, is it actually spreading it's connections out, or is it bursting? -- Sincerely, William Brown Senior Software Engineer, Identity and Access Management SUSE Labs, Australia
-- _______________________________________________ 389-users mailing list -- 389-users@lists.fedoraproject.org To unsubscribe send an email to 389-users-le...@lists.fedoraproject.org Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/389-users@lists.fedoraproject.org Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
