From mph at emotrics.com  Thu Oct 13 20:51:12 2022
From: mph at emotrics.com (Milton Huang)
Date: Thu, 13 Oct 2022 13:51:12 -0700
Subject: [Icecast] load balancing
Message-ID: <CAKSXWJ7e-yHdx-yPtR68v76nc+BC-4fpm2iLJ91EcK1qqsN_yA@mail.gmail.com>

Based on a suggestion Philipp made, I'm setting up an Icecast master/relay
setup where one Icecast master is broadcasting our stream to several
Icecast Relays which in turn receive direct client connections. All of this
is implemented on AWS ec2 Instances. To manage all the Relays under a
single URL, I'm currently using an AWS Load Balancer to distribute the
incoming requests from clients which all works fine.  My issue is that the
logs on the Relays only report the IP address of the Load Balancer, and not
of the original client. AWS automatically includes the client IP addresses
in a 'X-Forward-For' header, but Icecast doesn't parse that. I'm looking
for any suggestions on how to fix this so I can log all the correct client
IP addresses. (I *don't* want to change to the 'kh' branch just because
they implemented that header)

-milton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20221013/ef455d85/attachment.htm>

From dik23 at hotmail.com  Mon Oct 17 12:07:29 2022
From: dik23 at hotmail.com (Dik ....)
Date: Mon, 17 Oct 2022 12:07:29 +0000
Subject: [Icecast] Relay errors in logs
In-Reply-To: <LOYP123MB31843DE9DFAB248E3671A0C8A8549@LOYP123MB3184.GBRP123.PROD.OUTLOOK.COM>
References: <LOYP123MB31843DE9DFAB248E3671A0C8A8549@LOYP123MB3184.GBRP123.PROD.OUTLOOK.COM>
Message-ID: <LOYP123MB31846C40AD6EBD926DF59428A8299@LOYP123MB3184.GBRP123.PROD.OUTLOOK.COM>

Doesn't anyone have any ideas about this?
________________________________
From: Icecast <icecast-bounces at xiph.org> on behalf of Dik .... <dik23 at hotmail.com>
Sent: 28 September 2022 14:37
To: Icecast user discussions <icecast at xiph.org>
Subject: [Icecast] Relay errors in logs

icecast2 2.4.4-3ubuntu0.1 Ubuntu 20.04.5

I have set up a relay back to the localhost icecast server so that I can have one mountpoint with a fallback and one without

I have 2 questions.  1st is why am I getting the following in error.log when nothing is connected to /input, is there anything I've missed?

[2022-09-28  12:29:49] INFO slave/start_relay_stream Starting relayed source at mountpoint "/relay"
[2022-09-28  12:29:49] INFO slave/open_relay_connection connecting to domain.name:8000
[2022-09-28  12:29:49] INFO fserve/fserve_client_create checking for file /input (/usr/share/icecast2/web/input)
[2022-09-28  12:29:49] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/input" No such file or directory
[2022-09-28  12:29:49] EROR slave/open_relay_connection Error from relay request: /relay (File Not Found)

2nd is in order for /relay to update in any resonable amount of time once the stream is started to /input I have to set master-update-interval very low, in this case 2.  Again have I missed something?

Thanks in advance for any help

icecast.xml :

<icecast>

<mount>
     <mount-name>/relay</mount-name>
     <burst-size>67000</burst-size>

     <fallback-mount>/Fallback</fallback-mount>
     <fallback-override>1</fallback-override>

</mount>

<mount>
     <mount-name>/input</mount-name>
     <stream-name>Input</stream-name>
     <stream-url>http://domain.name:8000/input</stream-url>
     <username>input</username>
     <password>input-password</password>
     <public>1</public>
     <burst-size>67000</burst-size>
</mount>

<relay>
    <server>domain.name</server>
    <port>8000</port>
    <mount>/input</mount>
    <local-mount>/relay</local-mount>
    <username>relay</username>
    <password>relay-password</password>
    <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
    <on-demand>0</on-demand>
</relay>

<mount>
     <mount-name>/Fallback</mount-name>
     <burst-size>6553</burst-size>
</mount>

<master-update-interval>2</master-update-interval>

    <location>location</location>
    <admin>admin</admin>

    <limits>
        <clients>2000</clients>
        <sources>30</sources>
        <queue-size>3932100</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>1</source-timeout>
             <burst-on-connect>1</burst-on-connect>
             <burst-size>131070</burst-size>
    </limits>

    <authentication>
        <source-password>source-password</source-password>
        <relay-password>relay-password</relay-password>
        <admin-user>admin</admin-user>
        <admin-password>admin-password</admin-password>
    </authentication>

    <hostname>domain.name</hostname>
    <server-id>icecast</server-id>

    <listen-socket>
        <port>8000</port>

    </listen-socket>

    <listen-socket>
        <port>8443</port>
        <ssl>1</ssl>
    </listen-socket>

    <http-headers>
        <header name="Access-Control-Allow-Origin" value="*" />
        <header name="X-Robots-Tag" value="noindex, noarchive, nofollow, noimageindex, nocache, nosnippet, notranslate, noyaca" status="200" />
        <header name="X-Clacks-Overhead" value="GNU Terry Pratchett" />
    </http-headers>

    <fileserve>1</fileserve>

    <paths>
        <basedir>/usr/share/icecast2</basedir>
        <logdir>/var/log/icecast2</logdir>
        <webroot>/usr/share/icecast2/web</webroot>
        <adminroot>/usr/share/icecast2/admin</adminroot>
        <alias source="/" destination="/status.xsl"/>
        <ssl-certificate>/etc/icecast2/cert/bundle.pem</ssl-certificate>
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
        <logsize>10000</logsize> <!-- Max size of a logfile -->
    </logging>

    <security>
        <chroot>0</chroot>
         <changeowner>
            <user>icecast2</user>
            <group>icecast</group>
         </changeowner>
    </security>
</icecast>




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20221017/aa81d9f2/attachment.htm>

From mrx23dot at gmail.com  Mon Oct 24 10:20:54 2022
From: mrx23dot at gmail.com (Arpad Toth)
Date: Mon, 24 Oct 2022 11:20:54 +0100
Subject: [Icecast] random reconnectdelay needed
Message-ID: <CAGuhpmzj_oG-NB210b-SPjn7hF0y0fPxfVRN0ushatykt-Y_Xw@mail.gmail.com>

Hello,

I have five ices2 running on a server, I weekly restart icecast
service as a good practice,

then ices2-s bombard the service with the same default timeout as a
result ~half of them fail and exit.

Some smarter back off timing would be nicer, like random expo or
handshake based.


Cheers,
Arpad


From mph at emotrics.com  Tue Oct 25 01:52:04 2022
From: mph at emotrics.com (Milton Huang)
Date: Mon, 24 Oct 2022 18:52:04 -0700
Subject: [Icecast] Fwd: notifying relays
In-Reply-To: <CAKSXWJ7sihmxQ7PJ9iZATZtupv32JGAr1yer+QMPBEPZ8Z6vow@mail.gmail.com>
References: <CAKSXWJ7sihmxQ7PJ9iZATZtupv32JGAr1yer+QMPBEPZ8Z6vow@mail.gmail.com>
Message-ID: <CAKSXWJ5Oj+09kA=xFC5qEz2sho1Qr+s_YrQJ9PXxOmhr4-jK9Q@mail.gmail.com>

I have a setup with an Icecast master server playing a continuous stream to
a Relay on an AWS instance, which in turn provides an SSL stream to the
world using the latest Icecast version 2.4.99.3. On occasion, we will start
a second stream for testing purposes. What I'm finding is there is a long
delay before the stream shows up, which I assume is related to the default
master-update-interval.  What I'm wondering is whether there is a way to
notify the Icecast relay that I'm starting a new stream, as it seems
wasteful to decrease the master-update-interval for something that only is
used on occasion.  I really don't need the relay to be constantly polling
besides making sure our main stream hasn't failed, as we only usually have
the one stream.

-milton
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20221024/b648206e/attachment.htm>

From mph at emotrics.com  Tue Oct 25 01:53:20 2022
From: mph at emotrics.com (Milton Huang)
Date: Mon, 24 Oct 2022 18:53:20 -0700
Subject: [Icecast] Relay errors in logs
In-Reply-To: <LOYP123MB31846C40AD6EBD926DF59428A8299@LOYP123MB3184.GBRP123.PROD.OUTLOOK.COM>
References: <LOYP123MB31843DE9DFAB248E3671A0C8A8549@LOYP123MB3184.GBRP123.PROD.OUTLOOK.COM>
 <LOYP123MB31846C40AD6EBD926DF59428A8299@LOYP123MB3184.GBRP123.PROD.OUTLOOK.COM>
Message-ID: <CAKSXWJ5ShxXGOiAnfuRvJV0jOqLKab8FbcXmFaDLnxJgQXmqVg@mail.gmail.com>

Not exactly sure I understand what you are trying to do, but I don't think
you need the <mount> section for the Fallback

> <mount>
>      <mount-name>/Fallback</mount-name>
>      <burst-size>6553</burst-size>
> </mount>

What happens if you delete it?

I am running into the same issue with waiting for the Relay to poll its
Master. I sent an email out about that on July 13th titled notifying relays but
never got a response from anyone. Maybe I messed up my address, I'll resend
and see if anyone has an idea.

On Mon, Oct 17, 2022 at 5:07 AM Dik .... <dik23 at hotmail.com> wrote:

> Doesn't anyone have any ideas about this?
> ------------------------------
> *From:* Icecast <icecast-bounces at xiph.org> on behalf of Dik .... <
> dik23 at hotmail.com>
> *Sent:* 28 September 2022 14:37
> *To:* Icecast user discussions <icecast at xiph.org>
> *Subject:* [Icecast] Relay errors in logs
>
> icecast2 2.4.4-3ubuntu0.1 Ubuntu 20.04.5
>
> I have set up a relay back to the localhost icecast server so that I can
> have one mountpoint with a fallback and one without
>
> I have 2 questions.  1st is why am I getting the following in error.log
> when nothing is connected to /input, is there anything I've missed?
>
> [2022-09-28  12:29:49] INFO slave/start_relay_stream Starting relayed
> source at mountpoint "/relay"
> [2022-09-28  12:29:49] INFO slave/open_relay_connection connecting to
> domain.name:8000
> [2022-09-28  12:29:49] INFO fserve/fserve_client_create checking for file
> /input (/usr/share/icecast2/web/input)
> [2022-09-28  12:29:49] WARN fserve/fserve_client_create req for file
> "/usr/share/icecast2/web/input" No such file or directory
> [2022-09-28  12:29:49] EROR slave/open_relay_connection Error from relay
> request: /relay (File Not Found)
>
>
> 2nd is in order for /relay to update in any resonable amount of time once
> the stream is started to /input I have to set master-update-interval very
> low, in this case 2.  Again have I missed something?
>
> Thanks in advance for any help
>
> icecast.xml :
>
> <icecast>
>
> <mount>
>      <mount-name>/relay</mount-name>
>      <burst-size>67000</burst-size>
>
>      <fallback-mount>/Fallback</fallback-mount>
>      <fallback-override>1</fallback-override>
>
> </mount>
>
> <mount>
>      <mount-name>/input</mount-name>
>      <stream-name>Input</stream-name>
>      <stream-url>http://domain.name:8000/input</stream-url>
>      <username>input</username>
>      <password>input-password</password>
>      <public>1</public>
>      <burst-size>67000</burst-size>
> </mount>
>
> <relay>
>     <server>domain.name</server>
>     <port>8000</port>
>     <mount>/input</mount>
>     <local-mount>/relay</local-mount>
>     <username>relay</username>
>     <password>relay-password</password>
>     <relay-shoutcast-metadata>0</relay-shoutcast-metadata>
>     <on-demand>0</on-demand>
> </relay>
>
> <mount>
>      <mount-name>/Fallback</mount-name>
>      <burst-size>6553</burst-size>
> </mount>
>
> <master-update-interval>2</master-update-interval>
>
>     <location>location</location>
>     <admin>admin</admin>
>
>     <limits>
>         <clients>2000</clients>
>         <sources>30</sources>
>         <queue-size>3932100</queue-size>
>         <client-timeout>30</client-timeout>
>         <header-timeout>15</header-timeout>
>         <source-timeout>1</source-timeout>
>              <burst-on-connect>1</burst-on-connect>
>              <burst-size>131070</burst-size>
>     </limits>
>
>     <authentication>
>         <source-password>source-password</source-password>
>         <relay-password>relay-password</relay-password>
>         <admin-user>admin</admin-user>
>         <admin-password>admin-password</admin-password>
>     </authentication>
>
>     <hostname>domain.name</hostname>
>     <server-id>icecast</server-id>
>
>     <listen-socket>
>         <port>8000</port>
>
>     </listen-socket>
>
>     <listen-socket>
>         <port>8443</port>
>         <ssl>1</ssl>
>     </listen-socket>
>
>     <http-headers>
>         <header name="Access-Control-Allow-Origin" value="*" />
>         <header name="X-Robots-Tag" value="noindex, noarchive, nofollow,
> noimageindex, nocache, nosnippet, notranslate, noyaca" status="200" />
>         <header name="X-Clacks-Overhead" value="GNU Terry Pratchett" />
>     </http-headers>
>
>     <fileserve>1</fileserve>
>
>     <paths>
>         <basedir>/usr/share/icecast2</basedir>
>         <logdir>/var/log/icecast2</logdir>
>         <webroot>/usr/share/icecast2/web</webroot>
>         <adminroot>/usr/share/icecast2/admin</adminroot>
>         <alias source="/" destination="/status.xsl"/>
>         <ssl-certificate>/etc/icecast2/cert/bundle.pem</ssl-certificate>
>     </paths>
>
>     <logging>
>         <accesslog>access.log</accesslog>
>         <errorlog>error.log</errorlog>
>         <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
>         <logsize>10000</logsize> <!-- Max size of a logfile -->
>     </logging>
>
>     <security>
>         <chroot>0</chroot>
>          <changeowner>
>             <user>icecast2</user>
>             <group>icecast</group>
>          </changeowner>
>     </security>
> </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/20221024/4f13092b/attachment.htm>

From phschafft at de.loewenfelsen.net  Wed Oct 26 09:19:41 2022
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Wed, 26 Oct 2022 09:19:41 +0000
Subject: [Icecast] Fwd: notifying relays
In-Reply-To: <CAKSXWJ5Oj+09kA=xFC5qEz2sho1Qr+s_YrQJ9PXxOmhr4-jK9Q@mail.gmail.com>
References: <CAKSXWJ7sihmxQ7PJ9iZATZtupv32JGAr1yer+QMPBEPZ8Z6vow@mail.gmail.com>
 <CAKSXWJ5Oj+09kA=xFC5qEz2sho1Qr+s_YrQJ9PXxOmhr4-jK9Q@mail.gmail.com>
Message-ID: <2d88ce2f4a2961ce4f12bc80fcbd0f7e7fea2906.camel@de.loewenfelsen.net>

Good morning,

On Mon, 2022-10-24 at 18:52 -0700, Milton Huang wrote:
> 
> [...] using the latest Icecast version 2.4.99.3. [...] What I'm
> wondering is whether there is a way to notify the Icecast relay that
> I'm starting a new stream, as it seems wasteful to decrease the
> master-update-interval for something that only is used on occasion. 
> I really don't need the relay to be constantly polling besides making
> sure our main stream hasn't failed, as we only usually have the one
> stream.

just to recap to see if I understood you correctly:
Basically you ask for an endpoint to force a reload of the stream list
from the master server?

With best regards,

-- 
Philipp Schafft (CEO/Gesch?ftsf?hrer) 
Telephon:  +49.3535 490 17 92
Website:   https://www.loewenfelsen.net/
Follow us: https://www.linkedin.com/company/loewenfelsen/

L?wenfelsen UG (haftungsbeschr?nkt)     Registration number:
Bickinger Stra?e 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20221026/8f5674d9/attachment.sig>