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

Message read error in one match closing all server authoritative matches. #636

Closed
ragavendranbala opened this issue Jul 4, 2021 · 2 comments

Comments

@ragavendranbala
Copy link

I'm facing issues like

"websocket: close 1006 (abnormal closure): unexpected EOF"

"read tcp 172.20.0.3:7350->106.206.240.93:44654: i/o timeout" (Attached Log files)
Say there are 5 matches running on my server and if one of the match faced these type of issue. it closing all the matches and which are not affected (other 4 matches).

I have raised the issue in forum and waiting for update for a couple of weeks.

I have attached Docker compose file and Config file. Kindly check this

Docker Copmpose and config.zip

logfile.log

@Ragavendran-DX
Copy link

More info :
Unity : 2020.3.12
Nakama Unity Version : 2.9.5
Server version: 20a55b5+20a55b5f

And Same issue on [v3.4.0]

@sesposito
Copy link
Member

@ragavendranbala I've taken a look at the provided files and the only thing I can infer is that the client seems to be terminating the connection unexepectedly, this could be just bad logic on the client side.

I don't see how the error you're describing would terminate multiple matches uness there's some issue with your match handler code.

Either way I cannot reproduce, so I'll be closing this issue for the time being.

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

3 participants