-
Notifications
You must be signed in to change notification settings - Fork 565
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
[CRASH] opensips 3.1 crashes in drouting.so module (and in proto_bin.so too) #2581
Comments
@kertor , in corefile 2357093, in frame 0, I assume the carrier ID Also, still in frame 0, could you try to print this |
Hello @bogdan-iancu ! Thank you for quick response.
Yes, all looks correct, and partition looks good too:
Can not get info about requested data:
|
sorry, here output:
|
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. |
thank you @kertor ! As I see it, on the freshly restarted openSIPS, there is a kind of race condition between (a) loading the routing data from DB and (b) already receiving the sync info from the cluster (with the status of the GWs). If the (b) is faster, the dr data will by NULL (not yet loaded). |
@kertor, could you try this small patch:
|
Thank you @bogdan-iancu! |
@bogdan-iancu Tests looks good, problem was fixed. Thank you! |
Be sure we trigger the startup cluster sync AFTER loading the data from DB. Also, when receiving replicated data, be sure the data is actually loaded. Closes #2581
Thank you @kertor !! |
OpenSIPS version you are running
Crash Core Dump
https://disk.yandex.ru/d/3orUt-QRLvJVtg
Describe the traffic that generated the bug
Usual calls. Crash happened after opensips restart.
To Reproduce
Configured drouting replication between opensips nodes:
Steps to reproduce:
Relevant System Logs
OS/environment information
Additional context
Thank you for checking!
The text was updated successfully, but these errors were encountered: