Jump to content

Player kicked for invalid login - MAJOR UPDATE ON THIS ISSUE


Recommended Posts

I feel that my findings warrant the starting of a new thread, I leave it to the moderators to delete/merge this thread if they don't agree.


I have a MAJOR UPDATE about this issue. The thought occurred to me last night that maybe we are looking at the chicken/egg from the wrong angle, and maybe the client is crashing first, causing the server to give us the kicking player message erroneously? To test this, I joined the server, and then forcibly terminated the client. I did this several times, and in every case, immediately AFTER I forcibly terminated the client, the server gave the kicking player message.


Here is a lot of one such test:


At 12:30:24 I joined the server. At 12:31:02 I entered the server. It's about a 30 second process, give or take, to actually spawn once you make the connection attempt.


At 12:31:14 I forcibly terminated the client process.


ONE SECOND LATER You get the messages about kicking player for invalid login steam auth failed blah blah blah.


This is a very misleading message! it leads one to think that the player was kicked because their steam auth failed, when in fact it's the other way around. Their client crashed, and this is how the server removes the player from the server.


First of all my apologies to TFP for going on and on about this issue. Looks like I was wrong (yes, dear, you can write that in your journal - I was wrong :) ).


The problem appears to be that the game just crashes. A lot. And when it does, we get this message in the console that leads us down the wrong rabbit hole.



This is the log from this:


2018-01-02T12:30:24 259.606 INF [NET] PlayerConnected EntityID=-1, PlayerID='', OwnerID='', PlayerName=''

2018-01-02T12:30:24 259.809 INF PlayerLogin: Ook/Alpha 16.4

2018-01-02T12:30:24 259.809 INF Client IP:

2018-01-02T12:30:24 259.809 INF [steamworks.NET] Auth.AuthenticateUser()

2018-01-02T12:30:24 259.809 INF [steamworks.NET] Authenticating player: Ook SteamId: 76561197960378421 TicketLen: 1024 Result: k_EBeginAuthSessionResultOK

2018-01-02T12:30:24 260.009 INF [steamworks.NET] Authentication callback. ID: 76561197960378421, owner: 76561197960378421, result: k_EAuthSessionResponseOK

2018-01-02T12:30:24 260.009 INF Steam authentication successful, allowing user: EntityID=-1, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:30:24 260.009 INF Allowing player 12:31:15with id 76561197960378421

2018-01-02T12:30:25 260.762 INF RequestToEnterGame: 76561197960378421/Ook

2018-01-02T12:30:34 269.216 INF RequestToSpawnPlayer: 172, Ook, 12

2018-01-02T12:30:34 269.221 INF Created player with id=172

2018-01-02T12:30:34 269.225 INF Player connected, entityid=172, name=Ook, steamid=76561197960378421, steamOwner=76561197960378421, ip=

2018-01-02T12:30:34 269.225 INF Player set to online: 76561197960378421

2018-01-02T12:30:50 285.754 INF Time: 4.53m FPS: 21.02 Heap: 549.0MB Max: 549.0MB Chunks: 1109 CGO: 9 Ply: 2 Zom: 0 Ent: 2 (6) Items: 0 CO: 2 RSS: 1309.5MB

2018-01-02T12:31:02 297.731 INF GMSG: Player 'Ook' joined the game

2018-01-02T12:31:02 297.732 INF PlayerSpawnedInWorld (reason: JoinMultiplayer, position: -1306, 51, 200): EntityID=172, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:31:15 310.653 INF [steamworks.NET] Authentication callback. ID: 76561197960378421, owner: 76561197960378421, result: k_EAuthSessionResponseAuthTicketCanceled

2018-01-02T12:31:15 310.653 INF [steamworks.NET] Kick player for invalid login: 76561197960378421 Ook

2018-01-02T12:31:15 310.653 INF Kicking player (Steam auth failed: k_EAuthSessionResponseAuthTicketCanceled): EntityID=172, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:31:16 311.200 INF Player set to offline: 76561197960378421

2018-01-02T12:31:16 311.201 INF Player disconnected: EntityID=172, PlayerID='76561197960378421', OwnerID='76561197960378421', PlayerName='Ook'

2018-01-02T12:31:16 311.201 INF GMSG: Player 'Ook' left the game

2018-01-02T12:31:20 315.758 INF Time: 5.03m FPS: 36.25 Heap: 524.9MB Max: 549.0MB Chunks: 1109 CGO: 9 Ply: 1 Zom: 0 Ent: 1 (7) Items: 0 CO: 1 RSS: 1309.6MB

2018-01-02T12:31:50 345.774 INF Time: 5.53m FPS: 21.70 Heap: 581.7MB Max: 581.7MB Chunks: 1109 CGO: 9 Ply: 1 Zom: 0 Ent: 1 (7) Items: 0 CO: 1 RSS: 1309.6MB


- - - Updated - - -


PS: I did this on Linux, not Windows. To terminate the client, I killed the process SteamApps/common/7 Days To Die/7DaysToDie.x86_64 via the kill -KILL command in the console, which forced the client to immediately terminate.

Link to comment
Share on other sites

I realized today that those reporting this to me are running on Linux. I'm going to play on the Windows version for a while and see if the same thing happens. It's possible that the LInux version has a crash bug that the Windows version does not (it's also possible they are both equal opportunity crashers and it won't make any difference)

Link to comment
Share on other sites

Good on ya Zootal. Yeah, think I read that Ook runs slackware. Probably already been said elsewhere, but make certain the crashing clients have disabled the Steam in-game overlay (pretty standard problem with most graphic overlays, not just Steam's). If that doesn't help, client should toggle on GLCore Renderer (or remove GLCore if it is already enabled).

Link to comment
Share on other sites


This topic is now archived and is closed to further replies.

  • Create New...