<html><body><div style="font-family: lucida console,sans-serif; font-size: 12pt; color: #000000"><div>Hello Everyone,</div><div>You need tweak sysctl and postgresql.conf to allow opensips connect properly to remote postgresql.</div><div>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.</div><div><br data-mce-bogus="1"></div><div>volga629</div><div><br></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><b>From: </b>"Adrien Martin" <a.martin@alphalink.fr><br><b>To: </b>"OpenSIPS users mailling list" <users@lists.opensips.org>, "johan" <Johan@democon.be><br><b>Sent: </b>Tuesday, August 11, 2020 7:25:31 AM<br><b>Subject: </b>Re: [OpenSIPS-Users] [Crash Report] Weird crash with drouting/tls_mgm/usrloc/db_postgresql<br></div><div><br></div><div data-marker="__QUOTED_TEXT__">Hello,<br><br>Thanks for your answer.<br>Do you mean the patch didn't resolve the issue for volga629?<br><br>Anyway it's an interesting idea, this would point to a concurrency problem.<br>Gonna try but i think it would not work because there would still be udp and tcp/tls workers at the same time.<br><br><br>Regards,<br>-- <br>Adrien Martin<br><br><br>Le 11/08/2020 à 12:00, Johan De Clercq a écrit :<br>> I believe that 1579 was fixed by volga629 by reducing the number of workers<br>> in opensips.cfg.<br><br><br>_______________________________________________<br>Users mailing list<br>Users@lists.opensips.org<br>http://lists.opensips.org/cgi-bin/mailman/listinfo/users<br></div></div></body></html>