Page 1 of 1

Message exceed allowed max length (0 bytes)

Posted: 22 Apr 2008, 15:44
by Gamebrew
I just installed SmartFox on my linux server. Twice I tried just leaving it on, with no connections, just the admin console open on my client. I keep getting these errors every few minutes, but 0 length can't be a max:

Code: Select all

2008/05/02 18:13:42.967 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:14:06.510 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:14:08.086 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:16:03.498 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:16:22.675 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:17:51.422 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:17:55.228 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /77.250.93.216
2008/05/02 18:27:25.459 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /81.206.82.156
2008/05/02 18:43:00.601 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /84.47.54.247
2008/05/02 18:43:01.084 - [ WARNING ] [id: 11] (SmartFoxServer.readIncomingMessages): Message exceed allowed max length! (0 bytes) from > /213.211.37.85
Thanks!

Posted: 22 Apr 2008, 19:31
by Lapo
The server complains about messages of wrong/unexpected size. Usually this error should appear when a client sends too large data, but it can also come with a 0 bytes long request. This is seen more rarely, actually.
And yes, the error message can be misleading in that case.

It could be a malicious connection, trying to send illegal characters / data which ends up in an empty request, which is rejected.

Posted: 22 Apr 2008, 19:32
by Lapo
Btw, you have the IP address of the client machine. If the problem persists you can ban that IP

Posted: 22 Apr 2008, 20:58
by Gamebrew
Hi Lapo, I wonder why they would do that. Ok I will try banning the IP and maybe changing the port #.

Posted: 23 Apr 2008, 05:13
by Lapo
Have you ever taken a look at a firewall log of a server connected directly to the internet? It's a wild world out there :? :)
Seriously, you can literally receive thousands of all sorts of connection attempts, port scans, hack searches etc... every day :shock: