Server Crashing Issues

[Ben S.]

I am having a fairly severe problem with the server crashing VERY frequently on windows without any type of warning.  On linux however, it seems extremely stable and I have not ever experienced 1 crash.

On windows, I build with mingw, and am I right assuming for /downloads you guys use Visual Studio or some derivative?  Either way both compilers don't provide a very stable executable.

I am running Windows 7 64-bit.  Has anyone else had similar problems?

[deoxxa]

On windows, I build with mingw, and am I right assuming for /downloads you guys use Visual Studio or some derivative?  Either way both compilers don't provide a very stable executable.

The ones in /downloads are built with MingW as well, but I'm yet to see any issues.

I am running Windows 7 64-bit.  Has anyone else had similar problems?

I do it all in a virtual machine running as 32 bit so maybe it's a 64 bit issue, but as far as I understand it Windows has some form of virtual machine deal going on for 32 bit code on 64 bit hosts? I'll give it a go on a 64 bit box and see if I can replicate the issue.

[Ben S.]

I'll also give it a go on a 32 bit windows I have around.  I noticed that sometimes it just flat out crashes, and sometimes it spits out the message (can't remember exactly) Unhandled Message 0xsomething, even if nothing is connected.  Maybe socket connections aren't getting cleaned up properly?

I'll test a little more here soon to give you better results to work with.

[ReDucTor]

You should keep those 0x56789ABCDE  this error code helps us track the issue

[Ben S.]

OK, left it running for about an hour, came back and saw this on the console.  Also I think you need to format whatever print function you are using like %02X, cause i think 0x4 is supposed to be 0x04?

Unknown action: 0xa2
Unknown action: 0xc0
Unknown action: 0x5d
Unknown action: 0x6
Unknown action: 0x18
Unknown action: 0x4e
Unknown action: 0xe6
Unknown action: 0x6
Unknown action: 0x11
Unknown action: 0x46
Unknown action: 0x2d
Unknown action: 0xa9
Unknown action: 0xcb
Unknown action: 0x34
Unknown action: 0xed
Unknown action: 0xe2
Unknown action: 0xed
Unknown action: 0x35
Unknown action: 0xc4
Unknown action: 0xfd
Unknown action: 0xce
Unknown action: 0x94
Unknown action: 0x26
Unknown action: 0x5d
Unknown action: 0xf5
Unknown action: 0x69
Unknown action: 0x2a
Unknown action: 0x38
Unknown action: 0x1f
Unknown action: 0xd4
Unknown action: 0x4
Unknown action: 0xb4
Unknown action: 0x3d
Unknown action: 0x6f
Unknown action: 0x1d
Unknown action: 0x33

[Fador]

OK, left it running for about an hour, came back and saw this on the console.

What port are you running mineserver in? Looks like some random connection is made and thus crashing the server. I know we should do something to prevent it =b

Also I think you need to format whatever print function you are using like %02X, cause i think 0x4 is supposed to be 0x04?

Same thing?

[Ben S.]

Actually since I run the official server, I run this on port 12345 (easy to remember).  I'll try the default port and see if I have issues.

Oh, and no connections are shown on the console, just the message.

[Fador]

Oh, and no connections are shown on the console, just the message.

Because no message is printed on connect. Only after handshake and login. So if anyone connects with wrong protocol, you would get only those messages.

[Ben S.]

Well since my last post ( a few hours), it has been running without a hitch on 25565.  Is there no filtering of connections if the handshake fails?

Also something else to note.  When I ran this on port 12345 on 32 bit linux, there was never a problem to speak of.  Maybe it is just my situation, idk.

Edit: Haha just looked at the official minecraft server that has been running on port 12345 and saw this many times:

2010-12-07 18:22:42 [INFO] Disconnecting /**.**.**.***:57650: Protocol error
2010-12-07 18:22:42 [INFO] /**.**.**.***:57650 lost connection

Odd though that mineserver doesnt fail on linux when this probably happens.  Maybe sockets are handled differently internally by the OS.

Weird that port 12345 has crawlers....

[deoxxa]

That definitely sounds like junk data that the server is trying to parse. I'll open a ticket on the bug tracker for an enhancement to be a bit less trusting of initial data sent upon connect but before handshake.