Zupperrr...I remember I saw this backtrace before, but without the
ability to reproduce it.
Do you have OpenSIPS locally compiled or installed from packages ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 20.09.2016 20:22, Richard
just made one for you.
http://pastebin.com/HJkwuTDc
I'd ramped this up to 800cps and the recieving asterisk was
struggling crashed 5 times and autorestarted before i could ramp
down the sipp
On 20/09/2016 08:51,
Hi Bogdan,
I'll try and get that for you tomorrow.
Regards,
Richard
On 20/09/2016 08:51, Bogdan-Andrei Iancu wrote:
Hi Richard,
If not too much for you, I would really like to see the
Hi Richard,
If not too much for you, I would really like to see the backtrace - even
under OS stress conditions, OpenSIPS should NOT crash.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 16.09.2016 13:15, Richard Robson wrote:
Hi
Hi Bogdan,
It looks like it was the extra logging we were putting in using
xlog. We'd added them while we were developing the script and left
them in. this was causing systemd-journald to max out the box and
would segfault the opensips, which restarted.
Hi Richard,
Have you managed to get a corefile and extract a backtrace ?
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 06.09.2016 17:07, Richard Robson wrote:
If its any help, I can see packets coming in particularly BYEs that
are not
