LFS Forum - Logs flooding [probably fixed in 0.6B5]

#1 - DANIEL-CRO

Logs flooding [probably fixed in 0.6B5]

Fri, 26 Oct 2012 14:31

not exactly sure how I did this, it was something like this:
1. started LFS dedi host
2. played a bit on it and left host
3. put computer to hibernate with LFS dedi on
4. turned on computer after about 8 h ( then it started) - i think i got different local IP

Before few minutes wanned to start dedi's again, then realised they are already running, and log file was like 120 MB large

First there were messages

Oct 26 08:21:26 BLANK : OVERFLOW - host

700 of them per second

after this msg stoped, new started

Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (46) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (4) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection
Oct 26 08:25:35 Invalid (0) - could not find connection

about 850 per second

#2 - krugmander

Fri, 26 Oct 2012 23:54

120 mb txt file

Is this really a bug though?

#3 - DANIEL-CRO

Sat, 27 Oct 2012 08:26

Quote from krugmander :Is this really a bug though?

Of course it is

also I forgot to mention that CPU time was very high, all time sucking 50% of CPU (dual core)

#4 - edge3147

Sun, 28 Oct 2012 01:05

Quote from DANIEL-CRO :
3. put computer to hibernate with LFS dedi on

Don't hibernate if you want your host to run while you are away.

Hibernate power's off your computer and saves your windows session.

#5 - Whiskey

Sun, 28 Oct 2012 18:02

Quote from edge3147 :Don't hibernate if you want your host to run while you are away.

Hibernate power's off your computer and saves your windows session.

It's true that the server wont work, but that does not justify the flood the dedi produces. It should have a way to either just add 1 line with that error (o at leaste wait 1 minute) or just stop the server showing you the problem, so you have to reinit/restart it.

-

(edge3147) DELETED by edge3147

Sun, 28 Oct 2012 23:46

#6 - Scawen

Mon, 29 Oct 2012 11:06

I don't think this can happen with 0.6 B8 / B9, because the timer bounding will not allow LFS to act as if 8 hours has passed in a single frame. But please let me know if you can still reproduce that bug.

#7 - DANIEL-CRO

Tue, 30 Oct 2012 15:47

Quote from Scawen :I don't think this can happen with 0.6 B8 / B9, because the timer bounding will not allow LFS to act as if 8 hours has passed in a single frame. But please let me know if you can still reproduce that bug.

I guess it should be fine in new version.

Tonight I run both 0.6B and 0.6B9 and it only happned on 0.6B host. 150 MB of spam + 40 minutes CPU time

#8 - theodu69

Fri, 2 Nov 2012 23:07

Quote from DANIEL-CRO :I guess it should be fine in new version.

Tonight I run both 0.6B and 0.6B9 and it only happned on 0.6B host. 150 MB of spam + 40 minutes CPU time

Omfg.
150MB txt file