forums.smartfoxserver.com

INFO | jvm 1 | 2011/08/23 15:01:24 | 15:01:24.040 - [ INFO ] > Problems with Force-Login, Could not disconnect old user: 1:100000480437238

INFO | jvm 1 | 2011/08/23 15:01:24 | 15:01:24.040 - [ INFO ] > User: 1:100000480437238 is already logged in Zone: vslotZ

INFO | jvm 1 | 2011/08/23 15:01:24 | INFO: Problems with Force-Login, Could not disconnect old user: 1:100000480437238


This problem causes many players not being able to log back to the game.
Some how a ghost user stays online, and blocking the user from login back in.

The user has reported that he wasn't able to log in for the past 5 days.
We have checked the logs and found out these messages.

What can we do to solve this issue?

thank you.

server patch 1.6.9 everything is updated up to date.
I have also tried to manually kick the user and it did not work.
with the admin tool

This is one of those things that is pretty hard to reproduce and debug, we would need more info. Anyways another way to approach it is to force the user out somehow even if the server didn't get a disconnection event.

The problem is, we should at least know if the connection for this user is still open at the level of the OS. If so that would explain many things although it would make it pretty difficult to create a system that eliminates this ghosts automatically. One would need to go and remove them manually.

If you connect with the AdminTool can you see this user in the Room user list? Do you also see his remote address? If so you can then check via netstat if that remote address is still seen as active in your server,at the TCP level

Thanks for the reply,

As the Admin tool lacks an option to search users by username,
I cannot locate this user on the admin tool as we have got more than 6K onlines users and hundreds of rooms.

I will make custom command that retrieve user information.
Will let you know what i could find out.


Maybe you could fire some error event that we can catch on the server side when this kind of thing happen. then i could easily kill the socket once this happens.
Would be an ok work around.