I'm asking the experienced LFS programmers out there for some help.

Here is a snippet of my LFS dedi logs.txt file.

Quote :

May 20 15:12:17 Sent OK to new guest
May 20 15:12:17 Sent scrutineering packet
May 20 15:12:18 Sent host info to new guest
May 20 15:12:18 Sent new user packet
May 20 15:12:18 [DC]Jonno^L connected (jonno koot)
May 20 15:12:18 [DC]Jonno connected (Netherlands)
May 20 15:12:33 InitialD TiLorC^L left the pits (LX4)
May 20 15:12:38 ™SWEÖrebro^L pitted
May 20 15:12:39 [DC]Jonno : ^LWS • Granberg - xDDDDDDD
May 20 15:12:45 ™SWEÖrebro^L left the pits (FZR)
May 20 15:14:02 [DC]Jonno : ^LXaoz™ Dk9 - move off the road
May 20 15 13 07 [DC]Jonno^L left the pits (XRT)
May 20 15 13 19 INSIM ERROR : WOULDBLOCK
May 20 15 13 41 Repaired Mesh
May 20 15 13 43 FATAL INSIM ERROR : BUFFER SIZE
May 20 15 13 43 InSim closed : ClaViCo
May 20 15 13 43 GuestSend : wrong mode
May 20 15 13 43 GuestSend : wrong mode
May 20 15 13 46 Fatlace^JÐKeny^L pitted
May 20 15 13 46 Repaired Mesh
May 20 15 13 53 Fatlace^JÐKeny^L left the pits (LX4)

Obviously my InSim application is to blame for this but I can't exactly figure out what exactly causes the socket to be terminated. I'm speculating that a high amount of IS_BTN packets could be the cause. Only thing I know so far is that the issue occurs after 50 hours of runtime on a busy server. My lack of core knowledge of the OSI model,Internet Protocol,InSim protocol is no help either. Any information about this error is highly appreciated.

Guidance towards a comprehensive "button factory" is also welcome.

(Finally, ":-13-:" without "-" makes this weird smiley of ET and his little brother :13

EDIT:

Quote :

Hmmno.. Not really..

Some error about once a day but not disruptive. No idea what this means;

Dec 02 22:16:53 FATAL INSIM ERROR : BUFFER SIZE
Dec 02 22:16:53 InSim closed : InSim Relay
Dec 02 22:16:53 GuestSend : wrong mode
Dec 02 22:16:53 GuestSend : wrong mode

Only happened once. Didn't caused trouble really.

This patch E is much much more stable then the version B one in my opinion.
mjh93sa
8th December 2012, 19:02
I'm also getting the

FATAL INSIM ERROR : BUFFER SIZE

From experimentation so far it seems that the more text you throw into the game chat the sooner the error occurs. Only happening since the latest patches, and not had a chance to investigate further as yet.
Scawen
9th December 2012, 18:31
I'm surprised that is happening online. It suggests that InSim is sending out (over some time) a lot of information to the connected program, but the connected program isn't collecting it from its buffer. Eventually TCP can't send it and InSim stores it in its buffer. When this exceeds 47104 bytes then you will get the fatal error and the InSim program will be disconnected. What is the connected InSim program that gets disconnected?

link: https://www.lfsforum.net/archive/index.php/t-81538.html

probably cuz WKD is back

I'm far from convinced this issue is DDOS related. It hasn't happened when the DDOS attacks were on.

Quote from CodeLyoko1 :

probably cuz WKD is back

Don't post about things that you have no clue about.

im guessing its ok now cuz the insim on WS is working as normal