Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

memory-related error on proxytrunk #1495

Open
maruqmch opened this issue Sep 9, 2020 · 3 comments
Open

memory-related error on proxytrunk #1495

maruqmch opened this issue Sep 9, 2020 · 3 comments
Labels
* artemis * IvozProvider 2.x Artemis Release +bug Bug trunks SIP Trunks Proxy

Comments

@maruqmch
Copy link

maruqmch commented Sep 9, 2020

Hi Team

I am facing a memory-related error on proxytrunk server, installed ivoz 2.15 version
kamailio -v
version: kamailio 5.1.2 (x86_64/linux)
with -m 512 -M 32
childern=16

System Memory : 24 GB
System Cores: 12

On console getting the following error :

Sep 08 14:40:29 debian /usr/sbin/kamailio[99894]: ERROR: [core/mem/q_malloc.c:286]: qm_find_free(): qm_find_free(0x7fdf51eb9000, 11320); Free fragment not found!
Sep 08 14:40:29 debian /usr/sbin/kamailio[99894]: ERROR: [core/mem/q_malloc.c:419]: qm_malloc(): qm_malloc(0x7fdf51eb9000, 11320) called from tm: h_table.c: build_cell(320), module: tm; Free fragment not found!
Sep 08 14:40:29 debian /usr/sbin/kamailio[99894]: ERROR: tm [t_lookup.c:1279]: new_t(): out of mem:
Sep 08 14:40:29 debian /usr/sbin/kamailio[99894]: ERROR: tm [t_lookup.c:1422]: t_newtran(): new_t failed
Sep 08 14:40:29 debian /usr/sbin/kamailio[99894]: ERROR: sl [sl_funcs.c:362]: sl_reply_error(): stateless error reply used: No error (2/SL)

Please guide about the possible reason of failure or its memory leakage, possible solution.

Thanks

@Kaian Kaian added * artemis * IvozProvider 2.x Artemis Release +bug Bug trunks SIP Trunks Proxy labels Sep 10, 2020
@Kaian
Copy link
Member

Kaian commented Sep 10, 2020

Hi @maruqmch

Please, use provided templates for Bug reports, otherwise your issues will be automatically closed.

We haven't experienced memory problems with trunks proxy. We have fixed some memory leaks in proxyusers configuration, but our graphs show proxytrunks are quite stable.

Try increasing private memory from 32 to 256 and check what modules are taking the memory with:

# kamcmd-proxytrunks mod.stats all pkg
# kamcmd-proxytrunks mod.stats all shm

Regards!

@maruqmch
Copy link
Author

Hi Karan,
Thanks for your comment, will check after increasing memory.

Regards

@Kaian
Copy link
Member

Kaian commented Nov 11, 2020

Any news on this?

Found the memory leaking module?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
* artemis * IvozProvider 2.x Artemis Release +bug Bug trunks SIP Trunks Proxy
Development

No branches or pull requests

2 participants