Hello, these errors do not indicate a crash, but unability to read due to low available memory. Did you get a crash (kamailio stopped)? If yes, any core file from where you can extract the backtrace? Anyhow, as hint, if you use a lot of tls, increase the size for shared memory, it is needed a lot there. Cheers, Daniel On 10.10.17 16:32, Andrew Paul wrote: Hi all, We were using kamailio 4.4.5 and we enabled only for webrtc. We were observing two memory crashed in last two weeks. Oct 10 01:03:03 webrtc /usr/sbin/kamailio[18002]: ERROR: <core> [tcp_read.c:1321]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f21ea8f6198 r: 0x7f21ea8f6218 Oct 10 01:03:04 webrtc /usr/sbin/kamailio[18003]: ERROR: tls [tls_server.c:190]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=9926856 threshold1=9961472 Oct 10 01:03:04 webrtc /usr/sbin/kamailio[18003]: ERROR: <core> [tcp_read.c:1321]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f21ea8f6198 r: 0x7f21ea8f6218 Oct 10 01:03:05 webrtc /usr/sbin/kamailio[18004]: ERROR: tls [tls_server.c:190]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=9926856 threshold1=9961472 Oct 10 01:03:05 webrtc /usr/sbin/kamailio[18004]: ERROR: <core> [tcp_read.c:1321]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f21ea8f6198 r: 0x7f21ea8f6218 Is there any known issue for tls module in kamailio_4.4.5 ?. We are using default 64MB for shared memory and 8MB for private memory. Do we need to increase this ?. Regards Andrew _______________________________________________ Kamailio (SER) - Users Mailing Listsr-users@lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com

Still curious if you got a core file so far (or it was just those error messages) and if yes, it would be good to get the backtrace. Cheers, Daniel On 11.10.17 05:27, Andrew Paul wrote: Thanks Daniel. We have increase shm memory to 1024 from 64 and private memory to 64 from 8MB. We will closely monitor and will update the thread if encounter any issue. Regards Varghese Paul On Tue, Oct 10, 2017 at 10:04 PM, Daniel-Constantin Mierla < miconda(a)gmail.com&gt; wrote: -- Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda Kamailio Advanced Training - www.asipto.com Kamailio World Conference - www.kamailioworld.com _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Hi Daniel, We were running the kamailio without any issue after changing the shared memory to 1024. We dont have any issue on last two months.  But today we got the issue and we are not able to connect new tls connections.  Dec 15 08:13:56 webrtc /usr/sbin/kamailio[19550]: ERROR: tls [tls_server.c:190]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=9886536 threshold1=9961472 Dec 15 08:13:56 webrtc /usr/sbin/kamailio[19550]: ERROR: <core> [tcp_read.c:1321]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f642bb1c668 r: 0x7f642bb1c6e8 Dec 15 08:13:56 webrtc /usr/sbin/kamailio[19550]: ERROR: tls [tls_server.c:190]: tls_complete_init(): tls: ssl bug #1491 workaround: not enough memory for safe operation: shm=9886536 threshold1=9961472 Dec 15 08:13:56 webrtc /usr/sbin/kamailio[19550]: ERROR: <core> [tcp_read.c:1321]: tcp_read_req(): ERROR: tcp_read_req: error reading - c: 0x7f642bb1c668 r: 0x7f642bb1c6e8 There is no crash, it is only low memory and new connections not occuring.  Can you suggest what can be the resolution here ?. Do we need a process restart to free up the memory resource ?.  Regards Varghese Paul  On Wed, Oct 11, 2017 at 2:28 PM, Sergey Safarov &lt;s.safarov(a)gmail.com <mailto:s.safarov@gmail.com>> wrote: Hello Daniel Could you look this ticket with attached backtrace https://2600hz.atlassian.net/browse/KAZOO-5699 <https://2600hz.atlassian.net/browse/KAZOO-5699> I not sure where is root of issue. May be your comment clean this. ср, 11 окт. 2017 г. в 10:43, Daniel-Constantin Mierla &lt;miconda(a)gmail.com <mailto:miconda@gmail.com>>: Still curious if you got a core file so far (or it was just those error messages) and if yes, it would be good to get the backtrace. Cheers, Daniel On 11.10.17 05:27, Andrew Paul wrote: -- Daniel-Constantin Mierla www.twitter.com/miconda <http://www.twitter.com/miconda> -- www.linkedin.com/in/miconda <http://www.linkedin.com/in/miconda> Kamailio Advanced Training - www.asipto.com <http://www.asipto.com> Kamailio World Conference - www.kamailioworld.com <http://www.kamailioworld.com> _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org <mailto:sr-users@lists.kamailio.org> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users <https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users>