I’m not familiar with postgres configuration, what should I be looking for? It’s a default install in Debian buster, installed through the apt archives.
I also don’t seem to have any issues with other applications which are connecting to MariaDB and Redis servers over a Unix socket, so really not sure what’s going on here.
Same thing sometimes happens to me. But only when we (re)started Tryton-server and Nginx-server. I think it’s a configuration problem in Nginx, because at one client it is running fine, as at another client this happens. What I see on the client side is something about the bus. After login and logout about 2 - 3 times everything is back to normal and the message does not appear anymore.
Because it appeared after restarting Tryton, it isn’t a issue at the moment so I didn’t dig deeper. But I think in my case it has something to do with the location definition in Nginx configuration.
I tried logging in and out 3 times, but it also doesn’t seem to make a difference to me. If I open and close a few different tabs in the admin, I will encounter that error within a minute or 2.
It also sounds a bit weird that Nginx could be responsible for causing a connection between Tryton and the DB to get closed. Surely, that would be outside the control of Nginx.
Are you using the webclient? We are using the GTK desktop client. I’ve asked my client to pull the nginx.conf from the server. That one works for them.
And from my memory there was a specific location with the databasename.
Another possibility is that the connection pool is started before the fork of µwsgi. In this case the connections could be shared between multiple process and closed by one while the other still use it.
You could try to µwsgi option lazy-apps=true which prevent µwsgi to load the application before forking.