Last week we did a configuration change that should prevent 503 errors on the Weblate. You should now see 503 only if the weblate server is down for real. (But in case of high load, you may experience error 504 directly from weblate server, or error message in case of SQL server being down.) Please let us know if you still see random 503 errors. Technical details: openSUSE servers use haproxy for data routing. haproxy has a monitor feature. By default, haproxy monitors the home page. But in case of Weblate-2.6, the home page contains list of all projects. It requires number of database queries, and it requires a non trivial time. It caused further increase of the load, resulting a late reply. haproxy assumed that the server is down, and returned 503. Now haproxy monitors https://l10n.opensuse.org/static/weblate-128.png. It is fast, but it does not recognize broken database connection. Things are still not optimal. The fulltext engine has some memory leaks that causes server overload sometimes. I hope that these problems will be fixed by the upgrade to the latest Weblate. -- Best Regards / S pozdravem, Stanislav Brabec software developer --------------------------------------------------------------------- SUSE LINUX, s. r. o. e-mail: sbrabec@suse.com Křižíkova 148/34 (Corso IIa) tel: +49 911 7405384547 186 00 Praha 8-Karlín fax: +420 284 084 001 Czech Republic http://www.suse.cz/ PGP: 830B 40D5 9E05 35D8 5E27 6FA3 717C 209F A04F CD76 -- To unsubscribe, e-mail: opensuse-translation+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-translation+owner@opensuse.org