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

[6.X] LoginREST stucked "Couldn't bind to 0.0.0.0:8081" #16930

Closed
Palabola opened this issue Apr 10, 2016 · 2 comments
Closed

[6.X] LoginREST stucked "Couldn't bind to 0.0.0.0:8081" #16930

Palabola opened this issue Apr 10, 2016 · 2 comments
Assignees
@Shauren
Labels
Branch-master Feedback-WaitingResponse

Comments

@Palabola
Copy link
Contributor

Description:

I've done some stress test under Deb8 with our new Bnetserver, and found the following error sometimes after restarted it. I got the following error:

** Couldn't bind to 0.0.0.0:8081 **

After run net stat I explored the following on the 8081 port:

X.X.6.201:46675 TIME_WAIT

*Expected behaviour: *

We should close active connections on Bnetserver start, or close them on Bnetserver stop, or setup timeout limit.

Branch(es): 6.X

TC hash/commit: 05aa2c9

Operating system: Deb8 64Bit
@TrinityCoreBot TrinityCoreBot added the Invalid-IncompleteData/OrNotTrinityCore Reporter deleted parts or all template or he is using a 3rd party unsupported core. label Apr 10, 2016
@Aokromes Aokromes added Branch-master and removed Invalid-IncompleteData/OrNotTrinityCore Reporter deleted parts or all template or he is using a 3rd party unsupported core. labels Apr 12, 2016
@Palabola
Copy link
Contributor Author

After more diggin, I've found the timeout limit on 8081 port 60 seconds by default.

@Aokromes
Copy link
Member

this bug is still valid?

@Aokromes Aokromes closed this as completed Apr 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Shauren Shauren

Labels
Branch-master Feedback-WaitingResponse
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@Shauren @Aokromes @Palabola @TrinityCoreBot