Hi Marcello,
I haven;t looked on the yesterday log, but this from today doesn't look
from the timer process ...please confirm this..
Anyhow, the dump does not show any mem leak. Just probably a large
script and a lot of avps/var used :)..
Please check if it is really the timer process (use "openserctl ps" to
check it ). Also wait for the error from the timer process (for pkg mem).
regards,
bogdan
Marcello Lupo wrote:
Hi Bogdan,
i don't know if you got the time to analyze the log i sent you
yesterday but today i have another log of memory from one process in
out of memory that is not the timer process.
It is at:
http://82.193.22.211/log_memory_leak_20070904.txt
It is in out of pkg memory. Can you check it can be memory leak or not??
Anyway i increaased the pkg memory to 4 Mb and recompiled this morning.
Thank You,
Bye,
Marcello
Bogdan-Andrei Iancu wrote:
Well....there is no such documentation for how to
dimension private
memory due nat ping....normally the default memory should be quite
enough for couple of Ks of pings.....but probably it depends of what
other modules/services you are running (so what other private mem
consumers you have)....
use the memory debugger to see if there is a mem leak in the private
mem of the timer process....if you need help with this, let me know.
Regards,
Bogdan
Marcello Lupo wrote:
> Hi Bogdan,
> i left the values as default.
> I read that section you suggested to me already last time that i got
> memory leak, if you remember.
> I didn't found, probably i didn't searched well, specification on
> how to dimension my private memory based on usrloc entry to do
> natping. If you have something to point me at...
> Thank you in the meanwhile.
> Bye,
> Marcello
>
> Bogdan-Andrei Iancu wrote:
>> Hi Marcello,
>>
>> see the memory troubleshooting section on wiki to try to get an
>> idea why the private memory is not enough. Is is a memory shortage
>> (how much mem do you configured)? or is it a mem leak?
>>
>> Regards,
>> Bogdan