Jeremiah Rogers
2015-Aug-16 03:10 UTC
[Icecast] Relays Ending With "Disconnecting source due to socket timeout"
Greetings:
I use Icecast 2.4.0 on Windows 8.1. I have a config file which sets up
roughly a dozen relays to connect on demand.
My typical use is to connect to 1-4 of the streams simultaneously. All
connections are either via WinAmp to 127.0.0.1 or via other clients on
my LAN. My intent is to leave the connections active for up to 72 hours.
When I connect through my relays, eventually the connections are dropped
with "Disconnecting source due to socket timeout" errors. Connecting
to
the sources directly allows me to stream as long as I like. I presume my
problem to be me misunderstanding one or more settings, and any
tinkering I've done chasing the problem has centered on the limits
section. I've tried modifying queue-size, client-timeout,
header-timeout, source-timeout, burst-on-connect, and burst-size to no
avail. My config file is below. The config file has multiple relay
sections which follow the example here.
<icecast>
<limits>
<clients>16</clients>
<sources>12</sources>
<threadpool>5</threadpool>
<queue-size>524288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-on-connect>1</burst-on-connect>
<burst-size>65535</burst-size>
</limits>
<!-- set the mountpoint for a shoutcast source to use, the default
if not
specified is /stream but you can change it here if an
alternative is
wanted or an extension is required
<shoutcast-mount>/jzrcast</shoutcast-mount>
-->
<hostname>jzrtablet</hostname>
<listen-socket>
<port>8000</port>
<!-- <shoutcast-mount>/stream</shoutcast-mount> -->
</listen-socket>
<relays-on-demand>1</relays-on-demand>
<!-- StationNameGoesHere Relay -->
<relay>
<server>DomainGoesHere</server>
<port>8000</port>
<mount>/WhateverFollowsSlashInStreamURL</mount>
<local-mount>/SomethingICanRememberGoesHere</local-mount>
<!--<on-demand>0</on-demand>-->
<public>0</public>
<relay-shoutcast-metadata>1</relay-shoutcast-metadata>
</relay>
</icecast>
Everything past the relays section is unaltered from the default. Thanks
in advance for any thoughts.
--
Jeremiah Rogers
Mobile (Voice/Text): 704-996-5334
Email: jeremiahzrogers at gmail.com
Facebook/Twitter: /jzrogers
Nathan Miller
2015-Aug-16 03:22 UTC
[Icecast] Relays Ending With "Disconnecting source due to socket timeout"
Have you checked your firewall settings on your windows machine? Is there a firewall in the path of the connection? On Saturday, August 15, 2015, Jeremiah Rogers <jeremiahzrogers at gmail.com> wrote:> Greetings: > > I use Icecast 2.4.0 on Windows 8.1. I have a config file which sets up > roughly a dozen relays to connect on demand. > > My typical use is to connect to 1-4 of the streams simultaneously. All > connections are either via WinAmp to 127.0.0.1 or via other clients on > my LAN. My intent is to leave the connections active for up to 72 hours. > > When I connect through my relays, eventually the connections are dropped > with "Disconnecting source due to socket timeout" errors. Connecting to > the sources directly allows me to stream as long as I like. I presume my > problem to be me misunderstanding one or more settings, and any > tinkering I've done chasing the problem has centered on the limits > section. I've tried modifying queue-size, client-timeout, > header-timeout, source-timeout, burst-on-connect, and burst-size to no > avail. My config file is below. The config file has multiple relay > sections which follow the example here. > > <icecast> > <limits> > <clients>16</clients> > <sources>12</sources> > <threadpool>5</threadpool> > <queue-size>524288</queue-size> > <client-timeout>30</client-timeout> > <header-timeout>15</header-timeout> > <source-timeout>10</source-timeout> > <burst-on-connect>1</burst-on-connect> > <burst-size>65535</burst-size> > </limits> > > <!-- set the mountpoint for a shoutcast source to use, the default > if not > specified is /stream but you can change it here if an > alternative is > wanted or an extension is required > <shoutcast-mount>/jzrcast</shoutcast-mount> > --> > > <hostname>jzrtablet</hostname> > > <listen-socket> > <port>8000</port> > <!-- <shoutcast-mount>/stream</shoutcast-mount> --> > </listen-socket> > > <relays-on-demand>1</relays-on-demand> > > <!-- StationNameGoesHere Relay --> > <relay> > <server>DomainGoesHere</server> > <port>8000</port> > <mount>/WhateverFollowsSlashInStreamURL</mount> > <local-mount>/SomethingICanRememberGoesHere</local-mount> > <!--<on-demand>0</on-demand>--> > <public>0</public> > <relay-shoutcast-metadata>1</relay-shoutcast-metadata> > </relay> > </icecast> > > Everything past the relays section is unaltered from the default. Thanks > in advance for any thoughts. > > -- > Jeremiah Rogers > Mobile (Voice/Text): 704-996-5334 > Email: jeremiahzrogers at gmail.com <javascript:;> > Facebook/Twitter: /jzrogers > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org <javascript:;> > http://lists.xiph.org/mailman/listinfo/icecast >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20150815/cd24e327/attachment.htm
Jordan Erickson
2015-Aug-16 04:25 UTC
[Icecast] Relays Ending With "Disconnecting source due to socket timeout"
On 08/15/2015 08:10 PM, Jeremiah Rogers wrote: *snip*> When I connect through my relays, eventually the connections are dropped > with "Disconnecting source due to socket timeout" errors.*snip* What value is "eventually", approximately? Cheers, Jordan
Jeremiah Rogers
2015-Aug-16 13:34 UTC
[Icecast] Relays Ending With "Disconnecting source due to socket timeout"
Sorry to leave that out. My connections typically last 2-6 hours before the socket timeout error. The streams are MP3, either 64KBPS or 128KBPS. Nathan also asked about firewalls. My Windows Firewall is off, and my machine's antivirus doesn't have a firewall feature. I don't think there's any firewall in play here. Before emailing the list, I looked through several months of list archives hoping to find this problem covered. While I didn't find it, I saw reference to setting the log level to 4 and did that with my most recent stream to see what I might learn. When the socket timeout is generated, I see the following line. DBUG last 1439707668, timeout 10, now 1439707679 With each stream I used in that session, when that line would be generated, the difference between now and last was 11. They lead me to the following questions. What are those numbers? Do I correctly presume the allowable difference between them to be controlled by the <source-timeout> setting in the config file? If I change <source-timeout> to 30, 60, 256, or 512, what ramifications might that have on listeners, my machine, or sources from which I relay? Thanks! On 8/16/2015 0:25, Jordan Erickson wrote:> On 08/15/2015 08:10 PM, Jeremiah Rogers wrote: > *snip* >> When I connect through my relays, eventually the connections are dropped >> with "Disconnecting source due to socket timeout" errors. > *snip* > > What value is "eventually", approximately? > > > Cheers, > Jordan > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-- Jeremiah Rogers Mobile (Voice/Text): 704-996-5334 Email: jeremiahzrogers at gmail.com Facebook/Twitter: /jzrogers