-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[1.x] Janus server stalls at rooms_mutex lock in janus_videoroom.c #3478
Comments
Please test master, there have been a ton of fixes recently on potential deadlocks. |
videoroom.c code is almost same inmy version too. anyways, we will try to check latest master as well. Thanks |
@ramprakash110109 any update? |
We have pulled latest master and using it for past 2 weeks. We have not
faced any issues till now.
Thanks
…On Thu, 12 Dec 2024 at 5:20 PM, Lorenzo Miniero ***@***.***> wrote:
@ramprakash110109 <https://github.com/ramprakash110109> any update?
—
Reply to this email directly, view it on GitHub
<#3478 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGAOGAGEXRO3MRPCUH7HY2L2FF2AFAVCNFSM6AAAAABR274JKKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZYGY4DKNBVGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
We have been running janus-gateway v1.3.0 for ~1 month, and we occasionally get similar behavior to this one. Randomly, one of our instances stops responding to all HTTP requests, for example:
Instances keep failing from time to time, so it's possible that we can reproduce the issue. I'm not sure this is the same issue as this ticket. Do you have any suggestions for us on debugging it or providing more data? Thank you! |
The usual steps for similar issues:
|
What version of Janus is this happening on?
v1.2.1
Have you tested a more recent version of Janus too?
No, since it was a rare issue and unable to reproduce again
Was this working before?
This is the second time I am facing this issue in past 6 months
Is there a gdb or libasan trace of the issue?
https://pastebin.com/eVLkvU3H
Additional context
Sessions were running smoothly for more than 3 months.
But suddenly, threads seems to get locked and no http requests or rmq requests were processed in mediaserver.
When I debugged, I came to know that rooms_mutex lock was not unlocked in one of the previous request. But I was unable to find the exact request which caused this issue.
I have pasted the debug_lock output where I hit new http request after the mediaserver gets locked due to some previous request.
I suspect one of the stop_rtp_forward request could have caused this. But I am not sure.
Could you please guide on this?
The text was updated successfully, but these errors were encountered: