Re: Kicking X because they didn't logon to the game. -
Neil. - 27.02.2013
Got this from my logs
[15:11:53] Kicking 124.6.181.215 because they didn't logon to the game.
[15:12:20] Incoming connection: *.54.91.*:64259
[15:12:20] Incoming connection: *.194.230.*:52585
[15:12:50] Kicking *.54.*.5 because they didn't logon to the game.
[15:12:50] Kicking *.194.*.243 because they didn't logon to the game.
[15:12:52] Incoming connection: *.6.181.*:10948
[15:13:22] Kicking *.6.181.215 because they didn't logon to the game.
[15:13:37] Incoming connection: *.54.91.*:65107
[15:13:37] Incoming connection: *.194.230.*:52589
[15:13:38] Incoming connection: *.168.1.*:60405
[15:13:44] Incoming connection: *.168.1.*:60406
[15:14:07] Kicking *.54.*.5 because they didn't logon to the game.
[15:14:07] Kicking *.194.*.243 because they didn't logon to the game.
[15:14:07] Incoming connection: *.6.181.*:13320
[15:14:17] Incoming connection: *.168.*.1:65224
[15:14:18] * JustinMethod(1) left the server (Quit)
[15:14:18] [part] JustinMethod has left the server (1:1)
[15:14:18] * I_Love_Carmella(0) left the server (Quit)
[15:14:18] [part] I_Love_Carmella has left the server (0:1)
[15:14:18] (1) Invalid client connecting from *.54.91.5
[15:14:18] (1) Invalid client connecting from *.194.230.243
[15:14:18] (1) Invalid client connecting from *.6.181.215
[15:14:18] (1) Invalid client connecting from *.54.91.5
[15:14:18] (1) Invalid client connecting from *.194.230.243
I happen to have found these in my logs. (Censored the ips btw)
I use the following plugins (If it helps): mysql streamer Whirlpool sscanf regex nativechecker crashdetect
Re: Kicking X because they didn't logon to the game. -
Essle - 27.02.2013
Used function
mysql_ping() ?
Re: Kicking X because they didn't logon to the game. -
MicroSof - 09.03.2013
Mesmo problema
Code:
[19:01:11] Incoming connection: 200.97.221.217:63160
[19:01:11] Incoming connection: 201.9.237.17:55857
[19:01:11] Incoming connection: 187.64.124.81:54943
[19:01:11] Incoming connection: 187.41.132.244:52424
[19:01:11] Incoming connection: 200.97.221.217:63161
[19:01:11] Incoming connection: 201.9.237.17:55858
[19:01:11] Incoming connection: 187.64.124.81:54944
[19:01:11] Incoming connection: 187.41.132.244:52425
[19:01:11] Incoming connection: 200.97.221.217:63162
[19:01:11] Incoming connection: 201.9.237.17:55859
[19:01:11] Incoming connection: 187.41.132.244:52426
[19:01:11] Incoming connection: 201.9.237.17:55860
[19:01:11] Incoming connection: 187.41.132.244:52427
[19:01:11] Incoming connection: 201.9.237.17:55861
[19:01:11] Incoming connection: 187.41.132.244:52428
[19:01:11] Incoming connection: 201.9.237.17:55862
[19:01:11] Incoming connection: 187.41.132.244:62181
[19:01:11] Incoming connection: 187.41.132.244:62182
[19:01:11] Incoming connection: 187.41.132.244:62183
[19:01:11] Incoming connection: 187.41.132.244:62184
[19:01:11] Incoming connection: 187.41.132.244:62185
[19:01:11] Incoming connection: 187.41.132.244:62186
[19:01:11] Blocking 187.41.132.244 due to a 'server full' attack (1)
[19:01:11] Incoming connection: 201.9.237.17:55863
[19:01:11] Incoming connection: 201.9.237.17:55864
[19:01:41] Incoming connection: 187.64.124.81:56928
[19:01:43] Incoming connection: 187.64.124.81:55983
[19:02:03] Incoming connection: 201.9.237.17:55866
[19:02:11] Kicking 187.64.124.81 because they didn't logon to the game.
[19:02:44] Incoming connection: 187.64.124.81:61182
[19:03:07] Incoming connection: 201.58.212.204:3367
Re: Kicking X because they didn't logon to the game. -
CoaPsyFactor - 26.03.2013
I have same problem, there are some problems with MySQL I post it
here but that is not problem.
Here is part of server_log.txt
Code:
[17:19:50] Command successfull Bosna_Speed(3) - [/help]
[17:19:57] Command successfull Tom_Back(0) - [/b /withdraw]
[17:19:58] Command successfull Bosna_Speed(3) - [/withdraw]
[17:20:14] [chat] [Bosna_Speed]: ee
[17:20:18] [chat] [Bosna_Speed]: mogu je uzeti
[17:20:25] Command successfull Bosna_Speed(3) - [/B mogu je uzeti]
[17:20:29] Command successfull Tom_Back(0) - [/a ovaj Bosna Speed ce otvoriti srw moramo paziti da nam neodvuce igrace]
[17:20:33] Command successfull Bosna_Speed(3) - [/business buy]
[17:21:16] Command successfull Bosna_Speed(3) - [/business buy]
[17:21:25] Command successfull Tom_Back(0) - [/b g]
[17:21:33] [chat] [Bosna_Speed]: i sada ce mi pare dolaziti
[17:21:40] Command unsuccessfull Bosna_Speed(3) - [/Bi sada ce mi pare dolaziti]
[17:21:44] Command successfull Bosna_Speed(3) - [/B i sada ce mi pare dolaziti]
[17:21:52] Incoming connection: 178.77.3.158:3211
[17:21:53] [join] Marin_Milkovic has joined the server (2:178.77.3.158)
[17:22:04] Command successfull Tom_Back(0) - [/b koliko jos imas para]
[17:22:04] [part] Marin_Milkovic has left the server (2:0)
[17:22:07] Incoming connection: 84.41.123.120:2197
[17:22:08] [join] Srbija_Speed has joined the server (2:84.41.123.120)
[17:22:13] [chat] [Bosna_Speed]: 315
[17:22:16] Incoming connection: 5.133.151.49:14441
[17:22:23] Incoming connection: 178.77.3.158:3212
[17:22:46] Kicking 5.133.151.49 because they didn't logon to the game.
[17:22:53] Kicking 178.77.3.158 because they didn't logon to the game.
[17:23:07] Incoming connection: 84.41.123.120:2198
[17:23:13] Incoming connection: 5.133.151.49:14442
[17:23:37] Kicking 84.41.123.120 because they didn't logon to the game.
[17:23:43] Kicking 5.133.151.49 because they didn't logon to the game.
[17:24:26] Incoming connection: 46.35.146.57:20492
[17:24:56] Kicking 46.35.146.57 because they didn't logon to the game.
[17:28:32] Incoming connection: 93.143.164.193:1307
[17:29:02] Kicking 93.143.164.193 because they didn't logon to the game.
But I figure it out, that is while causing problem, some infinitive loop I guess
Re: Kicking X because they didn't logon to the game. -
ProShooter22 - 20.04.2013
i have the same problem help!
Re: Kicking X because they didn't logon to the game. -
ProShooter22 - 23.04.2013
wtf? no one can solve this ?
Re: Kicking X because they didn't logon to the game. -
EpicGuy - 23.04.2013
This happens with me before 1 year ago. and i just bought new laptop...
Re: Kicking X because they didn't logon to the game. -
ProShooter22 - 23.04.2013
Quote:
Originally Posted by EpicGuy
This happens with me before 1 year ago. and i just bought new laptop...
|
how did u solve this?
Re: Kicking X because they didn't logon to the game. -
ReV. - 05.05.2013
Hey guys, I'm having the same issue!
Quote:
[02:05:07] Kicking 41.46.81.144 because they didn't logon to the game.
[02:05:19] Incoming connection: 79.106.109.186:36767
[02:05:22] Incoming connection: 109.92.14.147:28863
[02:05:25] Incoming connection: 5.69.147.172:62917
[02:05:26] Kicking 122.178.149.98 because they didn't logon to the game.
[02:05:29] Kicking 99.37.169.218 because they didn't logon to the game.
[02:05:33] Incoming connection: 189.224.144.38:18024
[02:05:49] Kicking 79.106.109.186 because they didn't logon to the game.
[02:05:55] Kicking 5.69.147.172 because they didn't logon to the game.
[02:05:57] Incoming connection: 41.250.194.144:52726
[02:06:00] Incoming connection: 85.246.123.36:63551
[02:06:07] Incoming connection: 99.37.169.218:62177
[02:06:16] Incoming connection: 109.92.14.147:28881
[02:06:27] Kicking 41.250.194.144 because they didn't logon to the game.
[02:06:30] Kicking 85.246.123.36 because they didn't logon to the game.
[02:06:37] Kicking 99.37.169.218 because they didn't logon to the game.
[02:06:53] Incoming connection: 189.224.144.38:18029
[02:07:21] Incoming connection: 201.211.142.14:46992
[02:07:35] Incoming connection: 201.242.183.28:65460
[02:07:51] Kicking 201.211.142.14 because they didn't logon to the game.
[02:07:57] Incoming connection: 187.138.27.97:58644
[02:08:05] Kicking 201.242.183.28 because they didn't logon to the game.
|
Second time this happened, it's pretty rare so I'm unable to find out exactly what's causing it.
Plugins: mysql streamer sscanf irc
Re: Kicking X because they didn't logon to the game. -
ReV. - 02.08.2013
This is a script issue, happened to me before, it was due to an infinite loop, even though the sa-mp software has problems.. this is not one of them.
AW: Kicking X because they didn't logon to the game. -
Mellnik - 03.08.2013
I can confirm it. It was really caused due to an infinite loop.
If you have this problem I suggest you installing ExecLogger then you can trace back where it accesses a infinite loop.
Re: Kicking X because they didn't logon to the game. -
dr1ftp0w3r - 05.08.2013
I have this problem too
I also have mysql.so, I tried ExecLogger but server goes crazy with it.. it freezes.
Re: Kicking X because they didn't logon to the game. -
[NRG]Dark - 08.08.2013
Help please!!
Very people with this problem!!
Re: Kicking X because they didn't logon to the game. -
Jaxson - 09.08.2013
I have the same problem. The game mode starts normally on a Linux server. I couldn't start the game mode properly after the host switched to a Windows server.
I've done some tests and I figured out that if you load a game mode which doesn't use NPC, the server will start normally, with game modes that use NPC (like mine) that is not the case. I even tried loading the grandlarc.amx game mode (which doesn't use NPCs) and then loaded a gl_npcs filterscript (SA-MP default filterscript which uses NPCs), and as expected, the server didn't start.
Re: Kicking X because they didn't logon to the game. -
TheProfessional - 11.08.2013
This happens to me but once or twice only.
Re: Kicking X because they didn't logon to the game. -
[NRG]Dark - 13.08.2013
I think I actually managed to solve.
I downloaded the samp-server 0.3e direct sa-mp.com, copied the includes folder pawno / includes of sampserver downloaded and pasted the folder of the pawno includes. Replace. REcompile.
And my server is Ok to 48hours
Re: Kicking X because they didn't logon to the game. -
JackStenzel - 24.08.2013
Up
Anyone can solve this problem? while two or more players login the server, this fu** message appears and anybody can joy to the server.
Sorry for my very very bad english, Brazil xD
Re: Kicking X because they didn't logon to the game. -
Dr.Einstein - 05.11.2013
Sorry for bumping this topic, but this is important.
I had this problem with my server and I fixed it.
As Mellnik said, it is a timer in the game-mode itself and not on any filter-scripts. We all know that this problem is caused by a
while loop. So, I did some tests, if the infinite loop is in a filter-script, the r-con commands do work and players are able to join. On the other hand, if that infinite loop is in the game-mode itself, then the sever will seem OK, but it is actually frozen and no one can join, hence
Kicking IP *.*.*.*:**** because they didn't log on to the game..
The way I came around it is by checking all my
while loops. Now, I didn't know which one of them actually caused the problem so I added a sentinel for each 'while' loop that I found, so if a loop counter is passed that, a message would show on the logs telling me that the this loop is broken.
Example:
Code:
new counter=0, i;
while(i == 1)//we know that this is an infinite loop because we do not change the value of 'i'
{
// our normal code in here and at the end we increment the counter and check to see if we have a problem...
if(++counter >= 5000)//now, you can change the sentinel value to whatever fits the use of your loop
{
printf("Infinite loop has been stopped. Loop at function: 'function name'"); // we place the function name so we can pinpoint the problem and do something about the loop.
break; //we break the loop.
}
}
Re: Kicking X because they didn't logon to the game. -
David (Sabljak) - 13.11.2013
Well this started to happening me now after some time i fixed it i dont know how xd
every about 12-24 hours server running...
Re: Kicking X because they didn't logon to the game. -
Craig007911 - 24.01.2014
Got it some badly configured statement or infinite loop caused it set values of variables and arrays to a decent size not an infinite size

Fixed