Skip to content
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

turnc ERROR Fail to refresh permissions: all retransmissions failed for xxx #384

Open
SijmenHuizenga opened this issue Jan 22, 2024 · 6 comments

Comments

@SijmenHuizenga
Copy link
Contributor

Our application that uses the livekit go server-sdk is spitting out a tsunami of Fail to refresh permissions: all retransmissions failed for error messages. At some point hundreds of these messages per hour. Note that this application is handling multiple multiple livekit rooms at the same time, each with 1-5 video streams & 2 audio streams.

image

The error seems to originate from the pion turn project, which is used by Pion Webrtc. From what I read in the the code of pion turn, it seems this error happens when the turn server does not respond to the turn createpermission request. Since were not seeing any failed to refresh allocation messages, my guess is that somehow the TURN connection is still alive? It's weird.

I cannot see anything weird in the actual video streams. But I'm worried that these errors are a sign of a leftover connection or something that's not cleaned up properly.

@SijmenHuizenga
Copy link
Contributor Author

This is still an issue. At this time we are seeing this error continuously, about 13000 times per day.

@davidzhao
Copy link
Member

sorry we have not had a chance to look into this one. thanks for the heads up.

@SijmenHuizenga
Copy link
Contributor Author

We are still seeing about 19k of these errors every day.

Could anyone maybe point me into the direction of where to start debugging? I'm happy to add extra logs or do some experimentation. But I have no idea where to even start looking. Guidance would be much appreciated.

@SijmenHuizenga
Copy link
Contributor Author

We are now at ~43k of these error messages every day. The growth may be related to our grows in number of rooms & tracks.

@kristian1108
Copy link

+1, not sure if this is impacting anything, but there are ton of these errors in the logs

@lukmandev
Copy link

lukmandev commented Dec 12, 2024

'+' 1, we facing the same error

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants