From ak18 at 5x9.de  Fri Aug  3 16:38:02 2018
From: ak18 at 5x9.de (ak18 at 5x9.de)
Date: Fri, 3 Aug 2018 18:38:02 +0200
Subject: [Icecast] Mount with Relay: Fallback-override does not work
Message-ID: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>

Hello,

I'm using Icecast over 10 years, so let me first say *Thank you to all 
developers* of Icecast!

I have a problem using a mount with relay and a fallback. The option 
<fallback-override> is not working.

I tested two different configurations:

_Configuration A:_

 ??? <mount>
 ??????? <mount-name>/Stream-096k.mp3</mount-name>
 ??????? <max-listeners>2000</max-listeners>
 ??????? <burst-size>122880</burst-size>
<fallback-mount>/Recordings/Record1.mp3</fallback-mount>
 ??????? <fallback-override>1</fallback-override>
 ??? </mount>
 ??? <relay>
 ??????? <server>xxx.xxx.xxx.xxx</server>
 ??????? <port>8080</port>
 ??????? <mount>/Masterstream-096k.mp3</mount>
 ??????? <local-mount>/Stream-096k.mp3</local-mount>
 ??????? <on-demand>1</on-demand>
 ? ? ?? <fallback-override>1</fallback-override>
 ??? </relay>

_Configuration B:_

 ??? <mount>
 ??????? <mount-name>/Stream-096k.mp3</mount-name>
 ??????? <max-listeners>2000</max-listeners>
 ??????? <burst-size>122880</burst-size>
<fallback-mount>/Stream-Recorded.mp3</fallback-mount>
 ??????? <fallback-override>1</fallback-override>
 ??? </mount>
 ??? <relay>
 ??????? <server>xxx.xxx.xxx.xxx</server>
 ??????? <port>8080</port>
 ??????? <mount>/Masterstream-096k.mp3</mount>
 ??????? <local-mount>/Stream-096k.mp3</local-mount>
 ??????? <on-demand>1</on-demand>
 ? ? ?? <fallback-override>1</fallback-override>
 ??? </relay>

 ??? <mount>
 ??????? <mount-name>/Stream-Recorded.mp3</mount-name>
 ??????? <max-listeners>2000</max-listeners>
 ??????? <burst-size>61440</burst-size>
<fallback-mount>/Recordings/Record1.mp3</fallback-mount>
 ??????? <fallback-override>1</fallback-override>
 ? ?? ?? <limit-rate>49152</limit-rate>
 ??? </mount>

Problem 1:
In both configurations the fallback is played if the relay is offline. 
But if the stream of the relay is going to online, the listeners are not 
switched back from the fallback. Even if I wait hours, that does not happen.
Currently I still use the older icecast-version 2.3.1 - so pherhals this 
could be the reason...

Problem 2:
I also found that <limit-rate> (I did not find this option in the 
dokumentation, why?) does not have any effect, no matter what value I 
used. Maybe it's because of the older version? (I used limit-rate 
because the recording is 48k instead of 96k).

Kind regards.

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

From ross at stationplaylist.com  Sat Aug  4 14:12:50 2018
From: ross at stationplaylist.com (Ross Levis)
Date: Sun, 5 Aug 2018 02:12:50 +1200
Subject: [Icecast] DNAS v1 YP
Message-ID: <004801d42bfd$3c15f820$b441e860$@com>

I've been told that Icecast streams could be listed on the popular
Shoutcast.com directory if it supported the new DNAS v2 protocol for YP
updates.  Any thoughts of adding support for that?




From epirat07 at gmail.com  Sat Aug  4 19:00:29 2018
From: epirat07 at gmail.com (Marvin Scholz)
Date: Sat, 04 Aug 2018 21:00:29 +0200
Subject: [Icecast] DNAS v1 YP
In-Reply-To: <004801d42bfd$3c15f820$b441e860$@com>
References: <004801d42bfd$3c15f820$b441e860$@com>
Message-ID: <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>



On 4 Aug 2018, at 16:12, Ross Levis wrote:

> I've been told that Icecast streams could be listed on the popular
> Shoutcast.com directory if it supported the new DNAS v2 protocol for YP
> updates.  Any thoughts of adding support for that?

There are no plans to add that. And personally I would oppose such an
addition. (Thats just my opinion, not sure what the opinion of the other
Icecast developers is about that.)

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


From thomas at ruecker.fi  Sat Aug  4 20:16:08 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Sat, 4 Aug 2018 20:16:08 +0000
Subject: [Icecast] DNAS v1 YP
In-Reply-To: <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>
References: <004801d42bfd$3c15f820$b441e860$@com>
 <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>
Message-ID: <5038af26-09c2-ce52-8d24-5c800ad5b852@ruecker.fi>

On 08/04/2018 07:00 PM, Marvin Scholz wrote:
>
> On 4 Aug 2018, at 16:12, Ross Levis wrote:
>
>> I've been told that Icecast streams could be listed on the popular
>> Shoutcast.com directory if it supported the new DNAS v2 protocol for YP
>> updates.  Any thoughts of adding support for that?
> There are no plans to add that. And personally I would oppose such an
> addition. (Thats just my opinion, not sure what the opinion of the other
> Icecast developers is about that.)

Last I heard they were accepting YP submissions (only for MP3 and AAC
though) from Icecast servers.
Did that change?

TBR


From ross at stationplaylist.com  Sun Aug  5 00:50:34 2018
From: ross at stationplaylist.com (Ross Levis)
Date: Sun, 5 Aug 2018 12:50:34 +1200
Subject: [Icecast] DNAS v1 YP
In-Reply-To: <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>
References: <004801d42bfd$3c15f820$b441e860$@com>
 <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>
Message-ID: <006401d42c56$52fdc780$f8f95680$@com>

It may mean we will have to have to drop using Icecast for our hosting service and switch to Shoutcast. That would be a big disappointment.
 
Shoutcast.com were supporting the DNAS v1 YP updates from Icecast until a few months ago when they stopped it, due to support for Shoutcast v1 being dropped.  It wasn't designed to stop Icecast updates but that is now the result.

Shoutcast.com is a major director that internet stations need to be on.  We have customers complaining why they are not listed any longer.

-----Original Message-----
From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Marvin Scholz
Sent: Sunday, 5 August 2018 7:00 a.m.
To: Icecast streaming server user discussions
Subject: Re: [Icecast] DNAS v1 YP



On 4 Aug 2018, at 16:12, Ross Levis wrote:

> I've been told that Icecast streams could be listed on the popular 
> Shoutcast.com directory if it supported the new DNAS v2 protocol for 
> YP updates.  Any thoughts of adding support for that?

There are no plans to add that. And personally I would oppose such an addition. (Thats just my opinion, not sure what the opinion of the other Icecast developers is about that.)

>
>
> _______________________________________________
> 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 ross at stationplaylist.com  Sun Aug  5 02:34:40 2018
From: ross at stationplaylist.com (Ross Levis)
Date: Sun, 5 Aug 2018 14:34:40 +1200
Subject: [Icecast] DNAS v1 YP
In-Reply-To: <5038af26-09c2-ce52-8d24-5c800ad5b852@ruecker.fi>
References: <004801d42bfd$3c15f820$b441e860$@com>
 <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>
 <5038af26-09c2-ce52-8d24-5c800ad5b852@ruecker.fi>
Message-ID: <008f01d42c64$ddc5b360$99511a20$@com>

Yes it has changed.  They stopped Shoutcast v1 servers from submitting YP updates and in the process it stopped Icecast servers since it uses the same protocol.

-----Original Message-----
From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Thomas B. R?cker
Sent: Sunday, 5 August 2018 8:16 a.m.
To: icecast at xiph.org
Subject: Re: [Icecast] DNAS v1 YP

On 08/04/2018 07:00 PM, Marvin Scholz wrote:
>
> On 4 Aug 2018, at 16:12, Ross Levis wrote:
>
>> I've been told that Icecast streams could be listed on the popular 
>> Shoutcast.com directory if it supported the new DNAS v2 protocol for 
>> YP updates.  Any thoughts of adding support for that?
> There are no plans to add that. And personally I would oppose such an 
> addition. (Thats just my opinion, not sure what the opinion of the 
> other Icecast developers is about that.)

Last I heard they were accepting YP submissions (only for MP3 and AAC
though) from Icecast servers.
Did that change?

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




From thomas at ruecker.fi  Sun Aug  5 08:24:39 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Sun, 5 Aug 2018 08:24:39 +0000
Subject: [Icecast] DNAS v1 YP
In-Reply-To: <008f01d42c64$ddc5b360$99511a20$@com>
References: <004801d42bfd$3c15f820$b441e860$@com>
 <4E3EB6B3-ED54-432B-9BA3-3CB78A6C084A@gmail.com>
 <5038af26-09c2-ce52-8d24-5c800ad5b852@ruecker.fi>
 <008f01d42c64$ddc5b360$99511a20$@com>
Message-ID: <cd078d44-30d9-e771-fdbd-792c00301548@ruecker.fi>


> -----Original Message-----
> From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of Thomas B. R?cker
> Sent: Sunday, 5 August 2018 8:16 a.m.
>
> On 08/04/2018 07:00 PM, Marvin Scholz wrote:
>> On 4 Aug 2018, at 16:12, Ross Levis wrote:
>>
>>> I've been told that Icecast streams could be listed on the popular 
>>> Shoutcast.com directory if it supported the new DNAS v2 protocol for 
>>> YP updates.  Any thoughts of adding support for that?
>> There are no plans to add that. And personally I would oppose such an 
>> addition. (Thats just my opinion, not sure what the opinion of the 
>> other Icecast developers is about that.)
> Last I heard they were accepting YP submissions (only for MP3 and AAC
> though) from Icecast servers.
> Did that change?

On 08/05/2018 02:34 AM, Ross Levis wrote:
> Yes it has changed.  They stopped Shoutcast v1 servers from submitting YP updates and in the process it stopped Icecast servers since it uses the same protocol.

Well, that's certainly unfortunate for those who used this.

The Icecast core team have our plate full with items that we want to
have as part of our upcoming 2.5 release. So as Marvin pointed out we
currently have no plans for this.

*IF* there is someone who wants to take the lead on this topic and see
*IF* there is a way to get an Radionomy (shoutcast owners) approved
solution. I'd recommend to continue this discussion on the
icecast-dev at xiph.org mailing list. I am somewhat skeptical, based on how
they handled this situation (e.g. nobody contacted us) and the previous
track record of denying Icecast listings for many years. I took a brief
look at their Wiki and it looks somewhat incomplete regarding listing
submission. It only talks about generating "AuthKeys".

Proactive communication with all parties involved is the most likely way
to lead to a resolution.


TBR

PS: Please consider configuring your email client for inline quoting. It
makes such discussions a lot more readable.



From pm at nowster.me.uk  Sun Aug  5 19:40:22 2018
From: pm at nowster.me.uk (Paul Martin)
Date: Sun, 5 Aug 2018 20:40:22 +0100
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
Message-ID: <20180805194022.GA2520@thinkpad.nowster.org.uk>

On Fri, Aug 03, 2018 at 06:38:02PM +0200, ak18 at 5x9.de wrote:
> ??? <mount>
> ??????? <mount-name>/Stream-096k.mp3</mount-name>
> ??????? <max-listeners>2000</max-listeners>
> ??????? <burst-size>122880</burst-size>
> <fallback-mount>/Stream-Recorded.mp3</fallback-mount>
> ??????? <fallback-override>1</fallback-override>
> ??? </mount>

> Problem 1:
> In both configurations the fallback is played if the relay is offline. But
> if the stream of the relay is going to online, the listeners are not
> switched back from the fallback. Even if I wait hours, that does not happen.
> Currently I still use the older icecast-version 2.3.1 - so pherhals this
> could be the reason...

Fallback to a file just fills up buffers as fast as it can.  Not a
good idea at all as Icecast will keep buffering pretty much until it
runs out of memory if you're operating a relay.  Better to use a local
encoder (eg. liquidsoap) which does proper rate limiting.

"Note that the fallback file is not timed so be careful if you intend
to relay this. They are fine on slave streams but don?t use them on
master streams, if you do then the relay will consume stream data at a
faster rate and the listeners on the relay would eventually get kicked
off."

http://icecast.org/docs/icecast-2.4.1/config-file.html#relay

> Problem 2:
> I also found that <limit-rate> (I did not find this option in the
> dokumentation, why?)

Are you using the standard icecast2 or the kh (Karl Heyes) version?

-- 
Paul Martin <pm at nowster.me.uk>


From ak18 at 5x9.de  Mon Aug  6 12:26:26 2018
From: ak18 at 5x9.de (ak18 at 5x9.de)
Date: Mon, 6 Aug 2018 14:26:26 +0200
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <20180805194022.GA2520@thinkpad.nowster.org.uk>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
 <20180805194022.GA2520@thinkpad.nowster.org.uk>
Message-ID: <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>

Am 05.08.2018 um 21:40 schrieb Paul Martin:
>
> Fallback to a file just fills up buffers as fast as it can.  Not a
> good idea at all as Icecast will keep buffering pretty much until it
> runs out of memory if you're operating a relay.  Better to use a local
> encoder (eg. liquidsoap) which does proper rate limiting.
Thank you, but the buffering is not my problem, because I'm using a 
master-icecast-server which buffers the file only one time for all 
slave-icecast-servers. "liquidsoap" is not available for windows!?
>
>> Problem 2:
>> I also found that <limit-rate> (I did not find this option in the
>> dokumentation, why?)
> Are you using the standard icecast2 or the kh (Karl Heyes) version?
I'm using the versions from icecast.org.

Thanks so far


From pm at nowster.me.uk  Tue Aug  7 12:52:00 2018
From: pm at nowster.me.uk (Paul Martin)
Date: Tue, 7 Aug 2018 13:52:00 +0100
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
 <20180805194022.GA2520@thinkpad.nowster.org.uk>
 <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>
Message-ID: <20180807125200.GC19453@nowster.org.uk>

On Mon, Aug 06, 2018 at 02:26:26PM +0200, ak18 at 5x9.de wrote:
> Am 05.08.2018 um 21:40 schrieb Paul Martin:
> > 
> > Fallback to a file just fills up buffers as fast as it can.  Not a
> > good idea at all as Icecast will keep buffering pretty much until it
> > runs out of memory if you're operating a relay.  Better to use a local
> > encoder (eg. liquidsoap) which does proper rate limiting.
> Thank you, but the buffering is not my problem, because I'm using a
> master-icecast-server which buffers the file only one time for all
> slave-icecast-servers. "liquidsoap" is not available for windows!?

Read the documentation:

If you have to do file-based fallback, don't do fallback on the
master. Do it on the slaves.

-- 
Paul Martin <pm at nowster.me.uk>


From ak18 at 5x9.de  Tue Aug  7 14:12:45 2018
From: ak18 at 5x9.de (ak18 at 5x9.de)
Date: Tue, 7 Aug 2018 16:12:45 +0200
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <20180807125200.GC19453@nowster.org.uk>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
 <20180805194022.GA2520@thinkpad.nowster.org.uk>
 <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>
 <20180807125200.GC19453@nowster.org.uk>
Message-ID: <6846f0fd-af6e-b6b5-fc81-b9768c9c98fb@5x9.de>

Am 07.08.2018 um 14:52 schrieb Paul Martin:

> Read the documentation:
> If you have to do file-based fallback, don't do fallback on the
> master. Do it on the slaves.
>
Both configurations that I have posted are from the slave !
The <reply> is going the the master, the fallback is on the slave !

The problem is, using a mount with relay and a fallback on the slave! 
The option <fallback-override> is not working.

The salve is running version 2.4.1 of icecast from icecast.org.

> Are you using the standard icecast2 or the kh (Karl Heyes) version?
What is the difference between these version? I think kh is the 
developer and this version is newer (or better?) There can I get this 
kh-version?



From dave at dashs.denver.co.us  Tue Aug  7 18:55:10 2018
From: dave at dashs.denver.co.us (Dave Serls)
Date: Tue, 7 Aug 2018 12:55:10 -0600
Subject: [Icecast] YP registration for Authenticated streams
Message-ID: <20180807125510.59df414b@groucho.dashs.denver.co.us>


 Is it possible to register ones icecast streams at dir.xiph.org if they require 
 URL authentication? 
-- 
************************************************************************
*   Dave Serls                                 Littleton, CO, USA      *
*   dashs.denver.co.us                         http://www.dashs.com    *
************************************************************************


From epirat07 at gmail.com  Tue Aug  7 19:20:07 2018
From: epirat07 at gmail.com (Marvin Scholz)
Date: Tue, 07 Aug 2018 21:20:07 +0200
Subject: [Icecast] YP registration for Authenticated streams
In-Reply-To: <20180807125510.59df414b@groucho.dashs.denver.co.us>
References: <20180807125510.59df414b@groucho.dashs.denver.co.us>
Message-ID: <946A1356-1F5E-48C4-86FD-D22F8AF7140D@gmail.com>

On 7 Aug 2018, at 20:55, Dave Serls wrote:

>  Is it possible to register ones icecast streams at dir.xiph.org if 
> they require
>  URL authentication?

Why would it be useful to have streams in the directory that users can 
not listen
to because they require auth?

> -- 
> ************************************************************************
> *   Dave Serls                                 Littleton, CO, USA      
> *
> *   dashs.denver.co.us                         http://www.dashs.com    
> *
> ************************************************************************
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From dave at dashs.denver.co.us  Tue Aug  7 20:21:21 2018
From: dave at dashs.denver.co.us (Dave Serls)
Date: Tue, 7 Aug 2018 14:21:21 -0600
Subject: [Icecast] YP registration for Authenticated streams
In-Reply-To: <946A1356-1F5E-48C4-86FD-D22F8AF7140D@gmail.com>
References: <20180807125510.59df414b@groucho.dashs.denver.co.us>
 <946A1356-1F5E-48C4-86FD-D22F8AF7140D@gmail.com>
Message-ID: <20180807142121.1da1f4a4@groucho.dashs.denver.co.us>

On Tue, 07 Aug 2018 21:20:07 +0200
"Marvin Scholz" <epirat07 at gmail.com> wrote:

> On 7 Aug 2018, at 20:55, Dave Serls wrote:
> 
> >  Is it possible to register ones icecast streams at dir.xiph.org if 
> > they require
> >  URL authentication?  
> 
> Why would it be useful to have streams in the directory that users can 
> not listen
> to because they require auth?

  Ah. Answering a question with a question.
  I do not know if dir.xiph.org is included as a standard for internet radio appliances.
  Or is included in searches made from other sites.
  I am only interested in servicing users who may also use my email server, who will
  provide IP addresses that have been white-listed here for URL auth.
  Now can you provide an answer to my question?
> 
> > -- 
> > ************************************************************************
> > *   Dave Serls                                 Littleton, CO, USA      
> > *
> > *   dashs.denver.co.us                         http://www.dashs.com    
> > *
> > ************************************************************************
> > _______________________________________________
> > 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


-- 
************************************************************************
*   Dave Serls                                 Littleton, CO, USA      *
*   dashs.denver.co.us                         http://www.dashs.com    *
************************************************************************


From wayne at cffcs.com  Wed Aug  8 02:32:50 2018
From: wayne at cffcs.com (Wayne Barron)
Date: Tue, 7 Aug 2018 22:32:50 -0400
Subject: [Icecast] Icecast not working (error log provided)
Message-ID: <CAJatk5m5z+hovmerFHvSgoGiYXBf35dOH=Mp_w5y=ytwyEsGeQ@mail.gmail.com>

Hello all;

I have Icecast2 and Liquidsoap installed on an Ubuntu Server.

This is the error log from the server

[2018-08-08  02:22:18] INFO sighandler/_sig_die Caught signal 15,
shutting down...
[2018-08-08  02:22:18] INFO main/main Shutting down
[2018-08-08  02:22:18] INFO fserve/fserve_shutdown file serving stopped
[2018-08-08  02:22:18] INFO slave/_slave_thread shutting down current relays
[2018-08-08  02:22:18] INFO slave/_slave_thread Slave thread shutdown complete
[2018-08-08  02:22:18] INFO auth/auth_shutdown Auth shutdown
[2018-08-08  02:22:18] INFO yp/yp_shutdown YP thread down
[2018-08-08  02:22:19] INFO stats/stats_shutdown stats thread finished
[2018-08-08  02:22:19] INFO main/main Icecast 2.4.3 server started
[2018-08-08  02:22:19] INFO connection/get_ssl_certificate No SSL capability
[2018-08-08  02:22:19] INFO stats/_stats_thread stats thread started
[2018-08-08  02:22:19] INFO yp/yp_update_thread YP update thread started

On the web admin page. It is not showing anything under
Mountpoint list
Server Status
Public Home

Information only showed under
Admin Home
Version

Could someone please let me know what my next step should be?
Thank you

Wayne


From thomas at ruecker.fi  Wed Aug  8 05:41:05 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Wed, 8 Aug 2018 05:41:05 +0000
Subject: [Icecast] YP registration for Authenticated streams
In-Reply-To: <20180807142121.1da1f4a4@groucho.dashs.denver.co.us>
References: <20180807125510.59df414b@groucho.dashs.denver.co.us>
 <946A1356-1F5E-48C4-86FD-D22F8AF7140D@gmail.com>
 <20180807142121.1da1f4a4@groucho.dashs.denver.co.us>
Message-ID: <5c90812a-1b9a-98ea-59ef-d5f0c7f7860c@ruecker.fi>

Hi,


On 08/07/2018 08:21 PM, Dave Serls wrote:
> On Tue, 07 Aug 2018 21:20:07 +0200
> "Marvin Scholz" <epirat07 at gmail.com> wrote:
>
>> On 7 Aug 2018, at 20:55, Dave Serls wrote:
>>
>>>  Is it possible to register ones icecast streams at dir.xiph.org if 
>>> they require
>>>  URL authentication?  
>> Why would it be useful to have streams in the directory that users can 
>> not listen
>> to because they require auth?
>   Ah. Answering a question with a question.
>   I do not know if dir.xiph.org is included as a standard for internet radio appliances.
>   Or is included in searches made from other sites.
>   I am only interested in servicing users who may also use my email server, who will
>   provide IP addresses that have been white-listed here for URL auth.

It is far easier for us to really help people if we understand their
motivation.
Personally I've seen probably 70% of user questions for projects that
I'm involved in arrive at solutions that were different from the
original technical question setting. So while answering a question with
a question maybe doesn't feel very nice, I can understand why Marvin did
so. My answer would probably have been "Not really, but could you explain?"
In your case we'd probably suggest to address this possible use-case in
a different way. If you'd be interested in actually solving your issue
instead of an answer to one particular technical aspect that is.


>   Now can you provide an answer to my question?

No, we kindly ask you not to attempt to list streams that need
authentication of any kind. The directory is intended for freely
accessible streams.
Also we would prefer if people wouldn't list geo-blocked streams.
Currently there are a quite a few and we're working on addressing this.


Best regards,

Thomas B. Ruecker



From phschafft at de.loewenfelsen.net  Wed Aug  8 11:54:18 2018
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Wed, 08 Aug 2018 11:54:18 +0000
Subject: [Icecast] Problems with metadata updates
In-Reply-To: <894C999F-4ADB-4062-B85F-4CBF469E1D01@caturria.ca>
References: <894C999F-4ADB-4062-B85F-4CBF469E1D01@caturria.ca>
Message-ID: <1533729258.1765.49.camel@de.loewenfelsen.net>

Good afternoon,

On Tue, 2018-07-31 at 10:36 -0400, Jordan Verner wrote:
> Hi,
> I am writing a source client (from scratch).

Mind to share a link with the community?


> I?ve got the actual audio streaming part worked out just fine, but the
> metadata has me scratching my head a little bit.

> According to the docs, to update metadata for an mp3 stream

Yes. And only for MP3 and AAC this holds true. Also note that MP3 and
AAC are not officially supported by Icecast. They may work, but that's
it. We recommend to use Opus for most applications.


> you?re supposed to issue an http request like this:
> http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test <http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test>

Yes.


> If I send this request authenticated with the source
> username/password, I get this, and the metadata is not updated:
> <iceresponse>
> <message>Mountpoint will not accept URL updates</message>
> <return>1</return>
> </iceresponse>
> If I issue the same request but authenticate it using the admin
> password, it works and shows the following:
> <iceresponse>
> <message>Metadata update successful</message>
> <return>1</return>
> </iceresponse>

The above message is returned if:
      * the internal handler for the format does not support the
        operation (again, this is only for MP3 and AAC as they do not
        support metadata themself); not the case here as it works with
        admin credentials.
      * You are sending the data from a different source IP than the
        source (the audio data connection) is connected from.

This check is there for reasons of security. Without it there is an
attack with one DJ hijacking the stream of another DJ of the same
station. This has been seen in the wild and is an inherent problem of
MP3 and AAC.


> Lastly, if I hit admin/metadata.xsl instead of admin/metadata, and
> authenticate with source credentials and the exact same query
> parameters, it updates successfully, but of course returns a full HTML
> admin page instead of just the simple xml response.

Yes. As now you're no longer the source client but an actual user.


> For now I?m having to hit the metadata.xsl page and then probe the
> resulting HTML for the words metadata update successful instead of
> being able to do it the intended way as per the example in the
> documentation.

Please don't. The HTML is NOT for parsing.


> Also, are there any other valid mode strings besides updinfo?

No.

Hope this reply was helpful.

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

From dave at dashs.denver.co.us  Wed Aug  8 14:23:42 2018
From: dave at dashs.denver.co.us (Dave Serls)
Date: Wed, 8 Aug 2018 08:23:42 -0600
Subject: [Icecast] YP registration for Authenticated streams
In-Reply-To: <5c90812a-1b9a-98ea-59ef-d5f0c7f7860c@ruecker.fi>
References: <20180807125510.59df414b@groucho.dashs.denver.co.us>
 <946A1356-1F5E-48C4-86FD-D22F8AF7140D@gmail.com>
 <20180807142121.1da1f4a4@groucho.dashs.denver.co.us>
 <5c90812a-1b9a-98ea-59ef-d5f0c7f7860c@ruecker.fi>
Message-ID: <20180808082342.0f30c026@groucho.dashs.denver.co.us>

On Wed, 8 Aug 2018 05:41:05 +0000
"Thomas B. R?cker" <thomas at ruecker.fi> wrote:

> Hi,
> 
> 
> On 08/07/2018 08:21 PM, Dave Serls wrote:
> > On Tue, 07 Aug 2018 21:20:07 +0200
> > "Marvin Scholz" <epirat07 at gmail.com> wrote:
> >  
> >> On 7 Aug 2018, at 20:55, Dave Serls wrote:
> >>  
> >>>  Is it possible to register ones icecast streams at dir.xiph.org if 
> >>> they require
> >>>  URL authentication?    
> >> Why would it be useful to have streams in the directory that users can 
> >> not listen
> >> to because they require auth?  
> >   Ah. Answering a question with a question.
> >   I do not know if dir.xiph.org is included as a standard for internet radio appliances.
> >   Or is included in searches made from other sites.
> >   I am only interested in servicing users who may also use my email server, who will
> >   provide IP addresses that have been white-listed here for URL auth.  
> 
> It is far easier for us to really help people if we understand their
> motivation.
> Personally I've seen probably 70% of user questions for projects that
> I'm involved in arrive at solutions that were different from the
> original technical question setting. So while answering a question with
> a question maybe doesn't feel very nice, I can understand why Marvin did
> so. My answer would probably have been "Not really, but could you explain?"
> In your case we'd probably suggest to address this possible use-case in
> a different way. If you'd be interested in actually solving your issue
> instead of an answer to one particular technical aspect that is.
> 
> 
> >   Now can you provide an answer to my question?  
> 
> No, we kindly ask you not to attempt to list streams that need
> authentication of any kind. The directory is intended for freely
> accessible streams.
> Also we would prefer if people wouldn't list geo-blocked streams.
> Currently there are a quite a few and we're working on addressing this.
> 
> 
> Best regards,
> 
> Thomas B. Ruecker
> 

  Thanks for your reply.  I wasn't attempting to be confrontational, only
  conversational.  The folks at Icecast have always been helpful and civil.
  As a matter of fact, Marvin helped me to implement URL auth on #icecast,
  if his handle is "ePirat".  So thanks, Herr Scholz.
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


-- 
************************************************************************
*   Dave Serls                                 Littleton, CO, USA      *
*   dashs.denver.co.us                         http://www.dashs.com    *
************************************************************************


From jordan at caturria.ca  Wed Aug  8 15:42:32 2018
From: jordan at caturria.ca (Jordan Verner)
Date: Wed, 8 Aug 2018 11:42:32 -0400
Subject: [Icecast] Problems with metadata updates
In-Reply-To: <1533729258.1765.49.camel@de.loewenfelsen.net>
References: <894C999F-4ADB-4062-B85F-4CBF469E1D01@caturria.ca>
 <1533729258.1765.49.camel@de.loewenfelsen.net>
Message-ID: <534681C6-607B-4BF0-95EF-A7BB37F40683@caturria.ca>

Hi Philip,
Thanks for your response.
Yes, I more or less had it figured out. I figured the cannot accept url updates message was a security measure I was tripping.
As of yet, there is no link to share. I want to shoot for a 2019 release to Github though.
It?s a scriptable streaming system similar in a way to Liquidsoap, but with an emphasis on being able to be used as a precise station scheduler (so it has functionality like database, date and time manipulation etc built in).
There is also a configuration file based station manager which is written in script and built on top of it.
It?s coming along swimmingly, but with college starting back up in September I?d say a few more months to polish it up to the point at which I?d be comfortable releasing are in order.
I do look forward to public reception though, whenever that day arrives. A couple more outstanding bugs and a couple missing features stand in the way atm.

Kind regards,

Jordan.


> On Aug 8, 2018, at 7:54 AM, Philipp Schafft <phschafft at de.loewenfelsen.net> wrote:
> 
> Good afternoon,
> 
> On Tue, 2018-07-31 at 10:36 -0400, Jordan Verner wrote:
>> Hi,
>> I am writing a source client (from scratch).
> 
> Mind to share a link with the community?
> 
> 
>> I?ve got the actual audio streaming part worked out just fine, but the
>> metadata has me scratching my head a little bit.
> 
>> According to the docs, to update metadata for an mp3 stream
> 
> Yes. And only for MP3 and AAC this holds true. Also note that MP3 and
> AAC are not officially supported by Icecast. They may work, but that's
> it. We recommend to use Opus for most applications.
> 
> 
>> you?re supposed to issue an http request like this:
>> http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test <http://hostname:port/admin/metadata?mode=updinfo&mount=/station&song=test>
> 
> Yes.
> 
> 
>> If I send this request authenticated with the source
>> username/password, I get this, and the metadata is not updated:
>> <iceresponse>
>> <message>Mountpoint will not accept URL updates</message>
>> <return>1</return>
>> </iceresponse>
>> If I issue the same request but authenticate it using the admin
>> password, it works and shows the following:
>> <iceresponse>
>> <message>Metadata update successful</message>
>> <return>1</return>
>> </iceresponse>
> 
> The above message is returned if:
>      * the internal handler for the format does not support the
>        operation (again, this is only for MP3 and AAC as they do not
>        support metadata themself); not the case here as it works with
>        admin credentials.
>      * You are sending the data from a different source IP than the
>        source (the audio data connection) is connected from.
> 
> This check is there for reasons of security. Without it there is an
> attack with one DJ hijacking the stream of another DJ of the same
> station. This has been seen in the wild and is an inherent problem of
> MP3 and AAC.
> 
> 
>> Lastly, if I hit admin/metadata.xsl instead of admin/metadata, and
>> authenticate with source credentials and the exact same query
>> parameters, it updates successfully, but of course returns a full HTML
>> admin page instead of just the simple xml response.
> 
> Yes. As now you're no longer the source client but an actual user.
> 
> 
>> For now I?m having to hit the metadata.xsl page and then probe the
>> resulting HTML for the words metadata update successful instead of
>> being able to do it the intended way as per the example in the
>> documentation.
> 
> Please don't. The HTML is NOT for parsing.
> 
> 
>> Also, are there any other valid mode strings besides updinfo?
> 
> No.
> 
> Hope this reply was helpful.
> 
> 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
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast



From subscription at nextdial.com.br  Sun Aug 12 02:04:12 2018
From: subscription at nextdial.com.br (subscription at nextdial.com.br)
Date: Sat, 11 Aug 2018 23:04:12 -0300
Subject: [Icecast] Help to enable SSL
In-Reply-To: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
Message-ID: <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>

Hello,
  
 At a test VPS running Ubuntu 16.04 LTS I did this:
  	sudo apt-get update 	sudo add-apt-repository ppa:certbot/certbot 	sudo 
apt-get install certbot 	sudo apt-get install icecast2 	sudo certbot 
certonly --standalone -d domain.com 	cat cert.pem privkey.pem | sudo tee 
/etc/icecast2/icecast.pem 	sudo vi /etc/icecast2/icecast.xml 
	<listen-socket>
	    <port>8443</port>
	    <ssl>1</ssl>
	</listen-socket>
	<ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate> 	sudo chown 
icecast2:icecast /etc/icecast2/icecast.pem 	sudo /etc/init.d/icecast2 
restart 
  
 After that, I have this at the log:
  
 [2018-08-12  01:47:07] INFO stats/_stats_thread stats thread started
[2018-08-12  01:47:07] INFO main/main Icecast 2.4.2 server started
[2018-08-12  01:47:07] INFO connection/get_ssl_certificate No SSL 
capability
[2018-08-12  01:47:07] INFO yp/yp_update_thread YP update thread started
  
  
 I tried restart the VPS and a lot of things (change the order of the pem 
creation, etc), all with no success.
  
 What I am doing wrong?
  
  
 Best,
 Thiago

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

From thomas at ruecker.fi  Sun Aug 12 06:55:00 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Sun, 12 Aug 2018 06:55:00 +0000
Subject: [Icecast] Help to enable SSL
In-Reply-To: <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
 <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
Message-ID: <30871e4d-d694-719d-d2a2-ea65769b8ad7@ruecker.fi>

Hi,


On 08/12/2018 02:04 AM, subscription at nextdial.com.br wrote:
> Hello,
> ?
> At a test VPS running Ubuntu 16.04 LTS I did this:
>
>  1. sudo apt-get update
>  2. sudo add-apt-repository ppa:certbot/certbot
>  3. sudo apt-get install certbot
>

You'll need an additional step at this point, see below.


>  1. sudo apt-get install icecast2
>  2. sudo certbot certonly --standalone -d domain.com
>  3. cat cert.pem privkey.pem | sudo tee /etc/icecast2/icecast.pem
>  4. sudo vi /etc/icecast2/icecast.xml
>  5. <listen-socket>
>     ??? <port>8443</port>
>     ??? <ssl>1</ssl>
>     </listen-socket>
>     <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate>
>  6. sudo chown icecast2:icecast /etc/icecast2/icecast.pem
>  7. sudo /etc/init.d/icecast2 restart
>
> ?
> After that, I have this at the log:
> ?
> [2018-08-12? 01:47:07] INFO stats/_stats_thread stats thread started
> [2018-08-12? 01:47:07] INFO main/main Icecast 2.4.2 server started
> [2018-08-12? 01:47:07] INFO connection/get_ssl_certificate No SSL
> capability
> [2018-08-12? 01:47:07] INFO yp/yp_update_thread YP update thread started
> ?

This is because Debian (and Ubuntu, as they recycle the same packaging)
refuse to compile Icecast (and other software) with openSSL support for
political reasons.


> What I am doing wrong
>

You didn't do anything wrong as such. You just didn't know that there
are additional steps if you need TLS support.
The official Xiph.org packages are built with openSSL support:
https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories)

$ curl
https://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/Release.key
>/tmp/multimedia-obs.key
$ gpg /tmp/multimedia-obs.key

It should yield:
pub rsa2048 2017-11-21 [SC] [expires: 2020-01-30]
0E313DB7936B4E76E720065B77EC2301F23C6AA3
uid multimedia OBS Project

$ sudo apt-key add /tmp/multimedia-obs.key
$ sudo sh -c "echo deb
http://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/
./ >>/etc/apt/sources.list.d/icecast.list"
$ sudo apt-get update
$ sudo apt-get install icecast2

Make sure it downloads the package from an OBS address and not from an
ubuntu.com or mirror. (Newer versions like 18.04 require an explicit
version or other tricks at the moment: sudo apt-get install
icecast2/2.4.2-2 )

At this point your server should already be running the Xiph.org build
of Icecast and port 8443 should answer to HTTPS.

If you would prefer to listen to the standard port of 443, please follow
these additional directions:
http://lists.xiph.org/pipermail/icecast/2015-February/013198.html
Under no circumstances you should try to reverse proxy Icecast 2.4.x -
while one can make it mostly work, it is far from trivial to set things
up in a way that will avoid most of the corner cases. Most famously,
taking down your webserver.

Cheers,

Thomas



From thomas at ruecker.fi  Sun Aug 12 07:09:37 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Sun, 12 Aug 2018 07:09:37 +0000
Subject: [Icecast] Help to enable SSL
In-Reply-To: <30871e4d-d694-719d-d2a2-ea65769b8ad7@ruecker.fi>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
 <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
 <30871e4d-d694-719d-d2a2-ea65769b8ad7@ruecker.fi>
Message-ID: <cb36b5eb-6b3b-beab-79e2-e4f88463d563@ruecker.fi>


On 08/12/2018 06:55 AM, Thomas B. R?cker wrote:
>
>> What I am doing wrong
>>
> You didn't do anything wrong as such. You just didn't know that there
> are additional steps if you need TLS support.
> The official Xiph.org packages are built with openSSL support:
> https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories)

This one got munged:

> $ curl
> https://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/Release.key
>> /tmp/multimedia-obs.key

That should be:

curl
https://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/Release.key
\
-o /tmp/multimedia-obs.key


TBR



From subscription at nextdial.com.br  Mon Aug 13 11:54:43 2018
From: subscription at nextdial.com.br (subscription at nextdial.com.br)
Date: Mon, 13 Aug 2018 08:54:43 -0300
Subject: [Icecast] Icecast Digest, Vol 170, Issue 8
In-Reply-To: <mailman.1.1534075202.18116.icecast@xiph.org>
References: <mailman.1.1534075202.18116.icecast@xiph.org>
Message-ID: <7fec3ac135054f60b5204ffb92d5ad24@nextdial.com.br>

Thanks for the help Thomas.
  
 It worked.
  
  
 Best,
 Thiago
  
  
  

----------------------------------------
 De: icecast-request at xiph.org
Enviado: domingo, 12 de agosto de 2018 09:00
Para: icecast at xiph.org
Assunto: Icecast Digest, Vol 170, Issue 8   
Send Icecast mailing list submissions to icecast at xiph.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.xiph.org/mailman/listinfo/icecast or, via email, send a message with subject or body 'help' to icecast-request at xiph.org You can reach the person managing the list at icecast-owner at xiph.org When replying, please edit your Subject line so it is more specific than "Re: Contents of Icecast digest..." Today's Topics: 1. Help to enable SSL (subscription at nextdial.com.br) 2. Re: Help to enable SSL (Thomas B. R?cker) 3. Re: Help to enable SSL (Thomas B. R?cker) ---------------------------------------------------------------------- Message: 1 Date: Sat, 11 Aug 2018 23:04:12 -0300 From: "subscription at nextdial.com.br" <subscription at nextdial.com.br> To: <icecast at xiph.org> Subject: [Icecast] Help to enable SSL Message-ID: <7bbe79b1db49481eb462ca4d0ce66e13 at nextdial.com.br> Content-Type: text/plain; charset="utf-8" Hello, At a test VPS running Ubuntu 16.04 LTS I did this: sudo apt-get update sudo add-apt-repository ppa:certbot/certbot sudo apt-get install certbot sudo apt-get install icecast2 sudo certbot certonly --standalone -d domain.com cat cert.pem privkey.pem | sudo tee /etc/icecast2/icecast.pem sudo vi /etc/icecast2/icecast.xml <listen-socket> <port>8443</port> <ssl>1</ssl> </listen-socket> <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate> sudo chown icecast2:icecast /etc/icecast2/icecast.pem sudo /etc/init.d/icecast2 restart After that, I have this at the log: [2018-08-12 01:47:07] INFO stats/_stats_thread stats thread started [2018-08-12 01:47:07] INFO main/main Icecast 2.4.2 server started [2018-08-12 01:47:07] INFO connection/get_ssl_certificate No SSL capability [2018-08-12 01:47:07] INFO yp/yp_update_thread YP update thread started I tried restart the VPS and a lot of things (change the order of the pem creation, etc), all with no success. What I am doing wrong? Best, Thiago -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180811/680c713f/attachment-0001.html> ------------------------------ Message: 2 Date: Sun, 12 Aug 2018 06:55:00 +0000 From: Thomas B. R?cker <thomas at ruecker.fi> To: icecast at xiph.org Subject: Re: [Icecast] Help to enable SSL Message-ID: <30871e4d-d694-719d-d2a2-ea65769b8ad7 at ruecker.fi> Content-Type: text/plain; charset=windows-1252 Hi, On 08/12/2018 02:04 AM, subscription at nextdial.com.br wrote: > Hello, >   > At a test VPS running Ubuntu 16.04 LTS I did this: > > 1. sudo apt-get update > 2. sudo add-apt-repository ppa:certbot/certbot > 3. sudo apt-get install certbot > You'll need an additional step at this point, see below. > 1. sudo apt-get install icecast2 > 2. sudo certbot certonly --standalone -d domain.com > 3. cat cert.pem privkey.pem | sudo tee /etc/icecast2/icecast.pem > 4. sudo vi /etc/icecast2/icecast.xml > 5. <listen-socket> >     <port>8443</port> >     <ssl>1</ssl> > </listen-socket> > <ssl-certificate>/etc/icecast2/icecast.pem</ssl-certificate> > 6. sudo chown icecast2:icecast /etc/icecast2/icecast.pem > 7. sudo /etc/init.d/icecast2 restart > >   > After that, I have this at the log: >   > [2018-08-12  01:47:07] INFO stats/_stats_thread stats thread started > [2018-08-12  01:47:07] INFO main/main Icecast 2.4.2 server started > [2018-08-12  01:47:07] INFO connection/get_ssl_certificate No SSL > capability > [2018-08-12  01:47:07] INFO yp/yp_update_thread YP update thread started >   This is because Debian (and Ubuntu, as they recycle the same packaging) refuse to compile Icecast (and other software) with openSSL support for political reasons. > What I am doing wrong > You didn't do anything wrong as such. You just didn't know that there are additional steps if you need TLS support. The official Xiph.org packages are built with openSSL support: https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories) $ curl https://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/Release.key >/tmp/multimedia-obs.key $ gpg /tmp/multimedia-obs.key It should yield: pub rsa2048 2017-11-21 [SC] [expires: 2020-01-30] 0E313DB7936B4E76E720065B77EC2301F23C6AA3 uid multimedia OBS Project $ sudo apt-key add /tmp/multimedia-obs.key $ sudo sh -c "echo deb http://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/ ./ >>/etc/apt/sources.list.d/icecast.list" $ sudo apt-get update $ sudo apt-get install icecast2 Make sure it downloads the package from an OBS address and not from an ubuntu.com or mirror. (Newer versions like 18.04 require an explicit version or other tricks at the moment: sudo apt-get install icecast2/2.4.2-2 ) At this point your server should already be running the Xiph.org build of Icecast and port 8443 should answer to HTTPS. If you would prefer to listen to the standard port of 443, please follow these additional directions: http://lists.xiph.org/pipermail/icecast/2015-February/013198.html Under no circumstances you should try to reverse proxy Icecast 2.4.x - while one can make it mostly work, it is far from trivial to set things up in a way that will avoid most of the corner cases. Most famously, taking down your webserver. Cheers, Thomas ------------------------------ Message: 3 Date: Sun, 12 Aug 2018 07:09:37 +0000 From: Thomas B. R?cker <thomas at ruecker.fi> To: icecast at xiph.org Subject: Re: [Icecast] Help to enable SSL Message-ID: <cb36b5eb-6b3b-beab-79e2-e4f88463d563 at ruecker.fi> Content-Type: text/plain; charset=utf-8 On 08/12/2018 06:55 AM, Thomas B. R?cker wrote: > >> What I am doing wrong >> > You didn't do anything wrong as such. You just didn't know that there > are additional steps if you need TLS support. > The official Xiph.org packages are built with openSSL support: > https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories) This one got munged: > $ curl > https://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/Release.key >> /tmp/multimedia-obs.key That should be: curl https://download.opensuse.org/repositories/multimedia:/xiph/xUbuntu_16.04/Release.key \ -o /tmp/multimedia-obs.key TBR ------------------------------ Subject: Digest Footer _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast ------------------------------ End of Icecast Digest, Vol 170, Issue 8 ***************************************

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

From mvandop at xs4all.nl  Wed Aug 15 09:15:08 2018
From: mvandop at xs4all.nl (Michel van Dop)
Date: Wed, 15 Aug 2018 11:15:08 +0200
Subject: [Icecast] IPv6 full support  (future wish)
Message-ID: <8f0e188724cba987e55418d312593b1d@xs4all.nl>

Hi,

Thanks for the beautiful product,  i use it for a long time. Very
stable! 

I would like in a new version that IPv6 fully works like IPv4
<bind-address>. 

Now we can only use :: With multiple interfaces the use it all on that
port, this is difficult for multi icecast account on same server.

Best regards,
Michel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180815/90501bcc/attachment.htm>

From phschafft at de.loewenfelsen.net  Wed Aug 15 10:40:14 2018
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Wed, 15 Aug 2018 10:40:14 +0000
Subject: [Icecast] IPv6 full support  (future wish)
In-Reply-To: <8f0e188724cba987e55418d312593b1d@xs4all.nl>
References: <8f0e188724cba987e55418d312593b1d@xs4all.nl>
Message-ID: <1534329614.5822.18.camel@de.loewenfelsen.net>

Good morning,

On Wed, 2018-08-15 at 11:15 +0200, Michel van Dop wrote:
> Hi,
> 
> Thanks for the beautiful product,  i use it for a long time. Very
> stable! 
> 
> I would like in a new version that IPv6 fully works like IPv4
> <bind-address>. 
> 
> Now we can only use :: With multiple interfaces the use it all on that
> port, this is difficult for multi icecast account on same server.

I'm not exactly sure what your problem is. Icecast supports binding to
several addresses individually. E.g. this works for me:
    <listen-socket>
        <bind-address>::1</bind-address>
    </listen-socket>
    <listen-socket>
        <bind-address>2a01:*:*:*:*:*:6453:40a1</bind-address>
    </listen-socket>

Resulting in:
        Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
        tcp6       0      0 ::1:8000                :::*                    LISTEN      12043/icecast   
        tcp6       0      0 2a01:*:*:*:*:8000       :::*                    LISTEN      12043/icecast   
        

Maybe you can give us a little bit more context.

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

From mvandop at xs4all.nl  Thu Aug 16 09:40:40 2018
From: mvandop at xs4all.nl (Michel van Dop)
Date: Thu, 16 Aug 2018 11:40:40 +0200
Subject: [Icecast] IPv6 full support  (future wish)
In-Reply-To: <1534329614.5822.18.camel@de.loewenfelsen.net>
References: <8f0e188724cba987e55418d312593b1d@xs4all.nl>
 <1534329614.5822.18.camel@de.loewenfelsen.net>
Message-ID: <2f4abc9fee13f2200692bfe3fe3d52ec@xs4all.nl>

Hi Philipp, 

Thank you for the information. sorry for the unclear question.
I do not know that we can use a full IPv6 address in bind-address item.
I can not find it in the documents. Can we use it on all 2.4 versions?

Best regards,
Michel

Philipp Schafft schreef op 2018-08-15 12:40:

> Good morning,
> 
> On Wed, 2018-08-15 at 11:15 +0200, Michel van Dop wrote: 
> 
>> Hi,
>> 
>> Thanks for the beautiful product,  i use it for a long time. Very
>> stable! 
>> 
>> I would like in a new version that IPv6 fully works like IPv4
>> <bind-address>. 
>> 
>> Now we can only use :: With multiple interfaces the use it all on that
>> port, this is difficult for multi icecast account on same server.
> 
> I'm not exactly sure what your problem is. Icecast supports binding to
> several addresses individually. E.g. this works for me:
> <listen-socket>
> <bind-address>::1</bind-address>
> </listen-socket>
> <listen-socket>
> <bind-address>2a01:*:*:*:*:*:6453:40a1</bind-address>
> </listen-socket>
> 
> Resulting in:
> Proto Recv-Q Send-Q Local Address           Foreign Address         State       PID/Program name
> tcp6       0      0 ::1:8000                :::*                    LISTEN      12043/icecast   
> tcp6       0      0 2a01:*:*:*:*:8000       :::*                    LISTEN      12043/icecast   
> 
> Maybe you can give us a little bit more context.
> 
> With best regards, 
> _______________________________________________
> 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/20180816/0c45b45f/attachment.htm>

From thomas at ruecker.fi  Fri Aug 17 05:42:20 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Fri, 17 Aug 2018 05:42:20 +0000
Subject: [Icecast] IPv6 full support (future wish)
In-Reply-To: <2f4abc9fee13f2200692bfe3fe3d52ec@xs4all.nl>
References: <8f0e188724cba987e55418d312593b1d@xs4all.nl>
 <1534329614.5822.18.camel@de.loewenfelsen.net>
 <2f4abc9fee13f2200692bfe3fe3d52ec@xs4all.nl>
Message-ID: <8d80e83f-36a5-f9dc-bfd7-e0e17d2e329c@ruecker.fi>

Hi,


On 08/16/2018 09:40 AM, Michel van Dop wrote:
> Thank you for the information.?sorry for the unclear question.
>
> I do not know that we can use a full IPv6 address in bind-address item.
> I can not find it in the documents. Can we use it on all 2.4 versions?
>

I don't think we have changed things since 2.3.2:
https://icecast.org/news/icecast-release-2_3_2/


So yes, things are fine on our 2.4.0, 2.4.1, 2.4.2 and 2.4.3 releases.
Though for reasons of security and stability I'd strongly advise against
the former two.
2.4.2 and 2.4.3 are equivalent on Linux/Unix and available through all
mainstream distributions. In case of Debian use backports. If you need
TLS on Debian/Ubuntu, use our official packages:
https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories)

Br,
TBR

>
>
> Philipp Schafft schreef op 2018-08-15 12:40:
>
>> Good morning,
>>
>> On Wed, 2018-08-15 at 11:15 +0200, Michel van Dop wrote:
>>> Hi,
>>>
>>> Thanks for the beautiful product, ?i use it for a long time. Very
>>> stable!
>>>
>>> I would like in a new version that IPv6 fully works like IPv4
>>> <bind-address>.
>>>
>>> Now we can only use :: With multiple interfaces the use it all on that
>>> port, this is difficult for multi icecast account on same server.
>>
>> I'm not exactly sure what your problem is. Icecast supports binding to
>> several addresses individually. E.g. this works for me:
>> ????<listen-socket>
>> ????????<bind-address>::1</bind-address>
>> ????</listen-socket>
>> ????<listen-socket>
>> ????????<bind-address>2a01:*:*:*:*:*:6453:40a1</bind-address>
>> ????</listen-socket>
>>
>> Resulting in:
>> ????????Proto Recv-Q Send-Q Local Address ??????????Foreign Address
>> ????????State ??????PID/Program name
>> ????????tcp6 ??????0 ?????0 ::1:8000 ???????????????:::*
>> ???????????????????LISTEN ?????12043/icecast ??
>> ????????tcp6 ??????0 ?????0 2a01:*:*:*:*:8000 ??????:::*
>> ???????????????????LISTEN ?????12043/icecast ??
>> ????????
>>
>> Maybe you can give us a little bit more context.
>>
>> With best regards,
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org <mailto: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 seva.movie.store at gmail.com  Wed Aug 15 12:29:56 2018
From: seva.movie.store at gmail.com (Sebastian Pereiro)
Date: Wed, 15 Aug 2018 15:29:56 +0300
Subject: [Icecast] WARN cfgfile/_parse_alias incomplete alias definition
	HELP PLEASE.
Message-ID: <CABM3T0uCXz=okJv2K-m7e=S4UEOo104Lh=T-cv_2NeCqpYusKw@mail.gmail.com>

Hello
Maybe you can help me i couldnt find answer in web , sorry for english).
I install Icecast 2.4.0-kh10 with all needed packages .
Ubuntu-16.04-amd64.
No errors .

~# icecast -status
Icecast 2.4.0-kh10

When I start icecast
icecast -b -c /usr/local/etc/icecast.xml
i have problems like:
[2018-08-15  03:42:02] WARN cfgfile/_parse_alias incomplete alias definition
[2018-08-15  03:42:02] EROR main/fatal_error FATAL: error parsing config
file (/usr/local/etc/icecast.xml)
[2018-08-15  03:42:02] EROR main/fatal_error XML config parsing error

Ill try to fix and reinstall
apt-get install libxml2
apt-get install libxml-libxml-perl

apt-get install libxml2-dev

apt-get install libxml1-dev

What u think?
Best regards Vsevolod.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180815/f6afdf23/attachment.htm>

From thomas at ruecker.fi  Sun Aug 19 13:44:35 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Sun, 19 Aug 2018 13:44:35 +0000
Subject: [Icecast] WARN cfgfile/_parse_alias incomplete alias definition
 HELP PLEASE.
In-Reply-To: <CABM3T0uCXz=okJv2K-m7e=S4UEOo104Lh=T-cv_2NeCqpYusKw@mail.gmail.com>
References: <CABM3T0uCXz=okJv2K-m7e=S4UEOo104Lh=T-cv_2NeCqpYusKw@mail.gmail.com>
Message-ID: <12fb051f-a1f6-95b4-7e76-7ce58002ffd6@ruecker.fi>

Hi,


On 08/15/2018 12:29 PM, Sebastian Pereiro wrote:
> Hello?
> Maybe you can help me i couldnt find answer in web , sorry for english).
> I install?Icecast 2.4.0-kh10 with all needed packages .
>

Sorry, we can't help you with the "-kh" software as Xiph.org is the home
of the official Icecast, not the "-kh" variety.
There are substantial differences between Karl's fork and our official
software.

We we suggest to install official Icecast from our repositories or use
the Ubuntu "icecast2" package.
https://wiki.xiph.org/Icecast_Server/Installing_latest_version_(official_Xiph_repositories)
Please note that both come with init/systemd integration and should thus
be started e.g. using "systemctl start icecast2".


Best regards,

Thomas Ruecker
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180819/7e96c8af/attachment.htm>

From ak18 at 5x9.de  Sun Aug 19 13:49:43 2018
From: ak18 at 5x9.de (ak18 at 5x9.de)
Date: Sun, 19 Aug 2018 15:49:43 +0200
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <20180807125200.GC19453@nowster.org.uk>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
 <20180805194022.GA2520@thinkpad.nowster.org.uk>
 <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>
 <20180807125200.GC19453@nowster.org.uk>
Message-ID: <3b392bd2-a17b-6e23-3be1-c3354146859d@5x9.de>

Am 07.08.2018 um 14:52 schrieb Paul Martin:

> Are you using the standard icecast2 or the kh (Karl Heyes) version?
What is the difference between these version? I think kh is the 
developer and this version is newer (or better?) There can I get this 
kh-version?



From lion at lion.leolix.org  Sun Aug 19 14:09:07 2018
From: lion at lion.leolix.org (Philipp Schafft)
Date: Sun, 19 Aug 2018 14:09:07 +0000
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <3b392bd2-a17b-6e23-3be1-c3354146859d@5x9.de>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
 <20180805194022.GA2520@thinkpad.nowster.org.uk>
 <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>
 <20180807125200.GC19453@nowster.org.uk>
 <3b392bd2-a17b-6e23-3be1-c3354146859d@5x9.de>
Message-ID: <1534687747.5822.156.camel@lion.leolix.org>

Good afternoon,

On Sun, 2018-08-19 at 15:49 +0200, ak18 at 5x9.de wrote:
> Am 07.08.2018 um 14:52 schrieb Paul Martin:
> 
> > Are you using the standard icecast2 or the kh (Karl Heyes) version?
> What is the difference between these version? I think kh is the 
> developer and this version is newer (or better?) There can I get this 
> kh-version?

"-kh" is a fork by a different vendor (Karl Heyes) who never renamed his
product.

The development version of official Icecast is 2.5.x.

With best regards,

-- 
Philipp.
 (Rah of PH2)


From ak18 at 5x9.de  Mon Aug 20 13:50:36 2018
From: ak18 at 5x9.de (ak18 at 5x9.de)
Date: Mon, 20 Aug 2018 15:50:36 +0200
Subject: [Icecast] Mount with Relay: Fallback-override does not work
In-Reply-To: <1534687747.5822.156.camel@lion.leolix.org>
References: <63331aff-6bbd-791e-94dd-845e1426730b@5x9.de>
 <20180805194022.GA2520@thinkpad.nowster.org.uk>
 <3f80b1e1-6271-93d1-54c8-da4207a2b068@5x9.de>
 <20180807125200.GC19453@nowster.org.uk>
 <3b392bd2-a17b-6e23-3be1-c3354146859d@5x9.de>
 <1534687747.5822.156.camel@lion.leolix.org>
Message-ID: <83b44125-715b-55bb-b6cb-a8be85b48f0c@5x9.de>

Am 19.08.2018 um 16:09 schrieb Philipp Schafft:
> "-kh" is a fork by a different vendor (Karl Heyes) who never renamed his
> product.
>
> The development version of official Icecast is 2.5.x.
>
Where can I download this kh-version? Has Karl Heyes an homepage?


From subscription at nextdial.com.br  Fri Aug 24 23:51:30 2018
From: subscription at nextdial.com.br (subscription at nextdial.com.br)
Date: Fri, 24 Aug 2018 20:51:30 -0300
Subject: [Icecast] Client auth failed with ""
In-Reply-To: <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
 <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
Message-ID: <a2e1daeac4e54703877c2fe12542f44c@nextdial.com.br>

 Hello,
 We are using url authentication and getting the item bellow at the log:
  
 [2018-08-24  23:26:05] INFO auth_url/url_add_listener client auth 
(http://127.0.0.1:8001/listener/add) failed with ""
  
 I put try/catch and reviewed all my code ensure always return a proper 
status and header error code, so what trigger this kind of error?

  
  
 Regards,
 Thiago
  

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

From thomas at ruecker.fi  Sat Aug 25 09:50:20 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Sat, 25 Aug 2018 09:50:20 +0000
Subject: [Icecast] Client auth failed with ""
In-Reply-To: <a2e1daeac4e54703877c2fe12542f44c@nextdial.com.br>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
 <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
 <a2e1daeac4e54703877c2fe12542f44c@nextdial.com.br>
Message-ID: <985c647c-da4a-cdb2-abe7-8d27f9c75c63@ruecker.fi>




On 08/24/2018 11:51 PM, subscription at nextdial.com.br wrote:
> Hello,
> We are using url authentication and getting the item bellow at the log:
> ?
> [2018-08-24? 23:26:05] INFO auth_url/url_add_listener client auth
> (http://127.0.0.1:8001/listener/add) failed with ""
> ?
> I put try/catch and reviewed all my code ensure always return a proper
> status and header error code, so what trigger this kind of error?

Have you checked if there are corresponding log entries on the server
that Icecast was trying to access at 2018-08-24T23:26:05?
Could it be that your authentication backend was e.g. overloaded and
failed to answer the request?

Cheers,

Thomas





From chernabog at titanx.games  Tue Aug 28 17:28:32 2018
From: chernabog at titanx.games (Chernabog)
Date: Tue, 28 Aug 2018 13:28:32 -0400
Subject: [Icecast] =?utf-8?q?IceCast_-_Is_it_still_being_developed=3F?=
Message-ID: <b6f1968d7d4a391b088a8118308e2dd2@titanx.games>

 

Hello! I was just wondering if the IceCast platform was still being
actively developed? 

Thank you, 

Jason 
-- 

_DEFINE YOUR DESTINY IN ULTIMA GENESIS: CALL OF THE AVATAR [1]! PLAY FOR
FREE TODAY._ 

?FOLLOW US ON SOCIAL MEDIA!

 [2] [3] 

Links:
------
[1] https://titanx.games
[2] https://www.facebook.com/titanxgames/
[3] https://twitter.com/intent/user?screen_name=_TitanXGames
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180828/af3a8b4b/attachment.htm>

From jake at jakebriggs.com  Tue Aug 28 21:05:19 2018
From: jake at jakebriggs.com (jake)
Date: Wed, 29 Aug 2018 09:05:19 +1200
Subject: [Icecast] IceCast - Is it still being developed?
In-Reply-To: <b6f1968d7d4a391b088a8118308e2dd2@titanx.games>
References: <b6f1968d7d4a391b088a8118308e2dd2@titanx.games>
Message-ID: <438139f928d057e73d764b761c4b2e21@jakebriggs.com>

 

https://gitlab.xiph.org/xiph/icecast-server/commits/master 

The last commit was a week ago, and it looks fairly active, so.... yes? 

On 2018-08-29 05:28, Chernabog wrote: 

> Hello! I was just wondering if the IceCast platform was still being actively developed? 
> 
> Thank you, 
> 
> Jason 
> -- 
> _DEFINE YOUR DESTINY IN ULTIMA GENESIS: CALL OF THE AVATAR [1]! PLAY FOR FREE TODAY._ 
> 
> FOLLOW US ON SOCIAL MEDIA!
> 
> [2] [3] 
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
 

Links:
------
[1] https://titanx.games
[2] https://www.facebook.com/titanxgames/
[3] https://twitter.com/intent/user?screen_name=_TitanXGames
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/494d022d/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blocked.gif
Type: image/gif
Size: 118 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/494d022d/attachment.gif>

From ak18 at 5x9.de  Wed Aug 29 05:23:20 2018
From: ak18 at 5x9.de (ak18 at 5x9.de)
Date: Wed, 29 Aug 2018 07:23:20 +0200
Subject: [Icecast] IceCast - Is it still being developed?
In-Reply-To: <438139f928d057e73d764b761c4b2e21@jakebriggs.com>
References: <b6f1968d7d4a391b088a8118308e2dd2@titanx.games>
 <438139f928d057e73d764b761c4b2e21@jakebriggs.com>
Message-ID: <2b8f7cdb-22f9-8ef8-cb3c-adafcc7f74c6@5x9.de>

Is this the version of "Karl Heyes" with extra features? If not, there 
can I find the "Karl Heyes"-version?


Am 28.08.2018 um 23:05 schrieb jake:
>
> https://gitlab.xiph.org/xiph/icecast-server/commits/master
>
> The last commit was a week ago, and it looks fairly active, so.... yes?
>
> On 2018-08-29 05:28, Chernabog wrote:
>
>> Hello! I was just wondering if the IceCast platform was still being 
>> actively developed?
>>
>> Thank you,
>>
>> Jason
>>
>> -- 
>>
>> /*Define your destiny in Ultima Genesis: Call of the Avatar 
>> <https://titanx.games>! Play forfree today.*/
>>
>> *?Follow us on social media!*
>>
>> <https://www.facebook.com/titanxgames/><https://twitter.com/intent/user?screen_name=_TitanXGames>
>>
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org <mailto: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/20180829/a47209f8/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blocked.gif
Type: image/gif
Size: 118 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/a47209f8/attachment.gif>

From ross at stationplaylist.com  Wed Aug 29 05:48:36 2018
From: ross at stationplaylist.com (Ross Levis)
Date: Wed, 29 Aug 2018 17:48:36 +1200
Subject: [Icecast] IceCast - Is it still being developed?
In-Reply-To: <2b8f7cdb-22f9-8ef8-cb3c-adafcc7f74c6@5x9.de>
References: <b6f1968d7d4a391b088a8118308e2dd2@titanx.games>
 <438139f928d057e73d764b761c4b2e21@jakebriggs.com>
 <2b8f7cdb-22f9-8ef8-cb3c-adafcc7f74c6@5x9.de>
Message-ID: <001501d43f5b$ef5f6fd0$ce1e4f70$@com>

A simple internet search.

https://karlheyes.github.io/

 

From: Icecast [mailto:icecast-bounces at xiph.org] On Behalf Of ak18 at 5x9.de
Sent: Wednesday, 29 August 2018 5:23 p.m.
To: icecast at xiph.org
Subject: Re: [Icecast] IceCast - Is it still being developed?

 

Is this the version of "Karl Heyes" with extra features? If not, there can I find the "Karl Heyes"-version?

 

Am 28.08.2018 um 23:05 schrieb jake:

 

 

https://gitlab.xiph.org/xiph/icecast-server/commits/master

 

The last commit was a week ago, and it looks fairly active, so.... yes?

 

On 2018-08-29 05:28, Chernabog wrote:

Hello! I was just wondering if the IceCast platform was still being actively developed?

 

Thank you,

 

Jason

-- 

Define your destiny in Ultima Genesis: Call of the Avatar <https://titanx.games> ! Play for free today.

 Follow us on social media!

 <https://www.facebook.com/titanxgames/>  <https://twitter.com/intent/user?screen_name=_TitanXGames> 

 

_______________________________________________
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/20180829/208324e0/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.gif
Type: image/gif
Size: 118 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/208324e0/attachment.gif>

From thomas at ruecker.fi  Wed Aug 29 05:52:04 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Wed, 29 Aug 2018 05:52:04 +0000
Subject: [Icecast] IceCast - Is it still being developed?
In-Reply-To: <2b8f7cdb-22f9-8ef8-cb3c-adafcc7f74c6@5x9.de>
References: <b6f1968d7d4a391b088a8118308e2dd2@titanx.games>
 <438139f928d057e73d764b761c4b2e21@jakebriggs.com>
 <2b8f7cdb-22f9-8ef8-cb3c-adafcc7f74c6@5x9.de>
Message-ID: <bf0fc162-01e0-3a99-4b48-b3d1d173a6f3@ruecker.fi>

Hi,


On 08/29/2018 05:23 AM, ak18 at 5x9.de wrote:
>
> Is this the version of "Karl Heyes" with extra features? If not, there
> can I find the "Karl Heyes"-version?
>

No it is not.
This is the official Icecast with many many new features that will
become the 2.5 release, hopefully at some point soon?. There will be
another Beta release very soon?, hopefully including improved CORS support.

Please don't ask for/about the KH software here. It's a separate project
that has diverged significantly. If you are so inclined any search
engine should point you to it.

We're happy to discuss any issues/problems you might have with official
Icecast.
We're also interested to hear about what kind of features our users are
looking for.

Cheers,
Thomas

> Am 28.08.2018 um 23:05 schrieb jake:
>>
>> ?
>>
>> ?
>>
>> https://gitlab.xiph.org/xiph/icecast-server/commits/master
>>
>> ?
>>
>> The last commit was a week ago, and it looks fairly active, so.... yes?
>>
>> ?
>>
>> On 2018-08-29 05:28, Chernabog wrote:
>>
>>> Hello! I was just wondering if the IceCast platform was still being
>>> actively developed?
>>>
>>> ?
>>>
>>> Thank you,
>>>
>>> ?
>>>
>>> Jason
>>>
>>> -- 
>>>
>>> /*Define your destiny in Ultima Genesis: Call of the Avatar
>>> <https://titanx.games>! Play forfree today.*/
>>>
>>> *?Follow us on social media!*
>>>
>>> <https://www.facebook.com/titanxgames/><https://twitter.com/intent/user?screen_name=_TitanXGames>
>>>
>>>
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org <mailto: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/20180829/3d80410c/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: blocked.gif
Type: image/gif
Size: 118 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/3d80410c/attachment.gif>

From subscription at nextdial.com.br  Wed Aug 29 12:45:38 2018
From: subscription at nextdial.com.br (subscription at nextdial.com.br)
Date: Wed, 29 Aug 2018 09:45:38 -0300
Subject: [Icecast] Icecast is shutdown / client auth failed with ""
In-Reply-To: <a2e1daeac4e54703877c2fe12542f44c@nextdial.com.br>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
 <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
 <a2e1daeac4e54703877c2fe12542f44c@nextdial.com.br>
Message-ID: <966c3075bf4e4fff9969ba7f8155426d@nextdial.com.br>

Hello,
  
 In order to identify if was some issue regard to the auth api we include 
some trace logs and we move it to other machine.

Bellow is what trace we are generating (date, result, elapsed time in 
milleseconds, request):
    [8/29/18 11:49:00 AM]     200       0.3721    
action=listener_add&server=r22&port=443&client=2616&mount=/alphafmsp&user=&p
ass=&ip=177.223.XX&agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) 
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
[8/29/18 11:49:00 AM]     200       0.6181    
action=listener_remove&server=r22&port=443&client=673&mount=/aradiorock&user
=&pass=&duration=983&ip=191.206.XX&agent=NxApp/1.18.07.10 (Xamarin; 
Android; 27; Mi A2 Lite; Xiaomi)
[8/29/18 11:49:00 AM]     200       0.4407    
action=listener_add&server=r22&port=443&client=2618&mount=/alphafmsp&user=&p
ass=&ip=177.138.XX&agent=Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
[8/29/18 11:49:00 AM]     200       0.3872    
action=listener_add&server=r20&port=443&client=3040&mount=/aradiorock&user=&
pass=&ip=189.8.XX&agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) 
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
  
 Even with responses quickly responses we still getting:
  
 [2018-08-29  11:49:08] INFO auth_url/url_add_listener client auth 
(http://10.68.0.136:8001/listener/add) failed with ""
  
 And sometimes the icecast process just shutdown! Bellow is the last second 
logged:
  
 AUTH ACCESS.LOG
  
 [8/29/18 11:49:10 AM]    200   0.3864    
action=listener_add&server=r20&port=443&client=3071&mount=/amorfm&user=&pass
=&ip=191.39.XXX&agent=App/2.4.2 (Linux;Android 7.0) ExoPlayerLib/2.5.4
[8/29/18 11:49:10 AM]    200   0.204      
action=listener_add&server=r20&port=443&client=3070&mount=/alphafmsp&user=&p
ass=&ip=201.81.XXX&agent=Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
[8/29/18 11:49:10 AM]    200   0.2598    
action=listener_remove&server=r22&port=443&client=2625&mount=/alphafmsp&user
=&pass=&duration=6&ip=177.95.XXX&agent=Mozilla/5.0 (Windows NT 6.1) 
AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36
[8/29/18 11:49:10 AM]    200   0.1067    
action=listener_remove&server=r20&port=443&client=512&mount=/aradiorock&user
=&pass=&duration=1087&ip=179.127.XXX&agent=Mozilla/5.0 (Windows NT 6.1; 
Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.139 
Safari/537.36
[8/29/18 11:49:10 AM]    200   0.4311    
action=listener_add&server=r20&port=443&client=3072&mount=/alphafmsp&user=&p
ass=&ip=201.52.XXX&agent=Mozilla/5.0 (Windows NT 6.1) AppleWebKit/537.36 
(KHTML, like Gecko) Chrome/43.0.2357.132 Safari/537.36
[8/29/18 11:49:10 AM]    200   0.3617    
action=listener_add&server=r22&port=443&client=2638&mount=/aradiorock&user=&
pass=&ip=179.241.XXX&agent=NxApp/1.18.07.10 (Xamarin; Android; 26; moto x4; 
motorola)
  
 ICECAST ERROR.LOG (machine named "r20")
  
 [2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on 
/amorfm
[2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on 
/alphafmsp
[2018-08-29  11:49:10] DBUG auth/add_listener_to_source max on /amorfm is 
-1 (cur 6)
[2018-08-29  11:49:10] DBUG auth/add_listener_to_source Added client to 
/amorfm
[2018-08-29  11:49:10] DBUG auth/add_authenticated_listener client 
authenticated, passed to source
[2018-08-29  11:49:10] DBUG auth/add_listener_to_source max on /alphafmsp 
is 750 (cur 750)
[2018-08-29  11:49:10] DBUG fserve/fserve_add_client Adding client to file 
serving engine
[2018-08-29  11:49:10] DBUG fserve/fserve_add_pending fserve handler waking 
up
[2018-08-29  11:49:10] DBUG auth/auth_release ...refcount on auth_t 
/alphafmsp is now 751
[2018-08-29  11:49:10] INFO auth/auth_new_listener client 3070 failed
[2018-08-29  11:49:10] DBUG fserve/fserv_thread_function fserve handler 
exit
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
client_connections (2719)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
client_connections (2720)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients 
(1331)
[2018-08-29  11:49:10] DBUG client/client_read_bytes reading from 
connection has failed
[2018-08-29  11:49:10] INFO source/send_to_listener Client 512 
(179.127.XXX) has fallen too far behind, removing
[2018-08-29  11:49:10] DBUG auth/queue_auth_client ...refcount on auth_t 
/aradiorock is now 502
[2018-08-29  11:49:10] INFO auth/queue_auth_client auth on /aradiorock has 
1 pending
[2018-08-29  11:49:10] DBUG source/source_main Client removed
[2018-08-29  11:49:10] INFO source/source_main listener count on 
/aradiorock now 500
[2018-08-29  11:49:10] DBUG source/source_main Client added for mountpoint 
(/amorfm)
[2018-08-29  11:49:10] INFO source/source_main listener count on /amorfm 
now 7
[2018-08-29  11:49:10] INFO auth/auth_add_listener adding client for 
authentication
[2018-08-29  11:49:10] DBUG auth/queue_auth_client ...refcount on auth_t 
/alphafmsp is now 752
[2018-08-29  11:49:10] INFO auth/queue_auth_client auth on /alphafmsp has 1 
pending
[2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on 
/aradiorock
[2018-08-29  11:49:10] DBUG auth/auth_release ...refcount on auth_t 
/aradiorock is now 501
[2018-08-29  11:49:10] DBUG format/format_check_http_buffer processing 
pending client headers
[2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on 
/alphafmsp
[2018-08-29  11:49:10] DBUG auth/add_listener_to_source max on /alphafmsp 
is 750 (cur 750)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients 
(1332)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
connections (3046)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients 
(1331)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update "/aradiorock" 
slow_listeners (63)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global listeners 
(1317)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update "/aradiorock" 
listeners (500)
[2018-08-29  11:49:10] DBUG fserve/fserve_add_client Adding client to file 
serving engine
[2018-08-29  11:49:10] DBUG fserve/fserve_add_pending fserve handler waking 
up
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients 
(1332)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
connections (3047)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update "/amorfm" 
listener_peak (7)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update "/amorfm" 
listeners (7)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
client_connections (2721)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients 
(1331)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global listeners 
(1318)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
listener_connections (2347)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients 
(1332)
[2018-08-29  11:49:10] DBUG stats/modify_node_event update global 
connections (3048)
[2018-08-29  11:49:10] DBUG auth/auth_release ...refcount on auth_t 
/alphafmsp is now 751
[2018-08-29  11:49:10] INFO auth/auth_new_listener client 3072 failed
[2018-08-29  11:49:10] DBUG auth/queue_auth_client ...refcount on auth_t 
/alphafmsp is now 751
[2018-08-29  11:49:10] INFO auth/queue_auth_client auth on /alphafmsp has 1 
pending
[2018-08-29  11:49:10] DBUG fserve/fserv_thread_function fserve handler 
exit
[2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on 
/alphafmsp
  
 I can't figure out why icecast is shutting down and why sometimes it can't 
authenticate the request.
  
 It happens with different loads. Sometimes with about 2500, others with 
3000 and others with about 4200 listeners.
  
 Other useful info: we have a hearbeat api that do a "status-json.xsl" 
request at every 4s.
  
 Any ideas?
  

  
  
 Best,
 Thiago
  
  

----------------------------------------
 De: "subscription at nextdial.com.br" <subscription at nextdial.com.br>
Enviado: sexta-feira, 24 de agosto de 2018 20:51
Para: icecast at xiph.org
Assunto: Client auth failed with ""   
  Hello,
 We are using url authentication and getting the item bellow at the log:
  
 [2018-08-24  23:26:05] INFO auth_url/url_add_listener client auth 
(http://127.0.0.1:8001/listener/add) failed with ""
  
 I put try/catch and reviewed all my code ensure always return a proper 
status and header error code, so what trigger this kind of error?

    
    
   Regards,
   Thiago
    


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

From sytze.visser at gmail.com  Wed Aug 29 14:25:33 2018
From: sytze.visser at gmail.com (Sytze Visser)
Date: Wed, 29 Aug 2018 16:25:33 +0200
Subject: [Icecast] Icecast is shutdown / client auth failed with ""
In-Reply-To: <966c3075bf4e4fff9969ba7f8155426d@nextdial.com.br>
References: <ef1c5b8a61174b1b8ca13179e05c35ae@nextdial.com.br>
 <7bbe79b1db49481eb462ca4d0ce66e13@nextdial.com.br>
 <a2e1daeac4e54703877c2fe12542f44c@nextdial.com.br>
 <966c3075bf4e4fff9969ba7f8155426d@nextdial.com.br>
Message-ID: <CAGrLxecfX2Uf9qEygRsHSktveq26Lq2d_+9UoVi2t1bcV49RsQ@mail.gmail.com>

Hi all

I still have to analyze my problem comma but I'll let you know if it is
exactly the same.

Luckily my server is not in production yet. I am still testing.

Running Ubuntu 16.04 and Ice cast 2.4.2.

Is there anyone out there that has also had a similar problem of the
service coming to an abrupt stop.

On Wed, 29 Aug 2018, 14:45 subscription at nextdial.com.br, <
subscription at nextdial.com.br> wrote:

> Hello,
>
> In order to identify if was some issue regard to the auth api we include
> some trace logs and we move it to other machine.
>
> Bellow is what trace we are generating (date, result, elapsed time in
> milleseconds, request):
>
> [8/29/18 11:49:00 AM]     200       0.3721
> action=listener_add&server=r22&port=443&client=2616&mount=/alphafmsp&user=&pass=&ip=177.223.XX&agent=Mozilla/5.0
> (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/68.0.3440.106 Safari/537.36
> [8/29/18 11:49:00 AM]     200       0.6181
> action=listener_remove&server=r22&port=443&client=673&mount=/aradiorock&user=&pass=&duration=983&ip=191.206.XX&agent=NxApp/
> 1.18.07.10 (Xamarin; Android; 27; Mi A2 Lite; Xiaomi)
> [8/29/18 11:49:00 AM]     200       0.4407
> action=listener_add&server=r22&port=443&client=2618&mount=/alphafmsp&user=&pass=&ip=177.138.XX&agent=Mozilla/5.0
> (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/68.0.3440.106 Safari/537.36
> [8/29/18 11:49:00 AM]     200       0.3872
> action=listener_add&server=r20&port=443&client=3040&mount=/aradiorock&user=&pass=&ip=189.8.XX&agent=Mozilla/5.0
> (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/68.0.3440.106 Safari/537.36
>
> Even with responses quickly responses we still getting:
>
> [2018-08-29  11:49:08] INFO auth_url/url_add_listener client auth (
> http://10.68.0.136:8001/listener/add) failed with ""
>
> And sometimes the icecast process just shutdown! Bellow is the last second
> logged:
>
> AUTH ACCESS.LOG
>
> [8/29/18 11:49:10 AM]    200   0.3864
> action=listener_add&server=r20&port=443&client=3071&mount=/amorfm&user=&pass=&ip=191.39.XXX&agent=App/2.4.2
> (Linux;Android 7.0) ExoPlayerLib/2.5.4
> [8/29/18 11:49:10 AM]    200   0.204
> action=listener_add&server=r20&port=443&client=3070&mount=/alphafmsp&user=&pass=&ip=201.81.XXX&agent=Mozilla/5.0
> (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/68.0.3440.106 Safari/537.36
> [8/29/18 11:49:10 AM]    200   0.2598
> action=listener_remove&server=r22&port=443&client=2625&mount=/alphafmsp&user=&pass=&duration=6&ip=177.95.XXX&agent=Mozilla/5.0
> (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/68.0.3440.106 Safari/537.36
> [8/29/18 11:49:10 AM]    200   0.1067
> action=listener_remove&server=r20&port=443&client=512&mount=/aradiorock&user=&pass=&duration=1087&ip=179.127.XXX&agent=Mozilla/5.0
> (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/66.0.3359.139 Safari/537.36
> [8/29/18 11:49:10 AM]    200   0.4311
> action=listener_add&server=r20&port=443&client=3072&mount=/alphafmsp&user=&pass=&ip=201.52.XXX&agent=Mozilla/5.0
> (Windows NT 6.1) AppleWebKit/537.36 (KHTML, like Gecko)
> Chrome/43.0.2357.132 Safari/537.36
> [8/29/18 11:49:10 AM]    200   0.3617
> action=listener_add&server=r22&port=443&client=2638&mount=/aradiorock&user=&pass=&ip=179.241.XXX&agent=NxApp/
> 1.18.07.10 (Xamarin; Android; 26; moto x4; motorola)
>
> ICECAST ERROR.LOG (machine named "r20")
>
> [2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on
> /amorfm
> [2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on
> /alphafmsp
> [2018-08-29  11:49:10] DBUG auth/add_listener_to_source max on /amorfm is
> -1 (cur 6)
> [2018-08-29  11:49:10] DBUG auth/add_listener_to_source Added client to
> /amorfm
> [2018-08-29  11:49:10] DBUG auth/add_authenticated_listener client
> authenticated, passed to source
> [2018-08-29  11:49:10] DBUG auth/add_listener_to_source max on /alphafmsp
> is 750 (cur 750)
> [2018-08-29  11:49:10] DBUG fserve/fserve_add_client Adding client to file
> serving engine
> [2018-08-29  11:49:10] DBUG fserve/fserve_add_pending fserve handler
> waking up
> [2018-08-29  11:49:10] DBUG auth/auth_release ...refcount on auth_t
> /alphafmsp is now 751
> [2018-08-29  11:49:10] INFO auth/auth_new_listener client 3070 failed
> [2018-08-29  11:49:10] DBUG fserve/fserv_thread_function fserve handler
> exit
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> client_connections (2719)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> client_connections (2720)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients
> (1331)
> [2018-08-29  11:49:10] DBUG client/client_read_bytes reading from
> connection has failed
> [2018-08-29  11:49:10] INFO source/send_to_listener Client 512
> (179.127.XXX) has fallen too far behind, removing
> [2018-08-29  11:49:10] DBUG auth/queue_auth_client ...refcount on auth_t
> /aradiorock is now 502
> [2018-08-29  11:49:10] INFO auth/queue_auth_client auth on /aradiorock has
> 1 pending
> [2018-08-29  11:49:10] DBUG source/source_main Client removed
> [2018-08-29  11:49:10] INFO source/source_main listener count on
> /aradiorock now 500
> [2018-08-29  11:49:10] DBUG source/source_main Client added for mountpoint
> (/amorfm)
> [2018-08-29  11:49:10] INFO source/source_main listener count on /amorfm
> now 7
> [2018-08-29  11:49:10] INFO auth/auth_add_listener adding client for
> authentication
> [2018-08-29  11:49:10] DBUG auth/queue_auth_client ...refcount on auth_t
> /alphafmsp is now 752
> [2018-08-29  11:49:10] INFO auth/queue_auth_client auth on /alphafmsp has
> 1 pending
> [2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on
> /aradiorock
> [2018-08-29  11:49:10] DBUG auth/auth_release ...refcount on auth_t
> /aradiorock is now 501
> [2018-08-29  11:49:10] DBUG format/format_check_http_buffer processing
> pending client headers
> [2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on
> /alphafmsp
> [2018-08-29  11:49:10] DBUG auth/add_listener_to_source max on /alphafmsp
> is 750 (cur 750)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients
> (1332)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> connections (3046)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients
> (1331)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update "/aradiorock"
> slow_listeners (63)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> listeners (1317)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update "/aradiorock"
> listeners (500)
> [2018-08-29  11:49:10] DBUG fserve/fserve_add_client Adding client to file
> serving engine
> [2018-08-29  11:49:10] DBUG fserve/fserve_add_pending fserve handler
> waking up
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients
> (1332)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> connections (3047)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update "/amorfm"
> listener_peak (7)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update "/amorfm"
> listeners (7)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> client_connections (2721)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients
> (1331)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> listeners (1318)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> listener_connections (2347)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global clients
> (1332)
> [2018-08-29  11:49:10] DBUG stats/modify_node_event update global
> connections (3048)
> [2018-08-29  11:49:10] DBUG auth/auth_release ...refcount on auth_t
> /alphafmsp is now 751
> [2018-08-29  11:49:10] INFO auth/auth_new_listener client 3072 failed
> [2018-08-29  11:49:10] DBUG auth/queue_auth_client ...refcount on auth_t
> /alphafmsp is now 751
> [2018-08-29  11:49:10] INFO auth/queue_auth_client auth on /alphafmsp has
> 1 pending
> [2018-08-29  11:49:10] DBUG fserve/fserv_thread_function fserve handler
> exit
> [2018-08-29  11:49:10] DBUG auth/auth_run_thread 1 client(s) pending on
> /alphafmsp
>
> I can't figure out why icecast is shutting down and why sometimes it can't
> authenticate the request.
>
> It happens with different loads. Sometimes with about 2500, others with
> 3000 and others with about 4200 listeners.
>
> Other useful info: we have a hearbeat api that do a "status-json.xsl"
> request at every 4s.
>
> Any ideas?
>
>
>
> Best,
> Thiago
>
>
> ------------------------------
> *De*: "subscription at nextdial.com.br" <subscription at nextdial.com.br>
> *Enviado*: sexta-feira, 24 de agosto de 2018 20:51
> *Para*: icecast at xiph.org
> *Assunto*: Client auth failed with ""
>
> Hello,
> We are using url authentication and getting the item bellow at the log:
>
> [2018-08-24  23:26:05] INFO auth_url/url_add_listener client auth (
> http://127.0.0.1:8001/listener/add) failed with ""
>
> I put try/catch and reviewed all my code ensure always return a proper
> status and header error code, so what trigger this kind of error?
>
>
> Regards,
> Thiago
>
> _______________________________________________
> 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/20180829/b29daa14/attachment.htm>

From haenenhub at hotmail.com  Wed Aug 29 16:11:10 2018
From: haenenhub at hotmail.com (Hub. Haenen)
Date: Wed, 29 Aug 2018 16:11:10 +0000
Subject: [Icecast] Exit mailings
Message-ID: <AM4PR03MB1777B659D787C76B7B6502B6B9090@AM4PR03MB1777.eurprd03.prod.outlook.com>

Could you please take me of the mailinglist of Icecast. Thanks!


Greetz,



Hub.

<http://nl.linkedin.com/in/hubhaenen>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/b6a10b4a/attachment.htm>

From epirat07 at gmail.com  Wed Aug 29 16:37:58 2018
From: epirat07 at gmail.com (Marvin Scholz)
Date: Wed, 29 Aug 2018 18:37:58 +0200
Subject: [Icecast] Exit mailings
In-Reply-To: <AM4PR03MB1777B659D787C76B7B6502B6B9090@AM4PR03MB1777.eurprd03.prod.outlook.com>
References: <AM4PR03MB1777B659D787C76B7B6502B6B9090@AM4PR03MB1777.eurprd03.prod.outlook.com>
Message-ID: <CFBF0FC4-2363-4848-8AAD-DD75A00BF858@gmail.com>

You can unsubscribe from this list at 
http://lists.xiph.org/mailman/listinfo/icecast

On 29 Aug 2018, at 18:11, Hub. Haenen wrote:

> Could you please take me of the mailinglist of Icecast. Thanks!
>
>
> Greetz,
>
>
>
> Hub.
>
> <http://nl.linkedin.com/in/hubhaenen>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From awi3 at live.com  Wed Aug 29 16:15:50 2018
From: awi3 at live.com (Alan Bowness)
Date: Wed, 29 Aug 2018 16:15:50 +0000
Subject: [Icecast] Exit mailings
Message-ID: <VI1PR04MB44314E144E759CC4F42FAD00EF090@VI1PR04MB4431.eurprd04.prod.outlook.com>

And me too, please
[Smile]

From: Hub. Haenen<mailto:haenenhub at hotmail.com>
Sent: Wednesday, August 29, 2018 5:11 PM
To: Icecast at xiph.org<mailto:Icecast at xiph.org>
Subject: [Icecast] Exit mailings


Could you please take me of the mailinglist of Icecast. Thanks!



Greetz,





Hub.

<http://nl.linkedin.com/in/hubhaenen>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/47b1490f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: wlEmoticon-smile[1].png
Type: image/png
Size: 1046 bytes
Desc: wlEmoticon-smile[1].png
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180829/47b1490f/attachment.png>

From epirat07 at gmail.com  Wed Aug 29 16:48:36 2018
From: epirat07 at gmail.com (Marvin Scholz)
Date: Wed, 29 Aug 2018 18:48:36 +0200
Subject: [Icecast] Exit mailings
In-Reply-To: <VI1PR04MB44314E144E759CC4F42FAD00EF090@VI1PR04MB4431.eurprd04.prod.outlook.com>
References: <VI1PR04MB44314E144E759CC4F42FAD00EF090@VI1PR04MB4431.eurprd04.prod.outlook.com>
Message-ID: <910E3B77-8B6B-4E1F-9A99-08FFCE929D5D@gmail.com>

You can unsubscribe from this list at 
http://lists.xiph.org/mailman/listinfo/icecast

On 29 Aug 2018, at 18:15, Alan Bowness wrote:

> And me too, please
> [Smile]
>
> From: Hub. Haenen<mailto:haenenhub at hotmail.com>
> Sent: Wednesday, August 29, 2018 5:11 PM
> To: Icecast at xiph.org<mailto:Icecast at xiph.org>
> Subject: [Icecast] Exit mailings
>
>
> Could you please take me of the mailinglist of Icecast. Thanks!
>
>
>
> Greetz,
>
>
>
>
>
> Hub.
>
> <http://nl.linkedin.com/in/hubhaenen>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From sytze.visser at gmail.com  Thu Aug 30 20:27:14 2018
From: sytze.visser at gmail.com (Sytze Visser)
Date: Thu, 30 Aug 2018 22:27:14 +0200
Subject: [Icecast] Crash!!!
Message-ID: <CAGrLxefweNG7O8JXypvWg7DJhuz=YpEzXV3D+pOB6MHgJ3z4hg@mail.gmail.com>

Dear members

I have for 3 days now been battling with an icecast crash. Since I have 3
months of after hours experience I am taking some real strain in resolving
it and hope someone can help. I have included as much info as possible.
Please let me know what else you need.

*sytze at KerkRadio:~$ uname -a*
Linux KerkRadio 4.15.0-1022-azure #22~16.04.1-Ubuntu SMP Thu Aug 16
10:31:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

*sytze at KerkRadio:~$ cat /etc/icecast2/icecast.xml*
<icecast>
    <hostname>kerkradio.co.za</hostname>
    <location>South Africa</location>
    <admin>sytze.visser at gmail.com</admin>
    <limits>
        <clients>100</clients>
        <sources>2</sources>
        <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>
    <authentication>
        <source-password>hackme2</source-password>
        <relay-password>hackme2</relay-password>
        <admin-user>admin</admin-user>
        <admin-password>hackme2</admin-password>
    </authentication>
    <listen-socket>
        <port>8000</port>
    </listen-socket>
    <http-headers>
        <header name="Access-Control-Allow-Origin" value="*" />
    </http-headers>
    <fileserve>1</fileserve>
    <paths>
        <basedir>@pkgdatadir@</basedir>
        <logdir>@localstatedir@/log/@PACKAGE@</logdir>
        <webroot>@pkgdatadir@/web</webroot>
        <adminroot>@pkgdatadir@/admin</adminroot>
        <alias source="/" destination="/status.xsl"/>
    </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>
    </security>
</icecast>

*sytze at KerkRadio:/var/log$ ps -ef|grep icecast2*
sytze    13704  6203  0 21:27 pts/0    00:00:00 grep --color=auto icecast2

*sytze at KerkRadio:/var/log$ sudo systemctl start icecast2.service*

*sytze at KerkRadio:/var/log$ sudo systemctl status icecast2.service*
sytze at KerkRadio:~$ sudo systemctl status icecast2.service
? icecast2.service - LSB: Icecast2 streaming media server
   Loaded: loaded (/etc/init.d/icecast2; bad; vendor preset: enabled)
   Active: active (exited) since Thu 2018-08-30 22:18:19 SAST; 2min 6s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1402 ExecStart=/etc/init.d/icecast2 start (code=exited,
status=0/SUCCESS)
    Tasks: 0
   Memory: 0B
      CPU: 0

Aug 30 22:18:21 KerkRadio icecast2[1402]:  * Starting streaming media
server icecast2
Aug 30 22:18:21 KerkRadio icecast2[1402]:    ...done.
Aug 30 22:18:18 KerkRadio systemd[1]: Starting LSB: Icecast2 streaming
media server...
Aug 30 22:18:19 KerkRadio systemd[1]: Started LSB: Icecast2 streaming media
server.

*sytze at KerkRadio:/var/log$ cat /var/log/apport.log*
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: called for pid 6530,
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: executable:
/usr/bin/icecast2 (command line "/usr/bin/icecast2 -b -c
/etc/icecast2/icecast.xml")
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: is_closing_session(): no
DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: apport: report
/var/crash/_usr_bin_icecast2.113.crash already exists and unseen, doing
nothing to avoid disk usage DoS
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: called for pid 10519,
signal 11, core limit 0, dump mode 1
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: executable:
/usr/bin/icecast2 (command line "/usr/bin/icecast2 -b -c
/etc/icecast2/icecast.xml")
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: is_closing_session():
no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: apport: report
/var/crash/_usr_bin_icecast2.113.crash already exists and unseen, doing
nothing to avoid disk usage DoS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180830/3ce0e474/attachment.htm>

From thomas at ruecker.fi  Fri Aug 31 08:35:29 2018
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B._R=c3=bccker?=)
Date: Fri, 31 Aug 2018 08:35:29 +0000
Subject: [Icecast] Crash!!!
In-Reply-To: <CAGrLxefweNG7O8JXypvWg7DJhuz=YpEzXV3D+pOB6MHgJ3z4hg@mail.gmail.com>
References: <CAGrLxefweNG7O8JXypvWg7DJhuz=YpEzXV3D+pOB6MHgJ3z4hg@mail.gmail.com>
Message-ID: <aac211ea-3997-efd7-93f8-df4457f53694@ruecker.fi>

Hi,


On 08/30/2018 08:27 PM, Sytze Visser wrote:
> Dear members
>
> I have for 3 days now been battling with an icecast crash. Since I
> have 3? months of after hours experience I am taking some real strain
> in resolving it and hope someone can help. I have included as much
> info as possible. Please let me know what else you need.
>

Which version of Icecast is this?

It might be helpful to see the Icecast error.log messages leading up to
a crash.
If possible at log level 4 DBUG.
I'm slightly confused because your path section looks rather odd.

Cheers,
Thomas


From sytze.visser at gmail.com  Fri Aug 31 10:01:45 2018
From: sytze.visser at gmail.com (Sytze Visser)
Date: Fri, 31 Aug 2018 12:01:45 +0200
Subject: [Icecast] Crash!!!
In-Reply-To: <aac211ea-3997-efd7-93f8-df4457f53694@ruecker.fi>
References: <CAGrLxefweNG7O8JXypvWg7DJhuz=YpEzXV3D+pOB6MHgJ3z4hg@mail.gmail.com>
 <aac211ea-3997-efd7-93f8-df4457f53694@ruecker.fi>
Message-ID: <CAGrLxefTTYdN25Q-LRHhosxP-8At19hSutqYaKgcoAr0D+xWmQ@mail.gmail.com>

Hi there

It's verion 2.4.2.

Let me figure out how to do the Log level 4 and I will be back in about 7
hours.

Greetings from South Africa! 12pm!

On Fri, Aug 31, 2018 at 10:35 AM Thomas B. R?cker <thomas at ruecker.fi> wrote:

> Hi,
>
>
> On 08/30/2018 08:27 PM, Sytze Visser wrote:
> > Dear members
> >
> > I have for 3 days now been battling with an icecast crash. Since I
> > have 3  months of after hours experience I am taking some real strain
> > in resolving it and hope someone can help. I have included as much
> > info as possible. Please let me know what else you need.
> >
>
> Which version of Icecast is this?
>
> It might be helpful to see the Icecast error.log messages leading up to
> a crash.
> If possible at log level 4 DBUG.
> I'm slightly confused because your path section looks rather odd.
>
> Cheers,
> Thomas
> _______________________________________________
> 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/20180831/3ccfa266/attachment.htm>

From henk.vande.ridder at solcon.nl  Fri Aug 31 19:03:21 2018
From: henk.vande.ridder at solcon.nl (Henk van de Ridder)
Date: Fri, 31 Aug 2018 21:03:21 +0200
Subject: [Icecast] Crash!!!
Message-ID: <000001d4415d$494b69b0$dbe23d10$@solcon.nl>

I still see: @pkgdatadir@, etc. in the paths of the icecast.xml. 
Is this the used configuration file for the actual icecast ?
Then the should be replaced by the actual directory names. Isn't  it ?
Henk


-----Oorspronkelijk bericht-----
Van: Icecast [mailto:icecast-bounces at xiph.org] Namens icecast-request at xiph.org
Verzonden: vrijdag 31 augustus 2018 14:00
Aan: icecast at xiph.org
Onderwerp: Icecast Digest, Vol 170, Issue 19

Send Icecast mailing list submissions to
	icecast at xiph.org

To subscribe or unsubscribe via the World Wide Web, visit
	http://lists.xiph.org/mailman/listinfo/icecast
or, via email, send a message with subject or body 'help' to
	icecast-request at xiph.org

You can reach the person managing the list at
	icecast-owner at xiph.org

When replying, please edit your Subject line so it is more specific than "Re: Contents of Icecast digest..."


Today's Topics:

   1. Crash!!! (Sytze Visser)
   2. Re: Crash!!! (Thomas B. R?cker)
   3. Re: Crash!!! (Sytze Visser)


----------------------------------------------------------------------

Message: 1
Date: Thu, 30 Aug 2018 22:27:14 +0200
From: Sytze Visser <sytze.visser at gmail.com>
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: [Icecast] Crash!!!
Message-ID:
	<CAGrLxefweNG7O8JXypvWg7DJhuz=YpEzXV3D+pOB6MHgJ3z4hg at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Dear members

I have for 3 days now been battling with an icecast crash. Since I have 3 months of after hours experience I am taking some real strain in resolving it and hope someone can help. I have included as much info as possible.
Please let me know what else you need.

*sytze at KerkRadio:~$ uname -a*
Linux KerkRadio 4.15.0-1022-azure #22~16.04.1-Ubuntu SMP Thu Aug 16
10:31:05 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

*sytze at KerkRadio:~$ cat /etc/icecast2/icecast.xml* <icecast>
    <hostname>kerkradio.co.za</hostname>
    <location>South Africa</location>
    <admin>sytze.visser at gmail.com</admin>
    <limits>
        <clients>100</clients>
        <sources>2</sources>
        <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>
    <authentication>
        <source-password>hackme2</source-password>
        <relay-password>hackme2</relay-password>
        <admin-user>admin</admin-user>
        <admin-password>hackme2</admin-password>
    </authentication>
    <listen-socket>
        <port>8000</port>
    </listen-socket>
    <http-headers>
        <header name="Access-Control-Allow-Origin" value="*" />
    </http-headers>
    <fileserve>1</fileserve>
    <paths>
        <basedir>@pkgdatadir@</basedir>
        <logdir>@localstatedir@/log/@PACKAGE@</logdir>
        <webroot>@pkgdatadir@/web</webroot>
        <adminroot>@pkgdatadir@/admin</adminroot>
        <alias source="/" destination="/status.xsl"/>
    </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>
    </security>
</icecast>

*sytze at KerkRadio:/var/log$ ps -ef|grep icecast2*
sytze    13704  6203  0 21:27 pts/0    00:00:00 grep --color=auto icecast2

*sytze at KerkRadio:/var/log$ sudo systemctl start icecast2.service*

*sytze at KerkRadio:/var/log$ sudo systemctl status icecast2.service* sytze at KerkRadio:~$ sudo systemctl status icecast2.service ? icecast2.service - LSB: Icecast2 streaming media server
   Loaded: loaded (/etc/init.d/icecast2; bad; vendor preset: enabled)
   Active: active (exited) since Thu 2018-08-30 22:18:19 SAST; 2min 6s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 1402 ExecStart=/etc/init.d/icecast2 start (code=exited,
status=0/SUCCESS)
    Tasks: 0
   Memory: 0B
      CPU: 0

Aug 30 22:18:21 KerkRadio icecast2[1402]:  * Starting streaming media server icecast2
Aug 30 22:18:21 KerkRadio icecast2[1402]:    ...done.
Aug 30 22:18:18 KerkRadio systemd[1]: Starting LSB: Icecast2 streaming media server...
Aug 30 22:18:19 KerkRadio systemd[1]: Started LSB: Icecast2 streaming media server.

*sytze at KerkRadio:/var/log$ cat /var/log/apport.log*
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: called for pid 6530, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: executable:
/usr/bin/icecast2 (command line "/usr/bin/icecast2 -b -c
/etc/icecast2/icecast.xml")
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 9885) Thu Aug 30 20:28:08 2018: apport: report /var/crash/_usr_bin_icecast2.113.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: called for pid 10519, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: executable:
/usr/bin/icecast2 (command line "/usr/bin/icecast2 -b -c
/etc/icecast2/icecast.xml")
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: is_closing_session():
no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 10527) Thu Aug 30 20:38:18 2018: apport: report /var/crash/_usr_bin_icecast2.113.crash already exists and unseen, doing nothing to avoid disk usage DoS
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20180830/3ce0e474/attachment-0001.html>

------------------------------

Message: 2
Date: Fri, 31 Aug 2018 08:35:29 +0000
From: Thomas B. R?cker <thomas at ruecker.fi>
To: icecast at xiph.org
Subject: Re: [Icecast] Crash!!!
Message-ID: <aac211ea-3997-efd7-93f8-df4457f53694 at ruecker.fi>
Content-Type: text/plain; charset=utf-8

Hi,


On 08/30/2018 08:27 PM, Sytze Visser wrote:
> Dear members
>
> I have for 3 days now been battling with an icecast crash. Since I 
> have 3  months of after hours experience I am taking some real strain 
> in resolving it and hope someone can help. I have included as much 
> info as possible. Please let me know what else you need.
>

Which version of Icecast is this?

It might be helpful to see the Icecast error.log messages leading up to a crash.
If possible at log level 4 DBUG.
I'm slightly confused because your path section looks rather odd.

Cheers,
Thomas


------------------------------

Message: 3
Date: Fri, 31 Aug 2018 12:01:45 +0200
From: Sytze Visser <sytze.visser at gmail.com>
To: Icecast streaming server user discussions <icecast at xiph.org>
Subject: Re: [Icecast] Crash!!!
Message-ID:
	<CAGrLxefTTYdN25Q-LRHhosxP-8At19hSutqYaKgcoAr0D+xWmQ at mail.gmail.com>
Content-Type: text/plain; charset="utf-8"

Hi there

It's verion 2.4.2.

Let me figure out how to do the Log level 4 and I will be back in about 7 hours.

Greetings from South Africa! 12pm!

On Fri, Aug 31, 2018 at 10:35 AM Thomas B. R?cker <thomas at ruecker.fi> wrote:

> Hi,
>
>
> On 08/30/2018 08:27 PM, Sytze Visser wrote:
> > Dear members
> >
> > I have for 3 days now been battling with an icecast crash. Since I 
> > have 3  months of after hours experience I am taking some real 
> > strain in resolving it and hope someone can help. I have included as 
> > much info as possible. Please let me know what else you need.
> >
>
> Which version of Icecast is this?
>
> It might be helpful to see the Icecast error.log messages leading up 
> to a crash.
> If possible at log level 4 DBUG.
> I'm slightly confused because your path section looks rather odd.
>
> Cheers,
> Thomas
> _______________________________________________
> 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/20180831/3ccfa266/attachment-0001.html>

------------------------------

Subject: Digest Footer

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


------------------------------

End of Icecast Digest, Vol 170, Issue 19
****************************************