Yes, it makes sense as the crash (on bogus mem ops) was related to an
invalid Contact URI in the SIP request.
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 18.05.2016 17:06, John Nash wrote:
OK. will update.Thank you. SIP message validate in
OK. will update.Thank you. SIP message validate in the script seemed to
have stopped this crash or its not related to that?
On Wed, May 18, 2016 at 5:51 PM, Bogdan-Andrei Iancu
wrote:
> Hi John,
>
> Thanks for the info, I managed to find the bug and have it fixed:
>
>
Hi John,
Thanks for the info, I managed to find the bug and have it fixed:
https://github.com/OpenSIPS/opensips/commit/4b0fca533cd7be4a45c1381c78f2b37aaba6152b
Please update from GIT and let me know if you still have the problem.
Best regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and
Hello Bogdan,
The version is Server:: OpenSIPS (2.1.2 (x86_64/linux))
Since this is live we do not have detailed debug. Below is what happened
before crash (We had multiple such entries). I figured it might be related
to malformed SIP message so I applied sipmsg_validate() function even for
so
Hi Nash,
What version of OpenSIPS are you using ? also, before that CRITICAL
message, do you see any other error messages in the logs ?
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
http://www.opensips-solutions.com
On 12.05.2016 08:46, John Nash wrote:
Actually crash happened
Actually crash happened shortly after we uploaded 11000 codes but looks
like it is not related to drouting. I see following message
CRITICAL:topology_hiding:build_encoded_contact_suffix: #012>>> pkg_free()
on non-pkg ptr 0x18 - aborting!#012#012It seems you have hit a programming
bug.#012Please
I have been using drouting module with just 200 entries from 8 months
yesterday we had need of adding around 11000 entries in rules table but
after that opensips started to crash. I am currently using -m 2048 -M 1024
isn't it enough memory?
How can I anticipate memory usage?
John