Satz Klauer
2013-Feb-20 17:08 UTC
[Icecast] Relaying with Icecast - stand-by or active all the time?
The relaying-configuration seems to be straight-forward, unfortunately it does not work. That's my configuration: <relays-on-demand>1</relays-on-demand> <relay> <server>http://mp3stream7.apasf.apa.at</server> <port>8000</port> <mount>/</mount> <local-mount>/oe3.mp3</local-mount> <on-demand>1</on-demand> <relay-shoutcast-metadata>0</relay-shoutcast-metadata> </relay> And that's what the error log says: [2013-02-20 17:56:19] INFO connection/get_ssl_certificate No SSL capability [2013-02-20 17:56:20] DBUG slave/_slave_thread checking master stream list [2013-02-20 17:56:20] DBUG slave/check_relay_stream Adding relay source at mountpoint "/oe3.mp3" [2013-02-20 17:56:21] DBUG slave/_slave_thread checking master stream list [2013-02-20 17:56:37] DBUG auth/add_listener_to_source max on /oe3.mp3 is -1 (cur 0) [2013-02-20 17:56:37] DBUG auth/add_listener_to_source kicking off on-demand relay [2013-02-20 17:56:37] DBUG auth/add_listener_to_source Added client to /oe3.mp3 [2013-02-20 17:56:37] DBUG auth/add_authenticated_listener client authenticated, passed to source [2013-02-20 17:56:37] DBUG stats/modify_node_event update node clients (1) [2013-02-20 17:56:37] DBUG stats/modify_node_event update node connections (1) [2013-02-20 17:56:37] DBUG stats/modify_node_event update node client_connections (1) [2013-02-20 17:56:38] INFO slave/start_relay_stream Starting relayed source at mountpoint "/oe3.mp3" [2013-02-20 17:56:38] INFO slave/open_relay_connection connecting to http://mp3stream7.apasf.apa.at:8000 [2013-02-20 17:56:38] WARN slave/open_relay_connection Failed to connect to http://mp3stream7.apasf.apa.at:8000 [2013-02-20 17:56:38] DBUG source/source_clear_source clearing source "/oe3.mp3" When I'm doing a plain, simple wget http://mp3stream7.apasf.apa.at the stream is downloaded properly. Any Ideas what I'm doing wrong here? Thanks! On Wed, Feb 20, 2013 at 11:07 AM, R?cker Thomas <thomas.ruecker at tieto.com>wrote:> Hi, > > > On 20/02/13 11:38, Mike Thompsett wrote: > > Hi All, > > Will this also bounce new connections to the relay server once the > master server is maxed out? > > > So far we haven't done anything in this area. Also because I'd consider > this to be outside of core icecast scope. (I won't oppose patches, though) > The basic approach is round-robin DNS, which should give you an even > distribution across servers. > If that's not your intention, then you can use a simple http-redirect with > some business logic behind that to account for distribution ratio or geo-ip > distribution. I think I've seen such a script on git-hub even. > > Cheers > > Thomas > > > Regards, > Mike > > On 20 Feb 2013, at 07:53, Xabier Oneca -- xOneca < > xoneca+icecast at gmail.com> wrote: > > You have (little) documentation at > Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay > > Xabier Oneca_,,_ > El 20/02/2013 08:48, "Xabier Oneca -- xOneca" <xoneca+icecast at gmail.com> > escribi?: > >> You can set globally with the <relays-on-demand>1</relays-on-demand> in >> the global <icecast/> section, or you can configure per-relay with >> <on-demand>. >> >> You can find it in the sample config file. (Does not say much more.) >> >> Xabier Oneca_,,_ >> El 20/02/2013 08:39, "Satz Klauer" <satzklauer at googlemail.com> escribi?: >> >>> Thanks, but which parameter influences this behaviour? I could not find >>> anything in description of relaying parameters... >>> >>> On Wed, Feb 20, 2013 at 8:30 AM, Xabier Oneca -- xOneca < >>> xoneca+icecast at gmail.com> wrote: >>> >>>> Hello Satz, >>>> >>>> You can configure that behavior from the config file. >>>> >>>> Xabier Oneca_,,_ >>>> El 20/02/2013 07:58, "Satz Klauer" <satzklauer at googlemail.com> >>>> escribi?: >>>> >>>> Hi, >>>> >>>> I found there is a possibility to let IceCast relay other, existing >>>> streams. But how is it working exactly when no clients are connected to my >>>> relay server: >>>> >>>> - is it going to stand-by and not streaming andy data from the source >>>> >>>> or >>>> >>>> - is it pulling data from the source all the time also when no client >>>> is available that could consume this stream? This would mean the relay >>>> would consume traffic and bandwidth also when nobody will use it... >>>> >>>> Thanks! >>>> >>>> >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >>>> >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >>> _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20130220/97215574/attachment-0001.htm
José Luis Artuch
2013-Feb-20 18:22 UTC
[Icecast] Relaying with Icecast - stand-by or active all the time?
Satz, At first you should define <mount>. <mount> is the mountpoint to be relayed, located on remote server (master server). <local-mount> is the previous mountpoint, but now, located on local server (relay server). Trying "wget http://mp3stream7.apasf.apa.at" I get "http://194.232.200.156:8000/listen.pls" and this works ok. Otherwise, each mountpoint relayed is considered as a source in the relay server, so, you must configure correctly <sources> in the "icecast.xml" file in the relay server. El mi?, 20-02-2013 a las 18:08 +0100, Satz Klauer escribi?:> The relaying-configuration seems to be straight-forward, > unfortunately it does not work. That's my configuration: > > > > <relays-on-demand>1</relays-on-demand> > > <relay> > <server>http://mp3stream7.apasf.apa.at</server> > <port>8000</port> > <mount>/</mount> > <local-mount>/oe3.mp3</local-mount> > <on-demand>1</on-demand> > > <relay-shoutcast-metadata>0</relay-shoutcast-metadata> > </relay> > > > > And that's what the error log says: > > > [2013-02-20 17:56:19] INFO connection/get_ssl_certificate No SSL > capability > [2013-02-20 17:56:20] DBUG slave/_slave_thread checking master stream > list > [2013-02-20 17:56:20] DBUG slave/check_relay_stream Adding relay > source at mountpoint "/oe3.mp3" > [2013-02-20 17:56:21] DBUG slave/_slave_thread checking master stream > list > [2013-02-20 17:56:37] DBUG auth/add_listener_to_source max on /oe3.mp3 > is -1 (cur 0) > [2013-02-20 17:56:37] DBUG auth/add_listener_to_source kicking off > on-demand relay > [2013-02-20 17:56:37] DBUG auth/add_listener_to_source Added client > to /oe3.mp3 > [2013-02-20 17:56:37] DBUG auth/add_authenticated_listener client > authenticated, passed to source > [2013-02-20 17:56:37] DBUG stats/modify_node_event update node clients > (1) > [2013-02-20 17:56:37] DBUG stats/modify_node_event update node > connections (1) > [2013-02-20 17:56:37] DBUG stats/modify_node_event update node > client_connections (1) > [2013-02-20 17:56:38] INFO slave/start_relay_stream Starting relayed > source at mountpoint "/oe3.mp3" > [2013-02-20 17:56:38] INFO slave/open_relay_connection connecting to > http://mp3stream7.apasf.apa.at:8000 > [2013-02-20 17:56:38] WARN slave/open_relay_connection Failed to > connect to http://mp3stream7.apasf.apa.at:8000 > [2013-02-20 17:56:38] DBUG source/source_clear_source clearing source > "/oe3.mp3" > > > > When I'm doing a plain, simple > > > wget http://mp3stream7.apasf.apa.at > > > the stream is downloaded properly. Any Ideas what I'm doing wrong > here? > > > Thanks! > > > > > > On Wed, Feb 20, 2013 at 11:07 AM, R?cker Thomas > <thomas.ruecker at tieto.com> wrote: > > Hi, > > > > On 20/02/13 11:38, Mike Thompsett wrote: > > > Hi All, > > > > > > Will this also bounce new connections to the relay server > > once the master server is maxed out? > > > > > So far we haven't done anything in this area. Also because I'd > consider this to be outside of core icecast scope. (I won't > oppose patches, though) > The basic approach is round-robin DNS, which should give you > an even distribution across servers. > If that's not your intention, then you can use a simple > http-redirect with some business logic behind that to account > for distribution ratio or geo-ip distribution. I think I've > seen such a script on git-hub even. > > Cheers > > Thomas > > > > > > Regards, > > Mike > > > > On 20 Feb 2013, at 07:53, Xabier Oneca -- xOneca <xoneca > > +icecast at gmail.com> wrote: > > > > > > > You have (little) documentation at > > > Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay > > > > > > Xabier Oneca_,,_ > > > > > > > > > El 20/02/2013 08:48, "Xabier Oneca -- xOneca" <xoneca > > > +icecast at gmail.com> escribi?: > > > > > > You can set globally with the > > > <relays-on-demand>1</relays-on-demand> in the > > > global <icecast/> section, or you can configure > > > per-relay with <on-demand>. > > > > > > You can find it in the sample config file. (Does > > > not say much more.) > > > > > > Xabier Oneca_,,_ > > > > > > > > > El 20/02/2013 08:39, "Satz Klauer" > > > <satzklauer at googlemail.com> escribi?: > > > > > > Thanks, but which parameter influences > > > this behaviour? I could not find anything > > > in description of relaying parameters... > > > > > > > > > On Wed, Feb 20, 2013 at 8:30 AM, Xabier > > > Oneca -- xOneca <xoneca+icecast at gmail.com> > > > wrote: > > > > > > Hello Satz, > > > > > > You can configure that behavior > > > from the config file. > > > > > > Xabier Oneca_,,_ > > > > > > > > > El 20/02/2013 07:58, "Satz Klauer" > > > <satzklauer at googlemail.com> > > > escribi?: > > > > > > Hi, > > > > > > > > > > > > I found there is a > > > possibility to let IceCast > > > relay other, existing > > > streams. But how is it > > > working exactly when no > > > clients are connected to > > > my relay server: > > > > > > > > > - is it going to stand-by > > > and not streaming andy > > > data from the source > > > > > > > > > or > > > > > > > > > - is it pulling data from > > > the source all the time > > > also when no client is > > > available that could > > > consume this stream? This > > > would mean the relay would > > > consume traffic and > > > bandwidth also when nobody > > > will use it... > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > Icecast mailing list > > > Icecast at xiph.org > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > > > > > > > _______________________________________________ > > > Icecast mailing list > > > Icecast at xiph.org > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > _______________________________________________ > > > Icecast mailing list > > > Icecast at xiph.org > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20130220/e464e750/attachment-0001.htm
José Luis Artuch
2013-Feb-20 19:53 UTC
[Icecast] Relaying with Icecast - stand-by or active all the time?
Ah, ok Satz, I did not know that's right :( Now I am trying: <server>194.232.200.156</server> <port>8000</port> <mount>/listen.pls</mount> <local-mount>/oe3.mp3</local-mount> ... but I do not get the mountpoint "oe3.mp3" in http://186.56.96.133:8200 May be something related with the extension "pls" ?. El mi?, 20-02-2013 a las 19:30 +0100, Satz Klauer escribi?:> Jose, > > > > I'm already using "/" as mountpoint since the streams is sent from > this URL directly (with no additional name appended to it) > > On Wed, Feb 20, 2013 at 7:22 PM, Jos? Luis Artuch > <artuch at speedy.com.ar> wrote: > > Satz, > > At first you should define <mount>. > > <mount> is the mountpoint to be relayed, located on remote > server (master server). > <local-mount> is the previous mountpoint, but now, located on > local server (relay server). > > Trying "wget http://mp3stream7.apasf.apa.at" I get > "http://194.232.200.156:8000/listen.pls" and this works ok. > > Otherwise, each mountpoint relayed is considered as a source > in the relay server, so, you must configure correctly > <sources> in the "icecast.xml" file in the relay server. > > El mi?, 20-02-2013 a las 18:08 +0100, Satz Klauer escribi?: > > > The relaying-configuration seems to be straight-forward, > > unfortunately it does not work. That's my configuration: > > > > > > > > <relays-on-demand>1</relays-on-demand> > > > > <relay> > > <server>http://mp3stream7.apasf.apa.at</server> > > <port>8000</port> > > <mount>/</mount> > > <local-mount>/oe3.mp3</local-mount> > > <on-demand>1</on-demand> > > > > <relay-shoutcast-metadata>0</relay-shoutcast-metadata> > > </relay> > > > > > > > > And that's what the error log says: > > > > > > [2013-02-20 17:56:19] INFO connection/get_ssl_certificate No > > SSL capability > > [2013-02-20 17:56:20] DBUG slave/_slave_thread checking > > master stream list > > [2013-02-20 17:56:20] DBUG slave/check_relay_stream Adding > > relay source at mountpoint "/oe3.mp3" > > [2013-02-20 17:56:21] DBUG slave/_slave_thread checking > > master stream list > > [2013-02-20 17:56:37] DBUG auth/add_listener_to_source max > > on /oe3.mp3 is -1 (cur 0) > > [2013-02-20 17:56:37] DBUG auth/add_listener_to_source > > kicking off on-demand relay > > [2013-02-20 17:56:37] DBUG auth/add_listener_to_source Added > > client to /oe3.mp3 > > [2013-02-20 17:56:37] DBUG auth/add_authenticated_listener > > client authenticated, passed to source > > [2013-02-20 17:56:37] DBUG stats/modify_node_event update > > node clients (1) > > [2013-02-20 17:56:37] DBUG stats/modify_node_event update > > node connections (1) > > [2013-02-20 17:56:37] DBUG stats/modify_node_event update > > node client_connections (1) > > [2013-02-20 17:56:38] INFO slave/start_relay_stream Starting > > relayed source at mountpoint "/oe3.mp3" > > [2013-02-20 17:56:38] INFO slave/open_relay_connection > > connecting to http://mp3stream7.apasf.apa.at:8000 > > [2013-02-20 17:56:38] WARN slave/open_relay_connection > > Failed to connect to http://mp3stream7.apasf.apa.at:8000 > > [2013-02-20 17:56:38] DBUG source/source_clear_source > > clearing source "/oe3.mp3" > > > > > > > > When I'm doing a plain, simple > > > > > > wget http://mp3stream7.apasf.apa.at > > > > > > the stream is downloaded properly. Any Ideas what I'm doing > > wrong here? > > > > > > Thanks! > > > > > > > > On Wed, Feb 20, 2013 at 11:07 AM, R?cker Thomas > > <thomas.ruecker at tieto.com> wrote: > > > > Hi, > > > > > > On 20/02/13 11:38, Mike Thompsett wrote: > > > > > > > Hi All, > > > > > > > > > Will this also bounce new connections to the relay > > > server once the master server is maxed out? > > > > > > > > So far we haven't done anything in this area. Also > > because I'd consider this to be outside of core > > icecast scope. (I won't oppose patches, though) > > The basic approach is round-robin DNS, which should > > give you an even distribution across servers. > > If that's not your intention, then you can use a > > simple http-redirect with some business logic behind > > that to account for distribution ratio or geo-ip > > distribution. I think I've seen such a script on > > git-hub even. > > > > Cheers > > > > Thomas > > > > > > > > > Regards, > > > Mike > > > > > > On 20 Feb 2013, at 07:53, Xabier Oneca -- xOneca > > > <xoneca+icecast at gmail.com> wrote: > > > > > > > > > > > > > You have (little) documentation at > > > > Http://icecast.org/docs/icecast-2.3.2/icecast2_config_file.html#relay > > > > > > > > Xabier Oneca_,,_ > > > > > > > > El 20/02/2013 08:48, "Xabier Oneca -- xOneca" > > > > <xoneca+icecast at gmail.com> escribi?: > > > > > > > > You can set globally with the > > > > <relays-on-demand>1</relays-on-demand> > > > > in the global <icecast/> section, or you > > > > can configure per-relay with > > > > <on-demand>. > > > > > > > > You can find it in the sample config > > > > file. (Does not say much more.) > > > > > > > > Xabier Oneca_,,_ > > > > > > > > El 20/02/2013 08:39, "Satz Klauer" > > > > <satzklauer at googlemail.com> escribi?: > > > > > > > > Thanks, but which parameter > > > > influences this behaviour? I > > > > could not find anything in > > > > description of relaying > > > > parameters... > > > > > > > > On Wed, Feb 20, 2013 at 8:30 AM, > > > > Xabier Oneca -- xOneca <xoneca > > > > +icecast at gmail.com> wrote: > > > > > > > > Hello Satz, > > > > > > > > You can configure that > > > > behavior from the config > > > > file. > > > > > > > > Xabier Oneca_,,_ > > > > > > > > El 20/02/2013 07:58, > > > > "Satz Klauer" > > > > <satzklauer at googlemail.com> escribi?: > > > > > > > > Hi, > > > > > > > > > > > > I found there is > > > > a possibility to > > > > let IceCast > > > > relay other, > > > > existing > > > > streams. But how > > > > is it working > > > > exactly when no > > > > clients are > > > > connected to my > > > > relay server: > > > > > > > > > > > > - is it going to > > > > stand-by and not > > > > streaming andy > > > > data from the > > > > source > > > > > > > > > > > > or > > > > > > > > > > > > - is it pulling > > > > data from the > > > > source all the > > > > time also when > > > > no client is > > > > available that > > > > could consume > > > > this stream? > > > > This would mean > > > > the relay would > > > > consume traffic > > > > and bandwidth > > > > also when nobody > > > > will use it... > > > > > > > > > > > > Thanks! > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Icecast mailing > > > > list > > > > Icecast at xiph.org > > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > > Icecast mailing list > > > > Icecast at xiph.org > > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > > > > _______________________________________________ > > > > Icecast mailing list > > > > Icecast at xiph.org > > > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > > > > > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > > > > >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.xiph.org/pipermail/icecast/attachments/20130220/a44ae623/attachment.htm
Geoff Shang
2013-Feb-21 20:28 UTC
[Icecast] Relaying with Icecast - stand-by or active all the time?
On Wed, 20 Feb 2013, Jos? Luis Artuch wrote:> Now I am trying: > > <server>194.232.200.156</server> > <port>8000</port> > <mount>/listen.pls</mount> > <local-mount>/oe3.mp3</local-mount> > > ... but I do not get the mountpoint "oe3.mp3" in > http://186.56.96.133:8200 > May be something related with the extension "pls" ?.It is, kind of. The source server is a Shoutcast v1 server, which means no mountpoint. You should use: <mount>/</mount> instead. The /listen.pls is the link for a browser to get a media player to play, it's not the link to the stream itself which Icecast needs. HTH, Geoff.