[OpenSIPS-Devel] How to interpret the logs for memory status

[alexis.dacosta at bt.com]

Hello,

 

I reproduced the problem in the lab. You will find 2 another files:

- process.jpg

- openser.log

 

You have to indicate the full FTP URL to access to the files: ftp://ftpclient:clientcyber4ever@ftp.cyber-networks.fr/incoming/tmp/process.jpg

 

If you need anything else to find the leak memory, I can do more tests.

 

Thank you for your help,

 

Best regards,

--

Alexis DA COSTA 
BT Cyber Networks | T: 01 42 04 88 31 ou 88 10  | E: alexis.dacosta at bt.com| www.cyber-networks.fr <http://www.cyber-networks.fr/> 

 

________________________________

De : Da Costa,A,Alexis,JPENS R 
Envoyé : jeudi 18 décembre 2008 19:53
À : 'devel at lists.opensips.org'
Objet : How to interpret the logs for memory status

 

Hello,

 

Could you help me to interpret the logs for memory status?

 

I use Openser v1.3.1 (more details in memory_dump.txt) in order to proxy Presence flow and I may have detected a memory leak (cf. memory_leak.txt)

I sent you the result of a scenario with a sipp client.

I can upgrade to the lastest version of opensips if you say that I have to.

 

I put on the logs on the FTP server: ftp://ftpclient:clientcyber4ever@ftp.cyber-networks.fr/incoming/tmp/

- Config file: PRASVSIP01.cfg

- Memory log dump: memory_dump.txt, before scenario at 11:08 and after at 11:14

- memory leak log: memory_leak.txt

- sipp scenario: scenario.txt

- top command results: Top.txt

 

Thank you for your help,

 

Best regards,

--

Alexis DA COSTA 
BT Cyber Networks | T: +331 42 04 88 31 ou 88 10  | E: alexis.dacosta at bt.com| www.cyber-networks.fr <http://www.cyber-networks.fr/> 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.opensips.org/pipermail/devel/attachments/20081219/5d83b5ac/attachment-0001.htm