NET ERROR Flooding my Error Logs

**trevius** · #1 02-08-2008, 07:45 PM

Makes sense, cause it is mostly only from Chinese players. I need to get that debug turned off. Guess I will have to figure out how to setup the source and compile it all instead of using the simple win32 version. Just wish those debugs were turned off by default.

**trevius** · #2 02-08-2008, 07:49 PM

Here is another example from today. The thing that gets me is that some of them are the same exact message. It isn't incrementing like you would think an error like this should:

Code:

[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)

**trevius** · #3 02-12-2008, 10:50 AM

BTW, incase anyone else finds the debugs more than annoying, I *think* I have found a simple work-around for it.

Simply rename your "Log" folder in your eqemu directory to "Log2" or even just delete it. The debugs can't make logs if they don't have a folder to go into.

Why didn't I think of this before lol? Well, I originally considered it, but I figured they would just create another folder, so I didn't even bother.

The best part is that it is really quick and easy to turn off and on. All you do is rename your log folder back and restart your server.

Sure, you will get an error or 2 about the folder being missing so debugs and logs can't work, but I don't think it is a big deal. It seems to have reduced lag on my server by a lot so far as well. I wish there was an easy graceful way to disable and enable logs/debugs, but for now, this should work for anyone.

Hope someone finds that info useful.

**Congdar** · #4 03-05-2008, 02:53 AM

This error started happening on my server a few days ago. The account/player in question did not seem to be doing anything strange, and they claimed to not be experiencing any lag.

The real problem is that even after they log off, the error continues to fill the logs... I mean.... they're gone but their ip and error keep filling up the log files making them huge!

Is there a better way to handle out of order packets than this?

kiirdiir · #5 03-05-2008, 07:59 AM

Quote:

Originally Posted by Knightly

I can't tell you why it happens, but if you comment out the following line in common\EQStream.cpp it will stop:

Code:

if(CompareSequence(NextOutSeq, seq_send) == SeqFuture) {
//_log(NET__ERROR, _L "Tried to write a packet beyond the end of the queue! (%d is past next out %d)" __L, seq_send, NextOutSeq);
sitr=SequencedQueue.end();

Quote:

Originally Posted by trevius

Here is another example from today. The thing that gets me is that some of them are the same exact message. It isn't incrementing like you would think an error like this should:

Code:

[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)
[02.09. - 01:33:57] [NET__ERROR] 219.77.151.159:1193: Tried to write a packet beyond the end of the queue! (2781 is past next out 5625)

Maybe it was meant to be:

Code:

if(CompareSequence(NextOutSeq, seq_send) > SeqFuture) {
_log(NET__ERROR, _L "Tried to write a packet beyond the end of the queue! (%d is past next out %d)" __L, seq_send, NextOutSeq);
sitr=SequencedQueue.end();

Just throwing it out there, passing through trying to find solutions to other problems.

**Congdar** · #6 03-12-2008, 03:59 AM

The compare can only return SeqInOrder, SeqFuture or SeqPast, so > probably isn't correct and ignoring it doesn't seem right either... is the packet stuck in the queue somewhere because this is currently an endless loop even after the account has logged off. Is there some way to clear this packet?