Too many moves to process in a frame(6 allowed, 6 run), discarding move
TechnIckS
Join Date: 2007-01-14 Member: 59616Members
<div class="IPBDescription">Why!??</div>UPDATE: There was some affinity issue on my machine. Fixed now. (S1 was 2,3,4 and S2 was 0-7, changed S2 to 5,6,7, problem fixed)
--------------------------------------------------------------------------------
Since upgrading the server to 230 i keep getting this constantly:
Too many moves to process in a frame(6 allowed, 6 run), discarding move.
It starts choking the server... anyone have any ideas why it's doing this??
Also:
"Client sent a move too far in the past" and similar message for the future!??
WTF?!??
--------------------------------------------------------------------------------
Since upgrading the server to 230 i keep getting this constantly:
Too many moves to process in a frame(6 allowed, 6 run), discarding move.
It starts choking the server... anyone have any ideas why it's doing this??
Also:
"Client sent a move too far in the past" and similar message for the future!??
WTF?!??
Comments
I checked my log and it has this too - however I am currently running a batch file where it automatically sets the affinities to 567
not sure if it is lagging or not.
also getting these?
Client sent a move too far in the past (39380.23 ms behind)
Client underflowed time credit (35.81 ms for move)
etc
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Client sent a move in the future (1199775.33 ms ahead)
Client underflowed time credit (37.78 ms for move)
Client sent a move in the future (1199761.20 ms ahead)
Client underflowed time credit (34.33 ms for move)
Client sent a move in the future (1199783.91 ms ahead)
Client underflowed time credit (37.09 ms for move)
Client sent a move in the future (1199772.52 ms ahead)
Client underflowed time credit (41.67 ms for move)
Client sent a move in the future (1199833.62 ms ahead)
Client underflowed time credit (37.73 ms for move)
Client sent a move in the future (1199818.30 ms ahead)
Client underflowed time credit (36.55 ms for move)
Client sent a move in the future (1199878.23 ms ahead)
Client underflowed time credit (39.12 ms for move)
Client sent a move in the future (1199865.48 ms ahead)<!--c2--></div><!--ec2-->
that are just a few lines from the log
this cant be "just debugging"
edit: Also I just noticed this after updating to 230. Hope this helps!
<!--c1--><div class='codetop'>CODE</div><div class='codemain'><!--ec1-->Client sent a move in the future (1199775.33 ms ahead)
Client underflowed time credit (37.78 ms for move)
Client sent a move in the future (1199761.20 ms ahead)
Client underflowed time credit (34.33 ms for move)
Client sent a move in the future (1199783.91 ms ahead)
Client underflowed time credit (37.09 ms for move)
Client sent a move in the future (1199772.52 ms ahead)
Client underflowed time credit (41.67 ms for move)
Client sent a move in the future (1199833.62 ms ahead)
Client underflowed time credit (37.73 ms for move)
Client sent a move in the future (1199818.30 ms ahead)
Client underflowed time credit (36.55 ms for move)
Client sent a move in the future (1199878.23 ms ahead)
Client underflowed time credit (39.12 ms for move)
Client sent a move in the future (1199865.48 ms ahead)<!--c2--></div><!--ec2-->
that are just a few lines from the log
this cant be "just debugging"<!--QuoteEnd--></div><!--QuoteEEnd-->
Is this on a listen server or on a dedicated server?
It will spam the console window with "Too many moves to process in a frame(6 allowed, 6 run), discarding move" enough to delay chat input by at least 3 seconds and will lag the game out until the performance is 0%.
I already change the affinity and it is still doing the same thing.
I will see this message come up about 18 times before seeing a "Client sent a move too far in the ...." message when the server is running fine.
It usually happens near the end of the game and I have seen it on different maps. I only have standard ns2 maps running in the rotation at the moment so I am not sure if it does this on modded maps or not.
It happens in an instant and not gradually. Everything is running fine one moment then it lags the server to a halt.
Only mods I am running are ns2stats and DAK Admin Kit.
Happens at random as some of my regulars and friends have stated that they played a few maps without any problems.
Any ideas?
What to do?
It has been causing minor rubber banding to some players. the cpu also doesn't look to be over taxed at the time of the error.
i got this message like spam by 5-80 lines in one time causing freeze/lag
Another issue but it's with the webadmin when we refresh it may causing freeze on my server.
Before the 230 my server runing fine but since the last two build it's hard ....
If i refresh it lets say 5 times in a row - it will show those errors then the server tick rate goes to 1.
I never had these issues before, I was even running 2 servers off the same machine no problem with plenty of hardware and bandwidth to spare for another server so I'm assuming there is now a problem with the server its self.
Should there not be a -debug line filter, that UWE can use on their official servers to garner this log info?
How is making that spamming the console on servers UWE do not control, going to help them?
EDIT:
I have a server 2x Xeon 3.6GHZ and 8GB ram. I should be able to run at least 1x 16 slot server. I cannot. I have actually only tried to run a server on it since 230, so I don't how it would have gone in 228/229...
I just got this flooded in my server log - caused huge rubber banding issues.
Can we please turn this off - it is really affecting the servers...