create github issue for this
https://github.com/kamailio/kamailio/issues/1001
2017-02-16 10:34 GMT+03:00 Daniel-Constantin Mierla :
> If it is already running for some time, run:
>
> kamcmd corex.pkg_summary idx 1
>
> and then get the related qm/fm status/summary log messages from syslog and
> se
If it is already running for some time, run:
kamcmd corex.pkg_summary idx 1
and then get the related qm/fm status/summary log messages from syslog
and send them here to check if there is any potential pkg leak in the
sip worker one.
Cheers,
Daniel
On 16/02/2017 08:27, Dmitri Savolainen wrote:
No any tests. It was running two weeks and crushed in out of peak period.
i have never seen this before in the months of uptime. Will start
monitoring pkg memory from this moment too.
2017-02-16 9:58 GMT+03:00 Daniel-Constantin Mierla :
> Hello,
>
> for how long it was running? Was it any stress
Hello,
for how long it was running? Was it any stress test or just normal traffic?
The issue is related to pkg memory, to get the stats of it per each
process, run:
kamcmd pkg.stats
Cheers,
Daniel
On 15/02/2017 21:04, Dmitri Savolainen wrote:
> Hi.
> My kamailio v4.4.5 installation ( -m 512 -
Hi.
My kamailio v4.4.5 installation ( -m 512 -M 64 ) stop sip processing with
repeatable error:
Feb 15 21:45:05 kamailio[14173] ERROR: [mem/f_malloc.c:415]:
> fm_search_defrag(): fm_search_defrag(0x7f39917fa010, 952); Free fragment
> not found!
> Feb 15 21:45:05 kamailio[14173] ERROR: [mem/f_ma