-
Notifications
You must be signed in to change notification settings - Fork 584
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OpenSIPS 3.3.4 crashes intermittently #3547
Comments
Any updates here? No progress has been made in the last 15 days, marking as stale. Will close this issue if no further updates are made in the next 30 days. |
Hi @baevga. The backtrace indicates some memory corruption, but there are not hints about the actual point/module where the corruption happens. To help troubleshooting this, please see this tutorial on how to enable the memory debugging (no logging needed). Once the mem debugging is on, OpenSIPS will report whenever coming across a memory corruption. |
Hi @bogdan-iancu, I’ve enabled QMALLOC_DBG and obtained the following trace: https://pastebin.com/LVK7AdVn. Could you please take a look at it? If there’s anything specific you’d like me to check in the core dump, please let me know, and I’ll be happy to assist. Thank you in advance for your help! |
You had some "CRITICAL"log before the shutdown.... Even if the backtrace does not show a "stop" in the memory debugger (due to the detection of a mem corruption).... |
Yes, i have a critical record but nothing more:
And after that, it rebooted itself and continued working. One more thing REGISTER request that was passed to t_relay() wasn't sent out. |
Unfortunately this new point of crash is not related to the memory manager (and its consistency checks). So no clue. Rather keeping the memory debugger ON and hoping to catch something at a point. |
Understood. Previously, we encountered this issue on version 3.5, so we kindly request that this issue remains open. I will update our instances to version 3.5, attempt to reproduce the crash, and provide updates here. |
If it's a different version, I would strongly recommend opening a new report, with the new version and new info. What was already discussed here will be irrelevant while moving to 3.5 |
Ok, then i will open a brand new issue when gather info relevant to OpenSIPS v3.5. Thank you for assist! |
Hi @bogdan-iancu, I hope you're doing well! It seems I’m unable to reproduce the issue on version 3.5 because, after updating OpenSIPS, I encountered the exact same problem described in this ticket: #3542. This issue is currently blocking our update. Could you please take a look at it? Thank you in advance! |
Hello OpenSIPS team!
We facing with crashes OpenSIPS v3.3.4 sometimes.
Please, look into this coredump file - https://pastebin.com/9f9i6BSN
Steps to reproduce the behavior:
OS/environment information
The text was updated successfully, but these errors were encountered: