Hi Dave,
The core files do not help as they need to be investigated with your
binaries. Please run gdb path_to_executable path_to_corefile and then
run 'bt full' and send the output.
Regards,
--
Anca Vamanu
www.voice-system.ro
On 10/21/2010 10:08 PM, Dave Singer wrote:
On my production servers, both 1.6.2 and 1.6.3 versions of opensips,
almost every time I restart opensips it creates a core dump. Since I'm
giving it 2GB shared mem, it takes a little while to write the core to
disk and start running again.
So a couple questions.
1. Am I giving it more memory than it needs? Judging by how much the
core dump compressed probably way to much. I'm running about 30 calls
per sec with up to 1000 active calls. Calls are using mediaproxy with
engage and thus also dialog. I did run into memory shortage problems
before I explicitly upped it to 2GB with -m 2000 on the cmd line for
starting opensips.
2. Can someone look at the core dump(s) or let me know what/how to
look at them? The 2GB core dumps compressed very small and are
accessible via http:
opensips-1.6.2-notls.core.gz 6MB
<http://viper.wideideas.net/opensips-1.6.2-notls.core.gz>
opensips-1.6.3-tls_1.core.gz 2MB
<http://viper.wideideas.net/opensips-1.6.3-tls_1.core.gz>
opensips-1.6.3-tls_2.core.gz 2MB
<http://viper.wideideas.net/opensips-1.6.3-tls_2.core.gz>
Thanks for any help or suggestions.
Dave
_______________________________________________
Users mailing list
[email protected]
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
