[SR-Users] Logs suddenly inundated with qm_malloc errors

[Henning Westerholt]

Hello,

difficult to say, it could be also some random memory error or virtual/physical hardware issue. Are you seeing more error related to that, maybe it’s a memory leak? Make probably sense to observe it further. If it happens again, a diff between the rtpengine in 5.6.1 and 5.6.2 might get more insight.
Regarding a memory leak, you can observe the memory pool by kamcmd or different tools by looking at statistics or memory status.

Cheers,

Henning

--
Henning Westerholt – https://skalatan.de/blog/
Kamailio services – https://gilawa.com<https://gilawa.com/>

From: sr-users <sr-users-bounces at lists.kamailio.org> On Behalf Of George Diamantopoulos
Sent: Tuesday, December 13, 2022 12:14 PM
To: Kamailio (SER) - Users Mailing List <sr-users at lists.kamailio.org>
Subject: [SR-Users] Logs suddenly inundated with qm_malloc errors

Hello all,

I'm testing out release 5.6.2 on one production kamailio instance, and today our monitoring system triggered an alarm for lack of disk space on /. Indeed, kamailio.log started growing at an alarming rate at some point.

At about the same time disk space started being depleted, the following line was frequently logged in the logs (no instances of it before that time):

qm_malloc(): qm_malloc(0x7f5ade9c0010, 536) called from rtpengine: bencode.c: __bencode_piece_new(79), module: rtpengine; Free fragment not found!

They don't only concern rtpengine, core has produced similar "free fragment not found" errors as well. There's additional multiple "had header field", "bad header" and "invalid header name" errors appearing after that too, but I'm guessing that's only a symptom of the qm_malloc issue?

kamailio is started with -m 2048 -M 16 and there's another instance with almost identical traffic and configuration, but running on 5.6.1, which has never exhibited such failures in several months uptime. So I'm wondering, is there anything in 5.6.2 that could explain this? Thanks!

Best regards,
George
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20221213/4af9b18a/attachment.htm>