Univention Bugzilla – Bug 40799
Self service fails with postgres error
Last modified: 2016-03-18 06:50:26 CET
Created attachment 7504 [details] Screenshot OperationalError: FATAL … See Screenshot.
Created attachment 7507 [details] patch patch: Don't fork a module process for every HTTP request by using the unofficial HTTP basic auth feature of UMC.
Patch applied. As the same UMC module process is used now for every request there might be side effects. Can you please test how the memcached connection and the postgresql connection behaves in terms of timeouts and restarts. The UCR variable umc/module/timeout can be used to specify the seconds how long a module process is kept open when idling. Btw: Can we remove the memcached thing at all with that change? Because the protection against DoS happens in the same process now. If yes, not now.
OK: advisory OK: automated tests (ucs-test -E dangerous -s self-service), minor fixes in r67834 OK: manual tests checking number of database connections using: echo "SELECT * FROM pg_stat_activity"| su - postgres -c psql --> One connection per UMC module process. --> One UMC module process per language. --> Max. 35 UMC module processes.
<http://errata.software-univention.de/ucs/4.1/132.html>
<http://errata.software-univention.de/ucs/4.1/134.html>