From rowland.cutler at bbc.co.uk  Fri Mar 26 07:29:28 2021
From: rowland.cutler at bbc.co.uk (Rowland Cutler)
Date: Fri, 26 Mar 2021 07:29:28 +0000
Subject: [Icecast] Segafaulting
Message-ID: <39163EB5-9976-46D6-8869-703F9CFAC132@bbc.co.uk>

Hi,

We?re using Icecast 2.4.4-1.8 on Rhel7.8 as a relay, and we are occasionally getting segfaults, forcing the service to restart.


# dmesg -T  | grep -i seg
[Tue Jan 19 11:57:01 2021] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
[Wed Feb 24 10:25:22 2021] icecast[14921]: segfault at 400006570 ip 00007f2e146dae07 sp 00007f2d87a75ac8 error 4 in libc-2.17.so[7f2e1459c000+1c3000]
[Sun Mar 14 00:11:02 2021] icecast[16241]: segfault at 8 ip 000000000041a240 sp 00007f638fc79b10 error 4 in icecast[400000+36000]

Anyone had the same issue? Got any ideas how to find out what?s going on?

Thanks in advance,

Ro.

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

From petr.pisar at atlas.cz  Fri Mar 26 13:14:39 2021
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Fri, 26 Mar 2021 14:14:39 +0100
Subject: [Icecast] Segafaulting
In-Reply-To: <39163EB5-9976-46D6-8869-703F9CFAC132@bbc.co.uk>
References: <39163EB5-9976-46D6-8869-703F9CFAC132@bbc.co.uk>
Message-ID: <YF3eP0+Vp7jQSs+c@dhcp-0-146.brq.redhat.com>

V?Fri, Mar 26, 2021 at 07:29:28AM +0000,?Rowland Cutler napsal(a):
> We?re using Icecast 2.4.4-1.8 on Rhel7.8 as a relay, and we are occasionally getting segfaults, forcing the service to restart.
> 
> 
> # dmesg -T  | grep -i seg
> [Tue Jan 19 11:57:01 2021] acpi PNP0A03:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI]
> [Wed Feb 24 10:25:22 2021] icecast[14921]: segfault at 400006570 ip 00007f2e146dae07 sp 00007f2d87a75ac8 error 4 in libc-2.17.so[7f2e1459c000+1c3000]
> [Sun Mar 14 00:11:02 2021] icecast[16241]: segfault at 8 ip 000000000041a240 sp 00007f638fc79b10 error 4 in icecast[400000+36000]
> 
> Anyone had the same issue? Got any ideas how to find out what?s going on?
> 
Install debuginfo packages for icecast and glibc, and configure abrt daemon.
When icecast crashes again, you can obtain a coredump from an abrt cache and
use GDB (or abrt tools) for obtaining a stack trace and exact line numbers
of icecast sources where the crash happened.

Alternatively you can retrieve the coredumps from system journal.

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210326/3cae1061/attachment.sig>

From uktony at radiocompany.net  Sun Mar 28 17:59:55 2021
From: uktony at radiocompany.net (Tony Harding)
Date: Mon, 29 Mar 2021 01:59:55 +0800
Subject: [Icecast] REQUEST: Certificate documentation
In-Reply-To: <mailman.18.1616953106.27061.icecast@xiph.org>
Message-ID: <20210328175958.CDC9940267@smtp2.osuosl.org>

I would like to request a section in the manual dedicated to CertificatesWith the https now becoming mandatory following the gods of Google changes, this is becoming a critical subject.The process of using certbot to get a certificate, putting <ssl>1</ssl> against all the ports and putting <ssl-certificate>/etc/letsencrypt/live/ice.something.com/fullchain.pem</ssl-certificate> in the icecast.xml is fraught and needs a definitive guide.Lack of understanding of Icecast by non-users can make seeking help from Cert forums a struggle.I have a cert on my machine, have the entries in the XML, but still fail to get it to work. I would guess this is going to be a growing problem and would suggest that this would be a help to all and resource for new users to be pointed to.Tony Harding



From pete at malibubeach.com  Sun Mar 28 02:38:02 2021
From: pete at malibubeach.com (Peter Tompkins)
Date: Sat, 27 Mar 2021 19:38:02 -0700
Subject: [Icecast] Problem streaming from RTLSDR-Airband
Message-ID: <1d0701d7237b$60b23400$22169c00$@malibubeach.com>

I am brand new to icecast so I suspect this will be a silly query to many
but I am out of ideas.  I am running RTLSDR-Airband and Icecast on the same
Rasberry Pi 4b.   The icecast admin pages work (and say there are no active
mount points), The airband status page shows valid numbers indicating it is
connected to the radio device and is capturing the requested frecuencies.
But both of them are reporting error messages regarding the connection
between the two.  There is clearly something I am missing to tell icecast
that this should be treated as a request from a source.

 

I see the following in the icecast error log (and a comparable error message
in the airband log).

 

[2021-03-27  19:04:50] WARN fserve/fserve_client_create req for file
"/usr/share/icecast2/web/ATIS" No such file or directory

 

I have an output defined in the airband config thusly:

   {

      freq = 126.025;

      outputs: (

        {

                  type = "icecast";

                  server = "localhost";

          port = 8000;

          mountpoint = "ATIS";

          name = "ATIS";

          genre = "ATC";

          description = "KCMA ATIS";

          username = "source";

          password = "KCMA";

                }

      );

    },

 

I made minimal changes to the default icecast config:

Set source-password to KCMA to match the password in the airband config

Left hostname to localhost (at least for now)

I have a listen socket for port 8000 

 

If I read the documentation correctly, I do not need to define a mount point
in the xml file: I think I read that should happen automatically with the
source connect, but it seems to be complaining that the mountpoint name is
not recognized ("ATIS")

 

I am hoping someone can tell me what stupid thing I am overlooking?

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

From epirat07 at gmail.com  Sun Mar 28 20:27:45 2021
From: epirat07 at gmail.com (Marvin Scholz)
Date: Sun, 28 Mar 2021 22:27:45 +0200
Subject: [Icecast] Problem streaming from RTLSDR-Airband
In-Reply-To: <1d0701d7237b$60b23400$22169c00$@malibubeach.com>
References: <1d0701d7237b$60b23400$22169c00$@malibubeach.com>
Message-ID: <07868599-2A58-4480-9775-D60181800697@gmail.com>

Hi,

On 28 Mar 2021, at 4:38, Peter Tompkins wrote:

> I am brand new to icecast so I suspect this will be a silly query to 
> many
> but I am out of ideas.  I am running RTLSDR-Airband and Icecast on the 
> same
> Rasberry Pi 4b.   The icecast admin pages work (and say there are no 
> active
> mount points), The airband status page shows valid numbers indicating 
> it is
> connected to the radio device and is capturing the requested 
> frecuencies.
> But both of them are reporting error messages regarding the connection
> between the two.  There is clearly something I am missing to tell 
> icecast
> that this should be treated as a request from a source.
>
>
>
> I see the following in the icecast error log (and a comparable error 
> message
> in the airband log).
>
>
>
> [2021-03-27  19:04:50] WARN fserve/fserve_client_create req for file
> "/usr/share/icecast2/web/ATIS" No such file or directory
>
>

This is just an warning you will get when you try to request a 
mountpoint
that is not streamed to, as Icecast will then look for a file in the
webroot instead and this is the warning that it founds none, IIRC.

>
> I have an output defined in the airband config thusly:
>
>    {
>
>       freq = 126.025;
>
>       outputs: (
>
>         {
>
>                   type = "icecast";
>
>                   server = "localhost";
>
>           port = 8000;
>
>           mountpoint = "ATIS";
>
>           name = "ATIS";
>
>           genre = "ATC";
>
>           description = "KCMA ATIS";
>
>           username = "source";
>
>           password = "KCMA";
>
>                 }
>
>       );
>
>     },
>
>

Do you have any logs of the source client (Airband, I guess)?

>
> I made minimal changes to the default icecast config:
>
> Set source-password to KCMA to match the password in the airband 
> config
>
> Left hostname to localhost (at least for now)
>
> I have a listen socket for port 8000
>

Sounds fine, for now, and should work.

>
>
> If I read the documentation correctly, I do not need to define a mount 
> point
> in the xml file: I think I read that should happen automatically with 
> the
> source connect, but it seems to be complaining that the mountpoint 
> name is
> not recognized ("ATIS")
>

Yep, there is no need to explicitly configure any mountpoint in the XML
usually.

>
>
> I am hoping someone can tell me what stupid thing I am overlooking?


Can you share the error and access logs? If Airband tries to connect as 
source,
it definitely should be logged in there.


> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From pete at malibubeach.com  Mon Mar 29 03:47:44 2021
From: pete at malibubeach.com (pete at malibubeach.com)
Date: Sun, 28 Mar 2021 20:47:44 -0700
Subject: [Icecast] Problem streaming from RTLSDR-Airband
In-Reply-To: <07868599-2A58-4480-9775-D60181800697@gmail.com>
References: <1d0701d7237b$60b23400$22169c00$@malibubeach.com>
 <07868599-2A58-4480-9775-D60181800697@gmail.com>
Message-ID: <001601d7244e$4829d8b0$d87d8a10$@malibubeach.com>

30 seconds with wireshark solved the problem --- the source program was not resolving 'localhost'  (no IP traffic was a dead giveaway?.  Changed its config file to 127.0.0.1 and it connects now.

I appreciate your reply.

-----Original Message-----
From: Icecast <icecast-bounces at xiph.org> On Behalf Of Marvin Scholz
Sent: Sunday, March 28, 2021 1:28 PM
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] Problem streaming from RTLSDR-Airband

Hi,

On 28 Mar 2021, at 4:38, Peter Tompkins wrote:

> I am brand new to icecast so I suspect this will be a silly query to 
> many but I am out of ideas.  I am running RTLSDR-Airband and Icecast 
> on the same
> Rasberry Pi 4b.   The icecast admin pages work (and say there are no 
> active
> mount points), The airband status page shows valid numbers indicating 
> it is connected to the radio device and is capturing the requested 
> frecuencies.
> But both of them are reporting error messages regarding the connection 
> between the two.  There is clearly something I am missing to tell 
> icecast that this should be treated as a request from a source.
>
>
>
> I see the following in the icecast error log (and a comparable error 
> message in the airband log).
>
>
>
> [2021-03-27  19:04:50] WARN fserve/fserve_client_create req for file
> "/usr/share/icecast2/web/ATIS" No such file or directory
>
>

This is just an warning you will get when you try to request a 
mountpoint
that is not streamed to, as Icecast will then look for a file in the
webroot instead and this is the warning that it founds none, IIRC.

>
> I have an output defined in the airband config thusly:
>
>    {
>
>       freq = 126.025;
>
>       outputs: (
>
>         {
>
>                   type = "icecast";
>
>                   server = "localhost";
>
>           port = 8000;
>
>           mountpoint = "ATIS";
>
>           name = "ATIS";
>
>           genre = "ATC";
>
>           description = "KCMA ATIS";
>
>           username = "source";
>
>           password = "KCMA";
>
>                 }
>
>       );
>
>     },
>
>

Do you have any logs of the source client (Airband, I guess)?

>
> I made minimal changes to the default icecast config:
>
> Set source-password to KCMA to match the password in the airband 
> config
>
> Left hostname to localhost (at least for now)
>
> I have a listen socket for port 8000
>

Sounds fine, for now, and should work.

>
>
> If I read the documentation correctly, I do not need to define a mount 
> point
> in the xml file: I think I read that should happen automatically with 
> the
> source connect, but it seems to be complaining that the mountpoint 
> name is
> not recognized ("ATIS")
>

Yep, there is no need to explicitly configure any mountpoint in the XML
usually.

>
>
> I am hoping someone can tell me what stupid thing I am overlooking?


Can you share the error and access logs? If Airband tries to connect as 
source,
it definitely should be logged in there.


> _______________________________________________
> 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



From mail at psychedelik.com  Mon Mar 29 08:10:58 2021
From: mail at psychedelik.com (mail at psychedelik.com)
Date: Mon, 29 Mar 2021 10:10:58 +0200
Subject: [Icecast] REQUEST: Certificate documentation
In-Reply-To: <20210328175958.CDC9940267@smtp2.osuosl.org>
References: <20210328175958.CDC9940267@smtp2.osuosl.org>
Message-ID: <8377fa2c4c33c923779061beec1fe5cb@psychedelik.com>

Hi Tony,

I'm not a cutting-edge user of Icecast/Linux but I'll be glad to help.
My icecast stream with SSL is there : 
https://icecast.psychedelik.com:8010/ambient320
Just to let you know that we can get it to work.

How did you define your fullchain.pem?
Could you share your icecast.xml?

BG



On 28.03.2021 19:59, Tony Harding wrote:
> I would like to request a section in the manual dedicated to
> CertificatesWith the https now becoming mandatory following the gods
> of Google changes, this is becoming a critical subject.The process of
> using certbot to get a certificate, putting <ssl>1</ssl> against all
> the ports and putting
> <ssl-certificate>/etc/letsencrypt/live/ice.something.com/fullchain.pem</ssl-certificate>
> in the icecast.xml is fraught and needs a definitive guide.Lack of
> understanding of Icecast by non-users can make seeking help from Cert
> forums a struggle.I have a cert on my machine, have the entries in the
> XML, but still fail to get it to work. I would guess this is going to
> be a growing problem and would suggest that this would be a help to
> all and resource for new users to be pointed to.Tony Harding
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From dik23 at hotmail.com  Tue Mar 30 11:39:04 2021
From: dik23 at hotmail.com (Dik ....)
Date: Tue, 30 Mar 2021 11:39:04 +0000
Subject: [Icecast] Reliable method to kick broadcaster
Message-ID: <LO0P265MB3179E6964D5ACBCCDE4D91A8A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>

We're running live DJ shows who broadcast using butt to icecast running on linux

What we're concerned about is DJs failing to disconnect.  Does anyone here have a fool proof way to kick a broadcaster?  Is there something we could do with icecast itself or should we be looking at iptables drop / reject?

Thanks in advance for any input
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210330/744ffcc4/attachment.htm>

From dik23 at hotmail.com  Tue Mar 30 12:03:01 2021
From: dik23 at hotmail.com (Dik ....)
Date: Tue, 30 Mar 2021 12:03:01 +0000
Subject: [Icecast] Reliable method to kick broadcaster
In-Reply-To: <LO0P265MB3179E6964D5ACBCCDE4D91A8A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB3179E6964D5ACBCCDE4D91A8A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <LO0P265MB3179ED2765BAD093C8C514A3A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>

Sorry, I should add that while Kill Source will kick a broadcaster butt will automatically reconnect

________________________________
From: Icecast <icecast-bounces at xiph.org> on behalf of Dik .... <dik23 at hotmail.com>
Sent: 30 March 2021 12:39
To: Icecast user discussions <icecast at xiph.org>
Subject: [Icecast] Reliable method to kick broadcaster

We're running live DJ shows who broadcast using butt to icecast running on linux

What we're concerned about is DJs failing to disconnect.  Does anyone here have a fool proof way to kick a broadcaster?  Is there something we could do with icecast itself or should we be looking at iptables drop / reject?

Thanks in advance for any input
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210330/2bf3b4cb/attachment.htm>

From phschafft at de.loewenfelsen.net  Tue Mar 30 17:52:54 2021
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Tue, 30 Mar 2021 17:52:54 +0000
Subject: [Icecast] REQUEST: Certificate documentation
In-Reply-To: <20210328175958.CDC9940267@smtp2.osuosl.org>
References: <20210328175958.CDC9940267@smtp2.osuosl.org>
Message-ID: <93c36ca96011e736849808cb37455a79111cc3dd.camel@de.loewenfelsen.net>

Good afternoon,

On Mon, 2021-03-29 at 01:59 +0800, Tony Harding wrote:
> I would like to request a section in the manual dedicated to
> CertificatesWith the https now becoming mandatory following the gods
> of Google changes, this is becoming a critical subject.The process of
> using certbot to get a certificate, putting <ssl>1</ssl> against all
> the ports and putting <ssl-
> certificate>/etc/letsencrypt/live/ice.something.com/fullchain.pem</ss
> l-certificate> in the icecast.xml is fraught and needs a definitive
> guide.Lack of understanding of Icecast by non-users can make seeking
> help from Cert forums a struggle.I have a cert on my machine, have
> the entries in the XML, but still fail to get it to work. I would
> guess this is going to be a growing problem and would suggest that
> this would be a help to all and resource for new users to be pointed
> to.Tony Harding

May I ask which forums you are referring to?

Other than that, hm. Yes, maybe we could add something to the FAQ
and/or the 2.5.x docs. I mean, docs can always be improved. ;)

Maybe you want to open another thread for your current problem?

Also if there is interest for professional help, feel free to send me a
mail off-list.

With best regards,

-- 
Philipp Schafft (CEO/Gesch?ftsf?hrer) 
Telephon: +49.3535 490 17 92

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: 523 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210330/a54aed29/attachment.sig>

From phschafft at de.loewenfelsen.net  Tue Mar 30 17:47:10 2021
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Tue, 30 Mar 2021 17:47:10 +0000
Subject: [Icecast] Reliable method to kick broadcaster
In-Reply-To: <LO0P265MB3179ED2765BAD093C8C514A3A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>
References: <LO0P265MB3179E6964D5ACBCCDE4D91A8A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>
 <LO0P265MB3179ED2765BAD093C8C514A3A87D9@LO0P265MB3179.GBRP265.PROD.OUTLOOK.COM>
Message-ID: <b824232181131d2f2728aa94c39f0591d15c7dfc.camel@de.loewenfelsen.net>

Good afternoon,

On Tue, 2021-03-30 at 12:03 +0000, Dik .... wrote:
> Sorry, I should add that while Kill Source will kick a broadcaster
> butt will automatically reconnect
> 
> ________________________________
> From: Icecast <icecast-bounces at xiph.org> on behalf of Dik .... <
> dik23 at hotmail.com>
> Sent: 30 March 2021 12:39
> To: Icecast user discussions <icecast at xiph.org>
> Subject: [Icecast] Reliable method to kick broadcaster
> 
> We're running live DJ shows who broadcast using butt to icecast
> running on linux
> 
> What we're concerned about is DJs failing to disconnect.  Does anyone
> here have a fool proof way to kick a broadcaster?  Is there something
> we could do with icecast itself or should we be looking at iptables
> drop / reject?

There is no direct way to do that with Icecast. Icecast just can not
tell "good" from "bad" sources apart but for block lists and
credentials.

Ideally each DJ has his own credentials, so you can control access by
that. This way Icecast knows which of your DJs this specific source is
and can therefore accept, or reject the request.

If that is not possible you can block by IP. Icecast supports blocking,
however your standard firewall might be the more flexible solution
here. That depends a bit on what your setup looks like.

Hopefully that helps you a bit.

With best regards,

-- 
Philipp Schafft (CEO/Gesch?ftsf?hrer) 
Telephon: +49.3535 490 17 92

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: 523 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20210330/a1bab8a7/attachment.sig>