Jump to content

CURL error causes that players can not be authenticated and can not connect between the shards

Kova_

By Kova_

    • Pending

This issue happens at least twice per week while we host five servers with the shards. The problem is that all players can not connect to the other shard (the caves or the master). We can fix this problem only by restarting the server or waiting like an hour. 

---------------

I noticed this is the major issue (Master log): 

[22:35:29]: CURL ERROR: (login.kleientertainment.com) Operation too slow. Less than 5 bytes/sec transferred the last 60 seconds
[22:35:29]: [ValidateGameSessionTokenResponse] Network Failure (0)
[22:35:29]: CloseConnectionWithReason: ID_DST_GAME_SESSION_AUTH_FAILED
[22:35:38]: [Shard] Migration by user ('KU_SFlxL9Pf') failed (178).

and cave log:
  

[22:35:38]: [Shard] Migration for KU_SFlxL9Pf timed out.
[22:35:38]: [Shard] Cancelling pending migration #130 for (KU_SFlxL9Pf)
[22:35:38]: Registering master server in EU lobby

meanwhile client log:
  

[01:41:20]: Connection accepted to 188.94.79.145|14001 <8773861673417112171>
[01:41:20]: Network external address discovered: 92.6.106.166|65197
[01:41:20]: SendClientHandShakePacket to <8773861673417112171>
[01:41:46]: focus lost
[01:41:54]: focus gained
[01:41:55]: focus lost
[01:42:08]: focus gained
[01:42:09]: focus lost

---

Full master log: https://dontfight.club/test/master_bug_caves_log2.txt
Full caves log: https://dontfight.club/test/cave_bug_caves_log2.txt
Client log is in the attachment. However this one might be outdated.

client_log_2.txt

Steps to Reproduce

See the issue description.

Go to bugs

User Feedback


Kova_

CURL error happened even for the lobby listing server - aws/us... Restart again helped it but it is very annoying bug.

Share this comment

Link to comment
Share on other sites
Manngunner

To bump and add additional context: I have some logs and packet captures of this happening in real-time.

There appears to be a one minute delay from your server which you can see between packet 31 to 32.

This is happening more and more frequently. A resolution would be appreciated

capture.pcap log.txt

Share this comment

Link to comment
Share on other sites


Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...