Hello, I tried to reduce the number of workers to 1 with Opensips 3.1 (can not change TCP workers with 2.4+) and there is another crash about tls_domain that i have to investigate :) Our problems are somewhat different though, in this one there is no load/no calls, just some registrations (less than 5 UAC) and some drouting probing UDP and TLS.
As #1579 was closed, did the commit https://github.com/OpenSIPS/opensips/commit/c1403a1d9bee2254a84a866352266a41d9ff93bc fixed your problem or did you just tweak the workers/sysctl.conf/postgresql.conf? Thanks, regards, -- Adrien Martin Le 11/08/2020 à 14:34, Slava Bendersky a écrit : > Hello Everyone, > You need tweak sysctl and postgresql.conf to allow opensips connect properly > to remote postgresql. > In opensips I can't pass for any transport udp_worker tcp_worker more then > 10. Other wise it starts segfaulting. One opensips open from 150-170 > connections to database under load when cluster of 3 nodes you need > postgresql at least 650 connection limit. If you use TCP or WSS or TLS you > need increase tcp protocol buffer on protocol level other wise it will be > bottleneck for database and it will slow down all. > > volga629
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Users mailing list [email protected] http://lists.opensips.org/cgi-bin/mailman/listinfo/users
