[SR-Users] Memory leak or bad setting.

[Kjeld Flarup]

Hi Daniel

Just to confirm that 4.2.4 indeed solved the problem.
Thanks for your time.

Med venlig hilsen / Best regards
Kjeld Flarup (Christensen) M.Sc E.E, Teknisk chef 
Viptel ApS, Benslehøjvej 3, DK-7470 Karup J
Telefon: +45 46949949, Telefax: +45 46949950, http://viptel.dk

On 2015-05-08 16:31, Daniel-Constantin Mierla wrote:
> Hello,
>
> it is recommended to upgrade to latest 4.2.x -- there were some fixes
> since version 4.2.1. The same configuration file and database structure
> works for all 4.2.x, therefore just deploy the newer 4.2.x like you did
> with 4.2.1 and just restart.
>
> After upgrade, if you still see decrease of pkg free memory, let us know
> to investigate further.
>
> Cheers,
> Daniel
>
> On 08/05/15 16:01, Kjeld Flarup wrote:
>> Hello
>>
>> We experienced a failure on our kamailio (4.2.1+trusty), which required
>> a restart.
>> May  6 07:40:41 rtpproxy01 /usr/sbin/kamailio[5467]: ERROR: <core>
>> [msg_translator.c:2270]: generate_res_buf_from_sip_res(): out of mem
>>
>> Afterwards we inspected all the settings to be using default, but at a
>> much higher level than an other older kamailio which runs much more traffic.
>>
>> The big difference, is that this kamailio works with rtpengine. Does
>> that require more memory?
>>
>> We also observed that the free memory is constantly falling on some
>> instances. They all started with 16MB but after 1½ day some are on 11.6
>> Is this normal behaviour that will find a natural level or is there
>> something bad going on?
>>
>> We can also see that there are frags. Is that to be worried about, or is
>> this natural?
>>
>> kamcmd pkg.stats | egrep -e 'free|frag'
>> 	free: 16362760
>> 	total_frags: 17
>> 	free: 15835176
>> 	total_frags: 232
>> 	free: 15845760
>> 	total_frags: 205
>> 	free: 15829288
>> 	total_frags: 188
>> 	free: 15847456
>> 	total_frags: 181
>> 	free: 15853024
>> 	total_frags: 183
>> 	free: 15873232
>> 	total_frags: 225
>> 	free: 15858584
>> 	total_frags: 231
>> 	free: 15834592
>> 	total_frags: 205
>> 	free: 15852520
>> 	total_frags: 132
>> 	free: 15869048
>> 	total_frags: 120
>> 	free: 15824872
>> 	total_frags: 100
>> 	free: 15828448
>> 	total_frags: 113
>> 	free: 15858216
>> 	total_frags: 109
>> 	free: 15861992
>> 	total_frags: 82
>> 	free: 15871712
>> 	total_frags: 110
>> 	free: 15813824
>> 	total_frags: 109
>> 	free: 11583736
>> 	total_frags: 121
>> 	free: 11588896
>> 	total_frags: 106
>> 	free: 11580448
>> 	total_frags: 118
>> 	free: 11586312
>> 	total_frags: 134
>> 	free: 11592840
>> 	total_frags: 159
>> 	free: 11632536
>> 	total_frags: 120
>> 	free: 11582368
>> 	total_frags: 127
>> 	free: 11660104
>> 	total_frags: 97
>> 	free: 16352192
>> 	total_frags: 14
>> 	free: 16351088
>> 	total_frags: 13
>> 	free: 16341248
>> 	total_frags: 46
>> 	free: 16351184
>> 	total_frags: 19
>>
>> We use 4.2.1+trusty with these modules, is it possible that a newer
>> version has fixed some memory leak?
>>
>> loadmodule "db_mysql.so"
>> loadmodule "mi_fifo.so"
>> loadmodule "kex.so"
>> loadmodule "tm.so"
>> loadmodule "tmx.so"
>> loadmodule "sl.so"
>> loadmodule "rr.so"
>> loadmodule "pv.so"
>> loadmodule "maxfwd.so"
>> loadmodule "textops.so"
>> loadmodule "siputils.so"
>> loadmodule "xlog.so"
>> loadmodule "sanity.so"
>> loadmodule "ctl.so"
>> loadmodule "mi_rpc.so"
>> loadmodule "acc.so"
>> loadmodule "dispatcher.so"
>> loadmodule "permissions.so"
>> loadmodule "sdpops.so"
>> loadmodule "rtpengine.so"
>>