After having re-enabled the close_expired_tcp modparam, Kamailio made it about 12hours before giving the following warning and blocking new TLS connections again:
ERROR: tls [tls_server.c:189]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: 8870536 ERROR: <core> [tcp_read.c:1303]: tcp_read_req(): ERROR: tcp_read_req: error reading
When the close_expired_tcp modparam was disabled, Kamailio never displayed this warning and continued to process all TLS connections from 2015-11-19 through 2015-11-23, when I re-enabled the close_expired_tcp modparam for this test.
Thanks. -A
Quoting Anthony Messina amessina@messinet.com:
I have re-enabled the close_expired_tcp modparam and will report back when I have results. Thanks Camille. -A -- Anthony - https://messinet.com/
On November 23, 2015 3:46:55 AM CST, Camille Oudot camille.oudot@orange.com wrote:
Le Sun, 22 Nov 2015 15:22:06 -0600, Anthony Messina amessina@messinet.com a écrit :
I did tow things on 2015-11-19 which seem to have (at least temporarily) resolved this issue:
Upgraded to git master@b056aed
Commented out #modparam("usrloc", "close_expired_tcp", 1) based on
http://lists.sip-router.org/pipermail/sr-users/2015-November/090733.html
Hi Anthony,
does this memory issue occur again if you re-enable close_expired_tcp on this latest version you recompiled? This would help isolating the issue. Thanks