Oh yes? What is this then /usr/local/bin/postlogin.sh I don't know you have to look at what is different after the restart.
Do you mean that the contents of this file are not cached? or that there is some limit on the number of simultaneous requests to read it? content of this file not look too heavy
psql -c "UPDATE core_user SET last_login=now() WHERE username='$USER'" > /dev/null
Probably not as you only restarted. The limit is when you have create a new
connection and don't use an existing one.
I don't see a way to reuse an existing connection yet if the number of persistent connections after a restart should increase from 0 to 40K I miss something obvious? (We tried changing the client_limit value for imap-login (in order to reduce the number of processes), but in our experience it works correctly only within 3-5 and at higher values imap-login stops responding quite quickly.)
On Mon, Feb 3, 2025 at 10:29 PM Marc <Marc@f1-outsourcing.eu> wrote:
No, we don't have the noticeable iowait problem as I see it(at least until the number of connections lower 20-30K). The problem appears when thousands of clients try to reconnect at the same time and according to the documentation the auth service should make a simple request to postgres for this. This should not be related to i\o in theory. Just a sql query.
Oh yes? What is this then /usr/local/bin/postlogin.sh I don't know you have to look at what is different after the restart.
I don't really get this authentication attempts is limitted by tcp not? So
it does not really matter what you have mariadb, ldap, http, you awalys are limited to 150-200 r/s.
Can you explain? We also have SMTP connections and postfix on the same servers, but problems arise only at the stage of connecting to IMAP via postgres. How can this be related to tcp limits?
Probably not as you only restarted. The limit is when you have create a new connection and don't use an existing one.
Additionally, I would like to note that we can have hundreds of connections from one IP. Could this lead to a race condition with the anvil service and an increase in connection timeouts?
But this to you already had before the restart not? You have to search what is different.