Icecast Streaming Media Server

[karlH]

The key thing I see here is

[2012-12-29 14:40:34] DBUG source/source.c last 1356810023, timeout 10, now 1356810034
[2012-12-29 14:40:34] WARN source/source.c Disconnecting source due to socket timeout

so icecast never received any more data from the source, dropping the connection after 10 seconds of nothing being received. Either the source stalled or the connection broke preveting data getting there properly.

karl.

[weirdorecords]

Karl- that makes me think that I need to check the lame.dll. Does that sound right to you? Winamp is definitely sending sound (In the sense that I can hear it), and it's at least getting as far as Edcast, as I can see the meters moving.

DJ-Zath- I've got Comcast's router, & the machine I'm using as a server isn't wireless, so should be okay there. Thanks for thinking of me though.
_________________
thanks much!

Angela
Weirdo Records

[weirdorecords]

Still trying to fix my timeout problem. I tried adding this section to my configuration file, but no change:

<limits>
<clients>100</clients>
<sources>2</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<!-- If enabled, this will provide a burst of data when a client
first connects, thereby significantly reducing the startup
time for listeners that do substantial buffering. However,
it also significantly increases latency between the source
client and listening client. For low-latency setups, you
might want to disable this. -->
<burst-on-connect>1</burst-on-connect>
<!-- same as burst-on-connect, but this allows for being more
specific on how much to burst. Most people won't need to
change from the default 64k. Applies to all mountpoints -->
<burst-size>65535</burst-size>
</limits>
_________________
thanks much!

Angela
Weirdo Records

[karlH]

changes to icecast configuration will not improve the ability for icecast to receive data. If the data is not received then it will timeout at some point (default 10 seconds). Try to determine that data is being sent to icecast, avoid plugins except edcast for example, get your network administrator to determine what network packets are being sent, for all we know, the link dies.

karl.

[weirdorecords]

Well, after weeks of frustrating troubleshooting, I switched over to Shoutcast for now. Got it working in a day or two.
_________________
thanks much!

Angela
Weirdo Records

[karlH]

It's hard to come up with a solution when there is little information to go on, usually it is down to some assumption. For instance if shoutcast works using the exact same procedure then it's probably because the 2 ports and shoutcast-mount is not set up.

karl.