Login denial (Already logged in) for non-existing instance

[PepeAmpere]

Some of notAlab SPADS autohosts running on amazon AWS are constantly logged-in (based on SPADS report) no matter computer running the instances was off for 9 days.

Code: Select all

"ERROR    - [SPADS] Login denied on lobby server (Already logged in.)"

So next accounts are considered to be logged-in and there is no way how to force them to be offline (from the perspective of the lobby server) and get back the control over them:

• notAspace010
• notAspace011
• s44notAhost002
• KPPnotAhost002

Strange is there are multiple other accounts which were running on the same machines and they are not experiencing the same problem.

Can we ask for logging-off those accounts, check some logs and maybe suggest some solution to prevent this to happen?

Btw, the server which was running the autohosts was restarted with all instances running - so the ending of the instances was not standard - but the problem is that lobby server is still considering some of the accounts logged in.

[abma]

i checked logs for notAspace010:

2016-12-09T20:37:30 Client connected from <ip>:59590, session ID 419060.
2016-12-09T20:38:38 Client disconnected from <ip>, session ID was 419060: Connection timed out, didn't login
2016-12-09T20:38:38 Handler 0:419060 Successfully logged in user <notAspace010> (access=user).
2016-12-09T20:38:38 Handler 0:419060 <notAspace010> client "SPADS v0.11.41" missing compat flags: cl p

it seems it triggered a bug in the lobby server: the client timed out but sucessfully logged in. I've kicked the users you listed from the lobbyserver, so they should be able to reconnect.

[PepeAmpere]

Thanks for the fix of the accounts, abma.

I guess someone has to fix the lobby server, but im too noob for this.