Server crashes (failed login from Taiwan)
 

Hello,

I have a problem: Since a few month, my sc2 Server crashes frequently. The logfile says this:

code:


2012-08-18 04:59:20     I       msg:[DST 61.63.39.74:50786 sid=1] SHOUTcast 1 client connection closed (1 seconds) [Bytes: 14480] Agent: `Java/1.6.0_29'

2012-08-18 04:59:20     I       msg:[DST 61.63.39.74:50790 sid=1] SHOUTcast 1 client connection accepted.

2012-08-18 04:59:20     I       msg:[DST 61.63.39.74:50789 sid=1] SHOUTcast 1 client connection accepted. Lavf53.13.0

2012-08-18 04:59:20     I       msg:[DST 61.63.39.74:50791 sid=1] SHOUTcast 1 client connection accepted. NSPlayer/4.1.0.3856

2012-08-18 04:59:20     I       msg:[SRC 61.63.39.74:50795 sid=1] SHOUTcast 1 source connection.

2012-08-18 04:59:20     E       msg:[SRC 61.63.39.74:50795 sid=1] connection denied. Bad password.

2012-08-18 04:59:20     E       msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue

2012-08-18 04:59:21     E       msg:[DST 61.63.39.74:50791 sid=1] Socket error while waiting to send data. err=Connection reset by peer(104)

2012-08-18 04:59:21     E       msg:virtual void AOL_logger::consoleLogger_element::log(const AOL_logger::message&) Error writing to console - write issue

2012-08-18 04:59:21     I       msg:[DST 61.63.39.74:50791 sid=1] SHOUTcast 1 client connection closed (1 seconds) [Bytes: 14480] Agent: `NSPlayer/4.1.0.3856

After this my server breaks down. I blocked all connections to my server from Taiwan with IPtables, but thats not a permanent solution. (I had the same coming from china and Korea). Does anyone know that problem? How can I solve it?

see http://forums.winamp.com/showthread.php?p=2790357#known and #6

banning it won't help as there's a bug in the ban handling in the v2 DNAS (which is also fixed for the next release). the general solution is to ban it in the OS firewall where possible e.g. via iptables on linux of the Windows firewall (i suggest you search the forum for the IP from your log to find the other threads about this and how to do the banning as i've just mentioned).

-daz

eerr... I wrote that already:

well i missed it as i saw the IP first and went into auto-pilot on my reply. however, the details of known issue #6 state that it is fixed for the next release (which i'm trying to finish off at this very moment...).

-daz