Kicking XXX because they didnt logon to the game
#1

Hi, sorry for my english:

I have this problem if someone connect to my server

Code:
[16:39:03] BAD RCON ATTEMPT BY: 114.79.16.167
[16:41:25] Incoming connection: 82.170.242.242:14888
[16:41:43] Incoming connection: 83.154.33.106:58100
[16:41:55] Kicking 82.170.242.242 because they didn't logon to the game.
[16:42:13] Kicking 83.154.33.106 because they didn't logon to the game.
[16:43:26] Incoming connection: 189.94.155.146:53860
[16:43:56] Kicking 189.94.155.146 because they didn't logon to the game.
[16:45:35] BAD RCON ATTEMPT BY: 114.79.16.167
[16:49:00] BAD RCON ATTEMPT BY: 114.79.16.167
[16:50:50] Incoming connection: 79.180.138.161:1579
[16:51:20] Kicking 79.180.138.161 because they didn't logon to the game.
[16:53:54] Incoming connection: 194.166.44.11:58910
[16:54:24] Kicking 194.166.44.11 because they didn't logon to the game.
[18:18:53] Incoming connection: 178.51.34.127:51163
[18:19:23] Kicking 178.51.34.127 because they didn't logon to the game.
[19:26:24] Incoming connection: 194.166.44.11:60140
[19:26:54] Kicking 194.166.44.11 because they didn't logon to the game.
[20:46:17] BAD RCON ATTEMPT BY: 92.84.190.137
[23:18:26] Incoming connection: 94.226.103.28:55131
[23:18:56] Kicking 94.226.103.28 because they didn't logon to the game.
[00:49:05] Incoming connection: 69.80.23.113:51107
[00:49:06] Incoming connection: 69.80.23.113:60791
[00:49:35] Kicking 69.80.23.113 because they didn't logon to the game.
[00:49:36] Kicking 69.80.23.113 because they didn't logon to the game.
[00:50:15] Incoming connection: 69.80.23.113:61448
Now there are constant 3 players on server (since 24 hours), nobody can connect (see serverlog) because they didnt logon to the game.

If i restart the server it works for some hours, then the same problem.
What should I do?

OS: Debian 6.0.7
Reply
#2

https://sampforum.blast.hk/showthread.php?tid=413146
Reply
#3

I read this, but i dont find a solution in this thread
Reply
#4

Please help.. What should I do? Change the OS?
Now I have Debian
Reply
#5

I've had this issue before, there was an infinite loop in my script, so it's most likely your script that's causing this problem.
Reply
#6

And where can I find the infinite loop?
Reply
#7

What should I do now?
Reply
#8

++++push
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)