16 Jun
2014
16 Jun
'14
10:19 a.m.
Hi,
I've got a 3.3.2 Kamailio that from time to time gets very upset and starts rushing
these log entries to syslog:
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
The rate is about 10000 lines per second.
This fills the log partition, which locks other things up and the users
are unhappy. The server recovers nicely if restarted. I have scarce
logs because I have to remove logs to get service back.
Any suggestions? More data on request.
--
Måns Nilsson primary/secondary/besserwisser/machina
MN-1334-RIPE +46 705 989668
HELLO, everybody, I'm a HUMAN!!
16 Jun
16 Jun
10:30 a.m.
Hello,
you can set the debug=1 to get rid of INFO log messages.
Do you do some reload command at the time of these logs?
Cheers,
Daniel
On 16/06/14 10:19, Måns Nilsson wrote:
Hi,
I've got a 3.3.2 Kamailio that from time to time gets very upset and starts rushing
these log entries to syslog:
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
Jun 16 10:12:18 landsort /usr/local/kamailio/sbin/kamailio[37542]: INFO: <core>
[mem/f_malloc.c:532]: freeing a free fragment (0x80a4fb370/0x80a4fb380) - ignore
The rate is about 10000 lines per second.
This fills the log partition, which locks other things up and the users
are unhappy. The server recovers nicely if restarted. I have scarce
logs because I have to remove logs to get service back.
Any suggestions? More data on request.
_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users(a)lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users
--
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda
12:16 p.m.
Subject: Re: [SR-Users] stampeeding server. Date: Mon, Jun 16, 2014 at 10:30:59AM +0200
Quoting Daniel-Constantin Mierla (miconda(a)gmail.com):
Hello,
you can set the debug=1 to get rid of INFO log messages.
Thanks. Reserving debug=2 for development.
Do you do some reload command at the time of these
logs?
No. It happens over the weekend, with only REGISTERs and INVITEs
(figuratively speaking, but..)
--
Måns Nilsson primary/secondary/besserwisser/machina
MN-1334-RIPE +46 705 989668
Place me on a BUFFER counter while you BELITTLE several BELLHOPS in the
Trianon Room!! Let me one of your SUBSIDIARIES!
8:31 p.m.
Subject: Re: [SR-Users] stampeeding server. Date: Mon, Jun 16, 2014 at 12:16:59PM +0200
Quoting Måns Nilsson (mansaxel(a)besserwisser.org):
Subject: Re: [SR-Users] stampeeding server. Date: Mon,
Jun 16, 2014 at 10:30:59AM +0200 Quoting Daniel-Constantin Mierla (miconda(a)gmail.com):
From reading another big log dump, this looks like the dialog module
going haywire, and I think it is related to incorrect configuration
rather than a bug. It might be buggy user agents too; our user agents
are not known for their mature SIP code...
The investigation is going on... Will post back.
--
Måns Nilsson primary/secondary/besserwisser/machina
MN-1334-RIPE +46 705 989668
YOW!! I'm in a very clever and adorable INSANE ASYLUM!!
Hello,
you can set the debug=1 to get rid of INFO log messages.
Thanks. Reserving debug=2 for development.
Do you do some reload command at the time of
these logs?
No. It happens over the weekend, with only REGISTERs and INVITEs
(figuratively speaking, but..)
3820
days inactive
3820
days old
3 comments
2 participants
participants (2)
-
Daniel-Constantin Mierla -
Måns Nilsson