Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hello, Thanks for testing and feedback! I backported the patches to branch 5.2. Cheers, Daniel On 16.08.19 18:11, José Seabra wrote: > Hello Daniel, > > Those patches works ok. > Thank you for your support. > > Cheers > José Seabra > > Daniel-Constantin Mierla >

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hello Daniel, Those patches works ok. Thank you for your support. Cheers José Seabra Daniel-Constantin Mierla escreveu no dia sexta, 16/08/2019 à(s) 13:26: > Yes, those are the patches. > > Cheers, Daniel > On 16.08.19 14:08, José Seabra wrote: > > yes i need backport them, are these the

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Yes, those are the patches. Cheers, Daniel On 16.08.19 14:08, José Seabra wrote: > yes i need backport them, are these the correct patchs ? > > * > https://github.com/kamailio/kamailio/commit/4a904b5fe90253d0d5517cf1a5cdca3695e59ec3.patch > * >

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

yes i need backport them, are these the correct patchs ? - https://github.com/kamailio/kamailio/commit/4a904b5fe90253d0d5517cf1a5cdca3695e59ec3.patch - https://github.com/kamailio/kamailio/commit/d7bd8a187546f132547788c47ff9a3947be49957.patch -

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Can you try with latest master? I pushed some patches there for a proper fix. If you need to backport, are the patches done to the files core/fmsg.{c,h} and to evapi module, because I pushed some other patches not related to this issue. Cheers, Daniel On 16.08.19 12:03, José Seabra wrote: >

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Updating my last email with the output of coredump generated by kamailio. Please check out the following link to get the coredump output: https://pastebin.com/gsyPc0eg Let me know if you need further information Thank you José José Seabra escreveu no dia sexta, 16/08/2019 à(s) 10:37: > Hi

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hi Daniel, After apply your patch i noticed the following situations: When i restart my external application kamailio prints the following logs: *edge-sip-proxy[13581]: INFO: ESP_LOG: 123: [evapi:connection-closed] EVAPI 127.0.0.1:52906 connection has been closed*

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hello, can you try with master branch? The issue should be fixed by the commit:   * https://github.com/kamailio/kamailio/commit/d36a4b00c6becd42cfcec4fc7eb398371e1cc812 If works ok, then I will backport to stable branches. Cheers, Daniel On 14.08.19 12:19, José Seabra wrote: > Hello, > Please

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hello, Please find out the logs in the following link: - https://pastebin.com/h2UNHwYC Let me know if you need something else. Cheers José Seabra Daniel-Constantin Mierla escreveu no dia quarta, 14/08/2019 à(s) 10:59: > Hello, > > that's memory status, printing details for each allocated

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hello, that's memory status, printing details for each allocated chunk. I could spot a lot of chunks from the parser and get header field functions, but to be sure there is nothing else, can you set global parameter: mem_summary=12 and then reproduce again. The logs printed in syslog should

Re: [SR-Users] Evapi dispatcher is consuming all the private memory

Hello, can you enable pkg summary and generate it once the out of memory happens? Set memlog to lower value than debug, when the memory happens, do: https://www.kamailio.org/docs/modules/devel/modules/corex.html#corex.rpc.pkg_summary Then send some traffic to that process and watch the syslog.

[SR-Users] Evapi dispatcher is consuming all the private memory

Hello there, I'm using kamailio 5.2.1 with evapi module to send and receive events from an external application. During my stress tests to kamailio i have been noticing that at some point kamailio is getting out of memory: edge-sip-proxy[20565]ERROR: ESP_LOG: : [core/mem/q_malloc.c:291]: