Short connections &10053/10054

[rtmeado]

I have five 96 kbps streams encoded from Winamp feeding one instance of the latest Shoutcast v2 server.

I am seeing lots of 10053 and 10054 socket errors (which I know are normal disconnect messages) on connections that last for only a second or two. It thought maybe it was a bandwidth problem so I knocked all five streams down from 128k to 96k yesterday but I'm still seeing these errors.

There are 10-second intro files on all of the streams. I am aware of the stuttering/drop problem with Flash players and intro files but it looks like it happens with several different media players.

Would someone please take a look at this log and tell me what's going on with these connections that are dropped so quickly?

Some other details:

server is Win 2008 R2 x64 with ~2 gigabit network connection. At any given time I have about 100 listeners across the five streams, most have been connected for more than 1 hour. As you can see by the sid's, the quick drops happen for all of the streams. (sid=2 has the most traffic, roughtly 60% of the listeners)

Thank you for your time.
-rtmeado

[rtmeado]

Just noticed something, curious that the byte counts [265677] is always the same on those quick drops. Anyway...

[DrO]

i'd drop the intro file and see if that makes any difference as the ones that are struggling are pulling down what is likely just the intro file part and see an end of file and abort. you point out the same byte count, if the intro file is close to that size then that points at it being that at fault.

-daz

[rtmeado]

I removed the intro file line from server config and restarted it. Here is the log now...same connect/quick drops appearing.

But get this...take a look about halfway down and you'll see me connecting to sid=2 from a machine on the local network. 10.21.3.25

Here is that portion of the log...

2013-01-07 10:49:24 I msg:[DST 10.21.3.25:4658 sid=2] SHOUTcast 1 client connection accepted. NSPlayer/11.0.5721.5275 WMFSDK/11.0
2013-01-07 10:49:24 I msg:[DST 10.21.3.25:4659 sid=2] SHOUTcast 1 client connection accepted. NSPlayer/11.0.5721.5275 WMFSDK/11.0
2013-01-07 10:49:24 E msg:[DST 10.21.3.25:4658 sid=2] Socket error while waiting to send data. err=Software caused connection abort.(10053)
2013-01-07 10:49:24 I msg:[DST 10.21.3.25:4658 sid=2] SHOUTcast 1 client connection closed (0 seconds) [Bytes: 257356] Agent: `NSPlayer/11.0.5721
.5275 WMFSDK/11.0'


As a novice looking at this, I read it as Windows Media Player tried to connect on two different ports, connection fails and is closed after less than a second.

But that isn't what happened. What really happened is the stream connected, buffered, then started and continued playing perfectly until I disconnected to reply to you.

Any guess as to why the server is logging a connection like this and saying the listener (me) disconnected when in fact it was working just fine? I am thinking there are lots of people trying to connect and being kicked off but maybe that's not the case, at least for everyone. I feel like I am trying to troubleshoot something that might not even be a problem but I can't be sure.

Thanks for your help, DrO.
-rtmeado

[rtmeado]

A-ha, a clue...I just noticed the connection drop on the log is for port 4658 only. It looks like 4659 stays on which explains why I was hearing the stream fine.

I know it's not your bag, but do you have any idea why the attempted connection on two different ports from WMP with one being aborted?

Thanks again.