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.

Sign up for GitHub

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

Jump to bottom

"allocation watchdog determined stale session state" very quickly #740

Open
s-dvd opened this issue Mar 27, 2021 · 1 comment
Open

"allocation watchdog determined stale session state" very quickly #740

s-dvd opened this issue Mar 27, 2021 · 1 comment

Comments

@s-dvd
Copy link

s-dvd commented Mar 27, 2021 •
edited
Loading

We have hosted coturn and found that with one user I am getting following error within a second

Mar 27 10:38:47 ip-172-31-35-194 turnserver: 5084: session 001000000000000076: usage: realm=<xxx.xxxx.xxxx>, username=<>, rp=2, rb=48, sp=2, sb=228 Mar 27 10:38:47 ip-172-31-35-194 turnserver: 5084: session 001000000000000076: closed (2nd stage), user <> realm <turn.100ms.live> origin <>, local 172.31.35.194:3478, remote 132.154.251.199:34176, reason: allocation watchdog determined stale session state

When I asked user to check the ip address it was showing ipv6 address however in the above message it is ipv4 address.
@misi
Copy link
Contributor

misi commented Apr 7, 2021

Interesting. Can you please send a packet capture about such case?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@misi @s-dvd