From sm at noisynotes.com Thu Apr 2 15:32:24 2015 From: sm at noisynotes.com (Steve Matzura) Date: Thu, 02 Apr 2015 11:32:24 -0400 Subject: [Icecast] Icecast won't start on system boot In-Reply-To: <55178C06.6060303@ruecker.fi> References: <8b98hadgtr12f2l1hi4i8o7gfofb25l386@4ax.com> <55143451.6050006@ruecker.fi> <55146D8D.3040308@ruecker.fi> <55178C06.6060303@ruecker.fi> Message-ID: <23oqhap33h3lt3fjsa7d9bklu8fkg4oqn4@4ax.com> On Sun, 29 Mar 2015 05:22:14 +0000, you wrote: >On 03/26/2015 09:02 PM, Steve Matzura wrote: >> Well, here's the whole output from systemctl. >> >> # systemctl status icecast -l >> icecast.service - Icecast Network Audio Streaming Server >> Loaded: loaded (/usr/lib/systemd/system/icecast.service; enabled) >> Active: failed (Result: exit-code) since Thu 2015-03-26 18:06:10 >> CET; 38min ago >> Process: 839 ExecStart=/usr/bin/icecast -c /etc/icecast.xml >> (code=exited, status=1/FAILURE) >> Main PID: 839 (code=exited, status=1/FAILURE) >> CGroup: /system.slice/icecast.service >> >> Mar 26 18:06:09 {my-FQDN} systemd[1]: Starting Icecast Network Audio >> Streaming Server... >> Mar 26 18:06:09 {my-FQDN} systemd[1]: Started Icecast Network Audio >> Streaming Server. >> Mar 26 18:06:10 {my-FQDN} icecast[839]: [2015-03-26 18:06:09] WARN >> CONFIG/_parse_root Warning, not configured, using default >> value "Earth". >> Mar 26 18:06:10 {my-FQDN} icecast[839]: [2015-03-26 18:06:09] WARN >> CONFIG/_parse_root Warning, contact not configured, using >> default value "icemaster at localhost". >> Mar 26 18:06:10 {my-FQDN} icecast[839]: ERROR: You should not run >> icecast2 as root >> Mar 26 18:06:10 {my-FQDN} icecast[839]: Use the changeowner directive >> in the config file >> Mar 26 18:06:10 {my-FQDN} systemd[1]: icecast.service: main process >> exited, code=exited, status=1/FAILURE >> Mar 26 18:06:10 {my-FQDN} systemd[1]: Unit icecast.service entered >> failed state. >> >> I have since defined location and contact, but they were only warnings >> anyway. The XML definitely contains a changeowner section with user >> defined as nobody and group defined as nogroup. > >Are those inside the section? Ya know, there are none so blind ... IT'S BEEN COMMENTED OUT! 0 I'll try it with the comment lines removed and let you know. I swear I read this a half a hundred times and didn't notice it until JUST NOW! From nate at themillerhome.org Fri Apr 3 21:02:45 2015 From: nate at themillerhome.org (Nathan Miller) Date: Fri, 3 Apr 2015 14:02:45 -0700 Subject: [Icecast] After I enabled SSL, stream mountpoints broke Message-ID: I'm running Icecast package 2.4.1 on Ubuntu 14.04 from ttp:// download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04. I've been running on this server for about 6 months now without any issue and all my streams run great. This icecast server is running on the same host that my wordpress site is running on. This is all on my own private server, not a hosting service. Recently I decided to switch everything to SSL and all went well with the exception of the icecast server. The SSL portion of the icecast server is actually working just fine and the SSL certificate is loading on the admin page on all modern browsers without any issue or error. I can see the full admin page and navigate it without issue. The problem is as soon as I add this line to the section, as required to load the PEM certificate, my mountpoint streams stopped loading: /usr/share/icecast2/ssl/mysslcertname.pem Then my icecast error log fills with this whenever anyone attempts to hit any of the stream mountpoints that failed to load: [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for file /stream1 (/usr/share/icecast2/web/stream1) [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/stream1" No such file or directory [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for file /stream2 (/usr/share/icecast2/web/stream2) [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/stream2" No such file or directory There is nothing in the error logs after I've added this line to the and restarted icecast so I'm not sure what is breaking but I'm guessing from the errors whenever someone tries to hit the mountpoint that the file that was supposed to be created never is. Not sure why adding to the path would cause this issue, but as soon as I remove it all returns to a working order with stream mountpoints loading and working perfectly...though now SSL is broken again :( Hopefully someone can provide some guidance here! Thanks! Nathan -------------- next part -------------- An HTML attachment was scrubbed... URL: From lion at lion.leolix.org Fri Apr 3 22:41:27 2015 From: lion at lion.leolix.org (Philipp Schafft) Date: Fri, 03 Apr 2015 22:41:27 +0000 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: References: Message-ID: <20150403224130.5927F12CF0@grassland.keep-cool.org> Good evening, On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote: > I'm running Icecast package 2.4.1 on Ubuntu 14.04 > from ttp://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04. > > > I've been running on this server for about 6 months now without any > issue and all my streams run great. This icecast server is running on > the same host that my wordpress site is running on. This is all on my > own private server, not a hosting service. > > > Recently I decided to switch everything to SSL and all went well with > the exception of the icecast server. The SSL portion of the icecast > server is actually working just fine and the SSL certificate is > loading on the admin page on all modern browsers without any issue or > error. I can see the full admin page and navigate it without issue. > The problem is as soon as I add this line to the section, as > required to load the PEM certificate, my mountpoint streams stopped > loading: > > > /usr/share/icecast2/ssl/mysslcertname.pem > > > > Then my icecast error log fills with this whenever anyone attempts to > hit any of the stream mountpoints that failed to load: > > > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for > file /stream1 (/usr/share/icecast2/web/stream1) > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file > "/usr/share/icecast2/web/stream1" No such file or directory > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for > file /stream2 (/usr/share/icecast2/web/stream2) > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file > "/usr/share/icecast2/web/stream2" No such file or directory Those messages tell that there is no mount nor a file in web/. I suspect that the stream is not mounted (= the source is not connected). > There is nothing in the error logs after I've added this line to the > and restarted icecast so I'm not sure what is breaking but I'm > guessing from the errors whenever someone tries to hit the mountpoint > that the file that was supposed to be created never is. Not sure why > adding to the path would cause this issue, but as soon as I remove it > all returns to a working order with stream mountpoints loading and > working perfectly...though now SSL is broken again :( Which source client do you use? If you switch the port to TLS that is used by the source client to connect you also need to set the source client to TLS mode. > Hopefully someone can provide some guidance here! Thanks! Please come back with the answers. I'm sure this isn't impossible. Have a good night! -- Philipp. (Rah of PH2) -------------- 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: From nate at themillerhome.org Sat Apr 4 02:42:14 2015 From: nate at themillerhome.org (Nathan Miller) Date: Fri, 3 Apr 2015 19:42:14 -0700 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: <20150403224130.5927F12CF0@grassland.keep-cool.org> References: <20150403224130.5927F12CF0@grassland.keep-cool.org> Message-ID: Philipp, Thank you for your quick response. I can't believe that I didn't think of that...I guess I just assumed that it would use SSL. I'm using Liquidsoap as my source client. Once you brought that up I started researching whether there was a way to force Liquidsoap to use SSL and from what I found it doesn't look like there is an option...but please correct me if you or anyone else who reads this knows differently. After I had a good idea of what was happening I found this other thread http://lists.xiph.org/pipermail/icecast/2015-January/013118.html that talks about exactly what I'm trying to do using Liquidsoap. I followed it and I'm good now running on two ports...one SSL and one not from connecting to Liquidsoap. Thanks again for your hint :) and please let me know if you've seen other ways to tackle this with Liquidsoap than what I setup. Nathan On Fri, Apr 3, 2015 at 3:41 PM, Philipp Schafft wrote: > Good evening, > > On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote: > > I'm running Icecast package 2.4.1 on Ubuntu 14.04 > > from ttp://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04 > . > > > > > > I've been running on this server for about 6 months now without any > > issue and all my streams run great. This icecast server is running on > > the same host that my wordpress site is running on. This is all on my > > own private server, not a hosting service. > > > > > > Recently I decided to switch everything to SSL and all went well with > > the exception of the icecast server. The SSL portion of the icecast > > server is actually working just fine and the SSL certificate is > > loading on the admin page on all modern browsers without any issue or > > error. I can see the full admin page and navigate it without issue. > > The problem is as soon as I add this line to the section, as > > required to load the PEM certificate, my mountpoint streams stopped > > loading: > > > > > > > /usr/share/icecast2/ssl/mysslcertname.pem > > > > > > > > Then my icecast error log fills with this whenever anyone attempts to > > hit any of the stream mountpoints that failed to load: > > > > > > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for > > file /stream1 (/usr/share/icecast2/web/stream1) > > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file > > "/usr/share/icecast2/web/stream1" No such file or directory > > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for > > file /stream2 (/usr/share/icecast2/web/stream2) > > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file > > "/usr/share/icecast2/web/stream2" No such file or directory > > Those messages tell that there is no mount nor a file in web/. I suspect > that the stream is not mounted (= the source is not connected). > > > > There is nothing in the error logs after I've added this line to the > > and restarted icecast so I'm not sure what is breaking but I'm > > guessing from the errors whenever someone tries to hit the mountpoint > > that the file that was supposed to be created never is. Not sure why > > adding to the path would cause this issue, but as soon as I remove it > > all returns to a working order with stream mountpoints loading and > > working perfectly...though now SSL is broken again :( > > Which source client do you use? If you switch the port to TLS that is > used by the source client to connect you also need to set the source > client to TLS mode. > > > > Hopefully someone can provide some guidance here! Thanks! > > Please come back with the answers. I'm sure this isn't impossible. > > Have a good night! > > -- > Philipp. > (Rah of PH2) > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From support at psrfm.org.au Sat Apr 4 03:40:26 2015 From: support at psrfm.org.au (PSRFM Support) Date: Sat, 4 Apr 2015 14:40:26 +1100 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: References: <20150403224130.5927F12CF0@grassland.keep-cool.org> Message-ID: <000501d06e89$170346d0$4509d470$@psrfm.org.au> Can you remove these emails from going to my address please. From: icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] On Behalf Of Nathan Miller Sent: Saturday, 4 April 2015 1:42 PM To: Icecast streaming server user discussions Subject: Re: [Icecast] After I enabled SSL, stream mountpoints broke Philipp, Thank you for your quick response. I can't believe that I didn't think of that...I guess I just assumed that it would use SSL. I'm using Liquidsoap as my source client. Once you brought that up I started researching whether there was a way to force Liquidsoap to use SSL and from what I found it doesn't look like there is an option...but please correct me if you or anyone else who reads this knows differently. After I had a good idea of what was happening I found this other thread http://lists.xiph.org/pipermail/icecast/2015-January/013118.html that talks about exactly what I'm trying to do using Liquidsoap. I followed it and I'm good now running on two ports...one SSL and one not from connecting to Liquidsoap. Thanks again for your hint :) and please let me know if you've seen other ways to tackle this with Liquidsoap than what I setup. Nathan On Fri, Apr 3, 2015 at 3:41 PM, Philipp Schafft > wrote: Good evening, On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote: > I'm running Icecast package 2.4.1 on Ubuntu 14.04 > from ttp://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04 . > > > I've been running on this server for about 6 months now without any > issue and all my streams run great. This icecast server is running on > the same host that my wordpress site is running on. This is all on my > own private server, not a hosting service. > > > Recently I decided to switch everything to SSL and all went well with > the exception of the icecast server. The SSL portion of the icecast > server is actually working just fine and the SSL certificate is > loading on the admin page on all modern browsers without any issue or > error. I can see the full admin page and navigate it without issue. > The problem is as soon as I add this line to the section, as > required to load the PEM certificate, my mountpoint streams stopped > loading: > > > /usr/share/icecast2/ssl/mysslcertname.pem > > > > Then my icecast error log fills with this whenever anyone attempts to > hit any of the stream mountpoints that failed to load: > > > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for > file /stream1 (/usr/share/icecast2/web/stream1) > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file > "/usr/share/icecast2/web/stream1" No such file or directory > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for > file /stream2 (/usr/share/icecast2/web/stream2) > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file > "/usr/share/icecast2/web/stream2" No such file or directory Those messages tell that there is no mount nor a file in web/. I suspect that the stream is not mounted (= the source is not connected). > There is nothing in the error logs after I've added this line to the > and restarted icecast so I'm not sure what is breaking but I'm > guessing from the errors whenever someone tries to hit the mountpoint > that the file that was supposed to be created never is. Not sure why > adding to the path would cause this issue, but as soon as I remove it > all returns to a working order with stream mountpoints loading and > working perfectly...though now SSL is broken again :( Which source client do you use? If you switch the port to TLS that is used by the source client to connect you also need to set the source client to TLS mode. > Hopefully someone can provide some guidance here! Thanks! Please come back with the answers. I'm sure this isn't impossible. Have a good night! -- Philipp. (Rah of PH2) _______________________________________________ Icecast mailing list Icecast at xiph.org http://lists.xiph.org/mailman/listinfo/icecast -------------- next part -------------- An HTML attachment was scrubbed... URL: From nate at themillerhome.org Sat Apr 4 04:51:14 2015 From: nate at themillerhome.org (Nathan Miller) Date: Fri, 3 Apr 2015 21:51:14 -0700 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: <000501d06e89$170346d0$4509d470$@psrfm.org.au> References: <20150403224130.5927F12CF0@grassland.keep-cool.org> <000501d06e89$170346d0$4509d470$@psrfm.org.au> Message-ID: You can unsubscribe here http://lists.xiph.org/mailman/listinfo/icecast On Fri, Apr 3, 2015 at 8:40 PM, PSRFM Support wrote: > Can you remove these emails from going to my address please. > > > > *From:* icecast-bounces at xiph.org [mailto:icecast-bounces at xiph.org] *On > Behalf Of *Nathan Miller > *Sent:* Saturday, 4 April 2015 1:42 PM > *To:* Icecast streaming server user discussions > *Subject:* Re: [Icecast] After I enabled SSL, stream mountpoints broke > > > > Philipp, > > > > Thank you for your quick response. I can't believe that I didn't think of > that...I guess I just assumed that it would use SSL. I'm using Liquidsoap > as my source client. Once you brought that up I started researching > whether there was a way to force Liquidsoap to use SSL and from what I > found it doesn't look like there is an option...but please correct me if > you or anyone else who reads this knows differently. > > > > After I had a good idea of what was happening I found this other thread > http://lists.xiph.org/pipermail/icecast/2015-January/013118.html that > talks about exactly what I'm trying to do using Liquidsoap. I followed it > and I'm good now running on two ports...one SSL and one not from connecting > to Liquidsoap. > > > > Thanks again for your hint :) and please let me know if you've seen other > ways to tackle this with Liquidsoap than what I setup. > > > > Nathan > > > > On Fri, Apr 3, 2015 at 3:41 PM, Philipp Schafft > wrote: > > Good evening, > > On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote: > > I'm running Icecast package 2.4.1 on Ubuntu 14.04 > > from ttp://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04 > . > > > > > > I've been running on this server for about 6 months now without any > > issue and all my streams run great. This icecast server is running on > > the same host that my wordpress site is running on. This is all on my > > own private server, not a hosting service. > > > > > > Recently I decided to switch everything to SSL and all went well with > > the exception of the icecast server. The SSL portion of the icecast > > server is actually working just fine and the SSL certificate is > > loading on the admin page on all modern browsers without any issue or > > error. I can see the full admin page and navigate it without issue. > > The problem is as soon as I add this line to the section, as > > required to load the PEM certificate, my mountpoint streams stopped > > loading: > > > > > > > /usr/share/icecast2/ssl/mysslcertname.pem > > > > > > > > Then my icecast error log fills with this whenever anyone attempts to > > hit any of the stream mountpoints that failed to load: > > > > > > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for > > file /stream1 (/usr/share/icecast2/web/stream1) > > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file > > "/usr/share/icecast2/web/stream1" No such file or directory > > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for > > file /stream2 (/usr/share/icecast2/web/stream2) > > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file > > "/usr/share/icecast2/web/stream2" No such file or directory > > Those messages tell that there is no mount nor a file in web/. I suspect > that the stream is not mounted (= the source is not connected). > > > > There is nothing in the error logs after I've added this line to the > > and restarted icecast so I'm not sure what is breaking but I'm > > guessing from the errors whenever someone tries to hit the mountpoint > > that the file that was supposed to be created never is. Not sure why > > adding to the path would cause this issue, but as soon as I remove it > > all returns to a working order with stream mountpoints loading and > > working perfectly...though now SSL is broken again :( > > Which source client do you use? If you switch the port to TLS that is > used by the source client to connect you also need to set the source > client to TLS mode. > > > > Hopefully someone can provide some guidance here! Thanks! > > Please come back with the answers. I'm sure this isn't impossible. > > Have a good night! > > -- > Philipp. > (Rah of PH2) > > _______________________________________________ > 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: From thomas at ruecker.fi Sat Apr 4 05:50:59 2015 From: thomas at ruecker.fi (=?windows-1252?Q?=22Thomas_B=2E_R=FCcker=22?=) Date: Sat, 04 Apr 2015 05:50:59 +0000 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: References: <20150403224130.5927F12CF0@grassland.keep-cool.org> Message-ID: <551F7BC3.2020601@ruecker.fi> On 04/04/2015 02:42 AM, Nathan Miller wrote: > Philipp, > > Thank you for your quick response. I can't believe that I didn't > think of that...I guess I just assumed that it would use SSL. I'm > using Liquidsoap as my source client. Once you brought that up I > started researching whether there was a way to force Liquidsoap to use > SSL and from what I found it doesn't look like there is an > option...but please correct me if you or anyone else who reads this > knows differently. > > After I had a good idea of what was happening I found this other > thread http://lists.xiph.org/pipermail/icecast/2015-January/013118.html that > talks about exactly what I'm trying to do using Liquidsoap. I > followed it and I'm good now running on two ports...one SSL and one > not from connecting to Liquidsoap. > > Thanks again for your hint :) and please let me know if you've seen > other ways to tackle this with Liquidsoap than what I setup. If you read the remainder of that thread you pointed to, you'll find some hints. The main thing being to "ssl enable" the source connections by using Stunnel on the originating machine. This random picture from "the interwebz" explains it pretty well: http://www.ximera.de/bilder/stunnel2.png In place of "Hamster" you'd have your source client. I expect the TLS support situation to improve with source clients, as we are soon going to release a TLS enabled version of libshout. The library many clients use to talk to Icecast servers. In case one has only local connections from source clients, then just binding a plain http port to ::1 or 127.0.0.1 is safe too. Cheers Thomas > On Fri, Apr 3, 2015 at 3:41 PM, Philipp Schafft > wrote: > > Good evening, > > On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote: > > I'm running Icecast package 2.4.1 on Ubuntu 14.04 > > from > ttp://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04 . > > > > > > I've been running on this server for about 6 months now without any > > issue and all my streams run great. This icecast server is > running on > > the same host that my wordpress site is running on. This is all > on my > > own private server, not a hosting service. > > > > > > Recently I decided to switch everything to SSL and all went well > with > > the exception of the icecast server. The SSL portion of the icecast > > server is actually working just fine and the SSL certificate is > > loading on the admin page on all modern browsers without any > issue or > > error. I can see the full admin page and navigate it without issue. > > The problem is as soon as I add this line to the section, as > > required to load the PEM certificate, my mountpoint streams stopped > > loading: > > > > > > > /usr/share/icecast2/ssl/mysslcertname.pem > > > > > > > > Then my icecast error log fills with this whenever anyone > attempts to > > hit any of the stream mountpoints that failed to load: > > > > > > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking for > > file /stream1 (/usr/share/icecast2/web/stream1) > > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for file > > "/usr/share/icecast2/web/stream1" No such file or directory > > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking for > > file /stream2 (/usr/share/icecast2/web/stream2) > > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for file > > "/usr/share/icecast2/web/stream2" No such file or directory > > Those messages tell that there is no mount nor a file in web/. I > suspect > that the stream is not mounted (= the source is not connected). > > > > There is nothing in the error logs after I've added this line to the > > and restarted icecast so I'm not sure what is breaking > but I'm > > guessing from the errors whenever someone tries to hit the > mountpoint > > that the file that was supposed to be created never is. Not > sure why > > adding to the path would cause this issue, but as soon as I > remove it > > all returns to a working order with stream mountpoints loading and > > working perfectly...though now SSL is broken again :( > > Which source client do you use? If you switch the port to TLS that is > used by the source client to connect you also need to set the source > client to TLS mode. > > > > Hopefully someone can provide some guidance here! Thanks! > > Please come back with the answers. I'm sure this isn't impossible. > > Have a good night! > > -- > Philipp. > (Rah of PH2) > > _______________________________________________ > 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 nate at themillerhome.org Sat Apr 4 06:53:39 2015 From: nate at themillerhome.org (Nathan Miller) Date: Fri, 3 Apr 2015 23:53:39 -0700 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: <551F7BC3.2020601@ruecker.fi> References: <20150403224130.5927F12CF0@grassland.keep-cool.org> <551F7BC3.2020601@ruecker.fi> Message-ID: Thanks Thomas. I did see the stunnel option but I really had no need to put out that extra effort as my source lives on the same host as the icecast server. Just like you stated, since I'm pointing it at the localhost there really is no need to encrypt that stream. So I'm just running a secondary port that isn't publicly exposed as non-ssl. Thanks again, Nathan On Fri, Apr 3, 2015 at 10:50 PM, "Thomas B. R?cker" wrote: > On 04/04/2015 02:42 AM, Nathan Miller wrote: > > Philipp, > > > > Thank you for your quick response. I can't believe that I didn't > > think of that...I guess I just assumed that it would use SSL. I'm > > using Liquidsoap as my source client. Once you brought that up I > > started researching whether there was a way to force Liquidsoap to use > > SSL and from what I found it doesn't look like there is an > > option...but please correct me if you or anyone else who reads this > > knows differently. > > > > After I had a good idea of what was happening I found this other > > thread http://lists.xiph.org/pipermail/icecast/2015-January/013118.html > that > > talks about exactly what I'm trying to do using Liquidsoap. I > > followed it and I'm good now running on two ports...one SSL and one > > not from connecting to Liquidsoap. > > > > Thanks again for your hint :) and please let me know if you've seen > > other ways to tackle this with Liquidsoap than what I setup. > > If you read the remainder of that thread you pointed to, you'll find > some hints. > The main thing being to "ssl enable" the source connections by using > Stunnel on the originating machine. This random picture from "the > interwebz" explains it pretty well: > http://www.ximera.de/bilder/stunnel2.png > In place of "Hamster" you'd have your source client. > > I expect the TLS support situation to improve with source clients, as we > are soon going to release a TLS enabled version of libshout. The library > many clients use to talk to Icecast servers. > > In case one has only local connections from source clients, then just > binding a plain http port to ::1 or 127.0.0.1 is safe too. > > Cheers > > Thomas > > > > > On Fri, Apr 3, 2015 at 3:41 PM, Philipp Schafft > > wrote: > > > > Good evening, > > > > On Fri, 2015-04-03 at 14:02 -0700, Nathan Miller wrote: > > > I'm running Icecast package 2.4.1 on Ubuntu 14.04 > > > from > > ttp://download.opensuse.org/repositories/home:/dm8tbr/xUbuntu_14.04 > . > > > > > > > > > I've been running on this server for about 6 months now without any > > > issue and all my streams run great. This icecast server is > > running on > > > the same host that my wordpress site is running on. This is all > > on my > > > own private server, not a hosting service. > > > > > > > > > Recently I decided to switch everything to SSL and all went well > > with > > > the exception of the icecast server. The SSL portion of the > icecast > > > server is actually working just fine and the SSL certificate is > > > loading on the admin page on all modern browsers without any > > issue or > > > error. I can see the full admin page and navigate it without > issue. > > > The problem is as soon as I add this line to the section, > as > > > required to load the PEM certificate, my mountpoint streams stopped > > > loading: > > > > > > > > > > > > /usr/share/icecast2/ssl/mysslcertname.pem > > > > > > > > > > > > Then my icecast error log fills with this whenever anyone > > attempts to > > > hit any of the stream mountpoints that failed to load: > > > > > > > > > [2015-04-02 18:17:59] INFO fserve/fserve_client_create checking > for > > > file /stream1 (/usr/share/icecast2/web/stream1) > > > [2015-04-02 18:17:59] WARN fserve/fserve_client_create req for > file > > > "/usr/share/icecast2/web/stream1" No such file or directory > > > [2015-04-03 01:52:43] INFO fserve/fserve_client_create checking > for > > > file /stream2 (/usr/share/icecast2/web/stream2) > > > [2015-04-03 01:52:43] WARN fserve/fserve_client_create req for > file > > > "/usr/share/icecast2/web/stream2" No such file or directory > > > > Those messages tell that there is no mount nor a file in web/. I > > suspect > > that the stream is not mounted (= the source is not connected). > > > > > > > There is nothing in the error logs after I've added this line to > the > > > and restarted icecast so I'm not sure what is breaking > > but I'm > > > guessing from the errors whenever someone tries to hit the > > mountpoint > > > that the file that was supposed to be created never is. Not > > sure why > > > adding to the path would cause this issue, but as soon as I > > remove it > > > all returns to a working order with stream mountpoints loading and > > > working perfectly...though now SSL is broken again :( > > > > Which source client do you use? If you switch the port to TLS that is > > used by the source client to connect you also need to set the source > > client to TLS mode. > > > > > > > Hopefully someone can provide some guidance here! Thanks! > > > > Please come back with the answers. I'm sure this isn't impossible. > > > > Have a good night! > > > > -- > > Philipp. > > (Rah of PH2) > > > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > > > > > > > > > > _______________________________________________ > > Icecast mailing list > > Icecast at xiph.org > > http://lists.xiph.org/mailman/listinfo/icecast > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From lion at lion.leolix.org Sat Apr 4 08:41:23 2015 From: lion at lion.leolix.org (Philipp Schafft) Date: Sat, 04 Apr 2015 08:41:23 +0000 Subject: [Icecast] After I enabled SSL, stream mountpoints broke In-Reply-To: <551F7BC3.2020601@ruecker.fi> References: <20150403224130.5927F12CF0@grassland.keep-cool.org> <551F7BC3.2020601@ruecker.fi> Message-ID: <20150404084126.894CC12CF0@grassland.keep-cool.org> Good morning, On Sat, 2015-04-04 at 05:50 +0000, "Thomas B. R?cker" wrote: > I expect the TLS support situation to improve with source clients, as > we > are soon going to release a TLS enabled version of libshout. The > library > many clients use to talk to Icecast servers. I would like to comment that further: With current (trunk/git master) libshout default mode is to autodetect TLS mode. So if you have a current libshout's binary installed and run a non-TLS aware source client it will automagically support TLS. There are currently two limits here: * There was no stable release since this was added. We are currently working on releasing soon^{TM}. * ON a non-TLS aware application there is no way to tune the TLS settings (of cause). So you *need* to get certificates right. > In case one has only local connections from source clients, then just > binding a plain http port to ::1 or 127.0.0.1 is safe too. tbr, I still think of my suggestion years ago to add support for UNIX Domain sockets for local connections. More performance (many times faster than IPv4 Stack and even more than IPv6 stack.), more security (you can just use all the normal UNIX file permission stuff). -- Philipp. (Rah of PH2) -------------- 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: From xoneca+icecast at gmail.com Mon Apr 6 15:47:38 2015 From: xoneca+icecast at gmail.com (Xabier Oneca -- xOneca) Date: Mon, 6 Apr 2015 17:47:38 +0200 Subject: [Icecast] Icecast won't start on system boot In-Reply-To: <23oqhap33h3lt3fjsa7d9bklu8fkg4oqn4@4ax.com> References: <8b98hadgtr12f2l1hi4i8o7gfofb25l386@4ax.com> <55143451.6050006@ruecker.fi> <55146D8D.3040308@ruecker.fi> <55178C06.6060303@ruecker.fi> <23oqhap33h3lt3fjsa7d9bklu8fkg4oqn4@4ax.com> Message-ID: Hello Steve! 2015-04-02 17:32 GMT+02:00 Steve Matzura : > Ya know, there are none so blind ... IT'S BEEN COMMENTED OUT! > > > 0 > > That's why I always use an editor with *syntax highlighting* :) Cheers, Xabier Oneca_,,_ From thomas at ruecker.fi Tue Apr 7 11:19:28 2015 From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=) Date: Tue, 07 Apr 2015 11:19:28 +0000 Subject: [Icecast] Event Triggers on 2.5 beta1 In-Reply-To: References: <9556E5AE-FE80-479C-BAB7-AD57DD2D0081@dadi.co> <4B415AEE-7601-48D2-AA28-ADEF7D7AF93B@gmail.com> <550839B0.9080208@ruecker.fi> <8972BDFB-3F3A-4877-9752-B07692CD2590@dadi.co> <550927BF.5070808@ruecker.fi> Message-ID: <5523BD40.90404@ruecker.fi> On 03/18/2015 07:41 AM, Robert Stanford wrote: >> Icecast streams don't have a notion of "pause", what do you mean by that? >> >> Cheers >> >> Thomas > I?m trying to trigger a URL event so that I can log listener statistics using an API. > I?m currently using listener authentication to track listener_add and listener_remove, > but using this method I seem to get a lot of spurious entries. So I wondered if events > would offer a more reliable way to track when a listener is actually playing a stream? Hmm, not so sure. Haven't run this for quite a while on a production system. There may be lots of noise due to clients making several requests to figure things out before then staying connected. Filtering for duration might help here. Any particular problems you're having? To answer your other question, currently we only define two event triggers: source-connect source-disconnect In the near future we'll be adding more. Please join the discussion here: https://trac.xiph.org/ticket/2189#ticket Cheers Thomas From sm at noisynotes.com Tue Apr 7 23:29:33 2015 From: sm at noisynotes.com (Steve Matzura) Date: Tue, 07 Apr 2015 19:29:33 -0400 Subject: [Icecast] Icecast won't start on system boot In-Reply-To: References: <8b98hadgtr12f2l1hi4i8o7gfofb25l386@4ax.com> <55143451.6050006@ruecker.fi> <55146D8D.3040308@ruecker.fi> <55178C06.6060303@ruecker.fi> <23oqhap33h3lt3fjsa7d9bklu8fkg4oqn4@4ax.com> Message-ID: On Mon, 6 Apr 2015 17:47:38 +0200, you wrote: >Hello Steve! > >2015-04-02 17:32 GMT+02:00 Steve Matzura : >> Ya know, there are none so blind ... IT'S BEEN COMMENTED OUT! >> >> >> 0 >> >> > >That's why I always use an editor with *syntax highlighting* :) Well that's a good idea in theory, but it couldn't possibly be highlighted enough to help me because I'm totally blind. No worries though. Just have to pay better attention to what my screenreader is (or, in this case, isn't) telling me. From thomas at ruecker.fi Wed Apr 8 12:52:37 2015 From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=) Date: Wed, 08 Apr 2015 12:52:37 +0000 Subject: [Icecast] Icecast 2.4.2 - security release Message-ID: <55252495.1000805@ruecker.fi> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Today we became aware of a bug in the Icecast code handling source client URL-authentication and are releasing a security fix. The bug was discovered by Juliane Holzt, who we'd like to thank for bringing this to our attention and providing us with further details. Affected Icecast versions: 2.3.3(first release with stream_auth) 2.4.0 2.4.1 Fix released in: 2.4.2 We do not release fixes for: 2.3.3: EOL 2.4.0: as 2.4.1 was a bugfix release for 2.4.0. The bug can only be triggered if "stream_auth" is being used, for example: /test.ogg This means, that all installations that use a default configuration are NOT affected.The default configuration only uses . Neither are simple mountpoints affected that use . A workaround, if installing an updated package is not possible, is to disable "stream_auth"and use instead. As far as we understand the bug only leads to a simple remote denial of service. The underlying issue is a null pointer dereference. For clarity: No remote code execution should be possible, server just segfaults. Proof of concept: curl "http://example.org:8000/admin/killsource?mount=/test.ogg" If the server is configured as above, then it will segfault.A source client does not need to be connected to that mount point. As Juliane points out: "This only happens when making a request WITHOUT login credentials." This means, that sadly exploiting this does not require any authentication, just the knowledge of a mount point configured with stream_auth. Original Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782120 Xiph.org ticket: https://trac.xiph.org/ticket/2191 Sources: http://downloads.xiph.org/releases/icecast/icecast-2.4.2.tar.gz SHA256 aa1ae2fa364454ccec61a9247949d19959cb0ce1b044a79151bf8657fd673f4f git-tag: release-2.4.2 As usual there are up to date packages available for most mainstream distributions. We've moved from my personal project to an official Xiph.org project on openSUSE OBS: https://build.opensuse.org/package/show/multimedia:xiph/icecast Individual repositories are here: A copy of the openSUSE OBS multimedia signing key is here: http://icecast.org/multimedia-obs.key The Windows version will be updated later today. Known issues (as in 2.4.1) * status-json.xsl format differs if one source client is connected and if more than one client is connected. Workaround: e.g. connect dummy source(s). * HTTP PUT implementation currently doesn?t support chunked encoding yet. * HTTP PUT with ?Expect: 100-Continue? receives first a ?100? and soon after a ?200?, instead of the ?200? at end of transmission. * Caution should be exercised when using or , as there is a small chance of stream file descriptors being mixed up with script file descriptors, if the FD numbers go above 1024. This will be further addressed in the next Icecast release. * Don?t use comments inside as it will prevent processing of further
tags. * Web interface shows Login when using just stream_auth. We are requesting a CVE ID through oss-security and I will update the ticket once we have received it. Thomas Ruecker Icecast maintainer PS: The OBS package builds are somewhat slow today, so it might still take a while until the last updated packages have been published to the repositories. I didn't want to delay the release announcement further. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iEYEARECAAYFAlUlJJQACgkQfkVKO9VkYGmWPACfUDcWmK5T6TFV4Q1f9+RZOcDr vj4An1CBPF2AntVl0jxUfCCBHD7wNcEy =jRys -----END PGP SIGNATURE----- From thomas at ruecker.fi Wed Apr 8 14:17:20 2015 From: thomas at ruecker.fi (=?UTF-8?B?IlRob21hcyBCLiBSw7xja2VyIg==?=) Date: Wed, 08 Apr 2015 14:17:20 +0000 Subject: [Icecast] [Icecast-dev] Icecast 2.4.2 - security release In-Reply-To: <55252495.1000805@ruecker.fi> References: <55252495.1000805@ruecker.fi> Message-ID: <55253870.6090702@ruecker.fi> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 [Resending, as Thunderbird/Enigmail broke the GPG signature] Today we became aware of a bug in the Icecast code handling source client URL-authentication and are releasing a security fix. The bug was discovered by Juliane Holzt, who we'd like to thank for bringing this to our attention and providing us with further details. Affected Icecast versions: 2.3.3(first release with stream_auth) 2.4.0 2.4.1 Fix released in: 2.4.2 We do not release fixes for: 2.3.3: EOL 2.4.0: as 2.4.1 was a bugfix release for 2.4.0. The bug can only be triggered if "stream_auth" is being used, for example: /test.ogg This means, that all installations that use a default configuration are NOT affected.The default configuration only uses . Neither are simple mountpoints affected that use . A workaround, if installing an updated package is not possible, is to disable "stream_auth"and use instead. As far as we understand the bug only leads to a simple remote denial of service. The underlying issue is a null pointer dereference. For clarity: No remote code execution should be possible, server just segfaults. Proof of concept: curl "http://example.org:8000/admin/killsource?mount=/test.ogg" If the server is configured as above, then it will segfault.A source client does not need to be connected to that mount point. As Juliane points out: "This only happens when making a request WITHOUT login credentials." This means, that sadly exploiting this does not require any authentication, just the knowledge of a mount point configured with stream_auth. Original Debian bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=782120 Xiph.org ticket: https://trac.xiph.org/ticket/2191 Sources: http://downloads.xiph.org/releases/icecast/icecast-2.4.2.tar.gz SHA256 aa1ae2fa364454ccec61a9247949d19959cb0ce1b044a79151bf8657fd673f4f git-tag: release-2.4.2 As usual there are up to date packages available for most mainstream distributions. We've moved from my personal project to an official Xiph.org project on openSUSE OBS: https://build.opensuse.org/package/show/multimedia:xiph/icecast Individual repositories are here: A copy of the openSUSE OBS multimedia signing key is here: http://icecast.org/multimedia-obs.key The Windows version will be updated later today. Known issues (as in 2.4.1) * status-json.xsl format differs if one source client is connected and if more than one client is connected. Workaround: e.g. connect dummy source(s). * HTTP PUT implementation currently doesn?support chunked encoding yet. * HTTP PUT with ?pect: 100-Continue?eceives first a ?0?nd soon after a ?0?instead of the ?0?t end of transmission. * Caution should be exercised when using or , as there is a small chance of stream file descriptors being mixed up with script file descriptors, if the FD numbers go above 1024. This will be further addressed in the next Icecast release. * Don?use comments inside as it will prevent processing of further
tags. * Web interface shows Login when using just stream_auth. We are requesting a CVE ID through oss-security and I will update the ticket once we have received it. Thomas Ruecker Icecast maintainer PS: The OBS package builds are somewhat slow today, so it might still take a while until the last updated packages have been published to the repositories. I didn't want to delay the release announcement further. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlUlOEQACgkQfkVKO9VkYGnuQQCeKicLiXFvqnsTmq/OaIP90SSD qIcAnjxqla+vSbnRGb3ouQyQBPmTBkcl =OAVW -----END PGP SIGNATURE----- From xoneca+icecast at gmail.com Fri Apr 10 12:08:24 2015 From: xoneca+icecast at gmail.com (Xabier Oneca -- xOneca) Date: Fri, 10 Apr 2015 14:08:24 +0200 Subject: [Icecast] Icecast won't start on system boot In-Reply-To: References: <8b98hadgtr12f2l1hi4i8o7gfofb25l386@4ax.com> <55143451.6050006@ruecker.fi> <55146D8D.3040308@ruecker.fi> <55178C06.6060303@ruecker.fi> <23oqhap33h3lt3fjsa7d9bklu8fkg4oqn4@4ax.com> Message-ID: 2015-04-08 1:29 GMT+02:00 Steve Matzura : > On Mon, 6 Apr 2015 17:47:38 +0200, you wrote: > >>Hello Steve! >> >>2015-04-02 17:32 GMT+02:00 Steve Matzura : >>> Ya know, there are none so blind ... IT'S BEEN COMMENTED OUT! >>> >>> >>> 0 >>> >>> >> >>That's why I always use an editor with *syntax highlighting* :) > > Well that's a good idea in theory, but it couldn't possibly be > highlighted enough to help me because I'm totally blind. Oh, my apologies! It didn't sound to me like you were *literally* blind... /me goes to the corner of the shame and keeps silent > No worries > though. Just have to pay better attention to what my screenreader is > (or, in this case, isn't) telling me. Cheers, Xabier Oneca_,,_ From lion at lion.leolix.org Sat Apr 11 07:03:16 2015 From: lion at lion.leolix.org (Philipp Schafft) Date: Sat, 11 Apr 2015 07:03:16 +0000 Subject: [Icecast] Check feed connected, active - IceCast 2.4.x In-Reply-To: References: Message-ID: <20150411070319.4636612CF0@grassland.keep-cool.org> Good morning, On Fri, 2015-04-10 at 23:41 +0000, Dean Sauer wrote: > After a situation arose, I am looking to put a little script to monitor > my IceCast server to make sure IceCast is up and running, and the feeds > connected... obviously not a verification of audio, yet, but at least the > source is sending data to the IceCast server. > > I can check that IceCast is running doing a simple: > > response_code = urllib.urlopen("http:/server:8000").getcode() Two slashes missing. > If I get a 200, IceCast is up/running. > > For feeds what would be the best URL to check and the response? > > NOTE: Feeds if THE SOURCE is NOT SENDING, FAIL OVER to a fail over > mount!! > > So taking this caveat into consideration for the above. So if I check > xyz.url:8000 it should come back 500 or something that its down and on > the failover mount... You can request /admin/stats.xml. That file will return the overall server status including per source information. If the server returns 200 with the expected XML document the server is up and running. You can look at the tags to find out if the sources are connected. -- Philipp. (Rah of PH2) -------------- 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: From marius at flage.org Sun Apr 12 13:38:16 2015 From: marius at flage.org (Marius Flage) Date: Sun, 12 Apr 2015 15:38:16 +0200 Subject: [Icecast] IceCast LIVE stats??? In-Reply-To: References: Message-ID: <552A7548.9020508@flage.org> We have implemented this as such: http://narkanalen.no/lyttere This is done by POST-ing to a web page every time a user connects/disconnects. All values are posted to a database. If you try connecting, you should see yourself appearing in the map pretty quickly. - Marius Den 11.04.2015 01:36, skrev Dean Sauer: > I am looking to find something that can be used to do LIVE STATS for > IceCast 2.4.x? > > Mainly listener counts on feeds. > > AWSTATS et al seem to all be ex post facto stat viewers.... not what I am > after. Numerous other stats viewers are nothing more than text counts... > meh.. not what I am after. Something with some "pretty graphics" to watch > LIVE... > > Must run on Kubuntu 12.04 or 14.04, server or client side. > > Any one doing this???? > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast From davekm3t at gmail.com Mon Apr 13 01:26:13 2015 From: davekm3t at gmail.com (Dave Pascoe) Date: Sun, 12 Apr 2015 21:26:13 -0400 Subject: [Icecast] Check feed connected, active - IceCast 2.4.x In-Reply-To: References: <20150411070319.4636612CF0@grassland.keep-cool.org> Message-ID: There is a plugin for Nagios called check_ice that you can also just compile and run standalone. See: https://github.com/pozar/check_ice On Sun, Apr 12, 2015 at 7:50 PM, Dean Sauer wrote: > On Sat, 11 Apr 2015 07:03:16 +0000, Philipp Schafft wrote: > > > You can request /admin/stats.xml. That file will return the overall > > server status including per source information. If the server returns > > 200 with the expected XML document the server is up and running. > > Thanks, my pseudo code already determined that and the underlying issue. > > If I query the server on port 8000 and get 200, then its up/running... > > Now the sources... > > > > You can > > look at the tags to find out if the sources are connected. > > Thanks, but no I am not scraping/parsing that. I despise the whole > concept of "scraping" sites like this, there is already one piece of > software doing this as it is in my arena. > > doing a: > > urllib.urlopen("http://domain/source").getcode() > > just returns a 200 even if the actual source is down, and the source is > on a fall back. If I were following http expectations I should get 302, > temp redirection as used widely, or 307 if you stick to the strict > standard. > > Sadly right now the simple check that IceCast is UP will have to suffice, > and covers the main problem, right now. > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > -------------- next part -------------- An HTML attachment was scrubbed... URL: From cdgraff at gmail.com Mon Apr 13 01:55:45 2015 From: cdgraff at gmail.com (Alejandro) Date: Sun, 12 Apr 2015 22:55:45 -0300 Subject: [Icecast] Check feed connected, active - IceCast 2.4.x In-Reply-To: References: <20150411070319.4636612CF0@grassland.keep-cool.org> Message-ID: Here can take a look other alternative: https://github.com/cdgraff/icecast-mon We base our solution in avprobe/ffprobe, this test like a real listener. Feedback is welcome! this is just first release, but we use on production. Regards, Alejandro 2015-04-12 22:26 GMT-03:00 Dave Pascoe : > There is a plugin for Nagios called check_ice that you can also just > compile and run standalone. > > See: https://github.com/pozar/check_ice > > > On Sun, Apr 12, 2015 at 7:50 PM, Dean Sauer > wrote: > >> On Sat, 11 Apr 2015 07:03:16 +0000, Philipp Schafft wrote: >> >> > You can request /admin/stats.xml. That file will return the overall >> > server status including per source information. If the server returns >> > 200 with the expected XML document the server is up and running. >> >> Thanks, my pseudo code already determined that and the underlying issue. >> >> If I query the server on port 8000 and get 200, then its up/running... >> >> Now the sources... >> >> >> > You can >> > look at the tags to find out if the sources are connected. >> >> Thanks, but no I am not scraping/parsing that. I despise the whole >> concept of "scraping" sites like this, there is already one piece of >> software doing this as it is in my arena. >> >> doing a: >> >> urllib.urlopen("http://domain/source").getcode() >> >> just returns a 200 even if the actual source is down, and the source is >> on a fall back. If I were following http expectations I should get 302, >> temp redirection as used widely, or 307 if you stick to the strict >> standard. >> >> Sadly right now the simple check that IceCast is UP will have to suffice, >> and covers the main problem, right now. >> >> _______________________________________________ >> 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: From lion at lion.leolix.org Mon Apr 13 06:47:06 2015 From: lion at lion.leolix.org (Philipp Schafft) Date: Mon, 13 Apr 2015 06:47:06 +0000 Subject: [Icecast] Check feed connected, active - IceCast 2.4.x In-Reply-To: References: <20150411070319.4636612CF0@grassland.keep-cool.org> Message-ID: <20150413064712.3B22812CF0@grassland.keep-cool.org> reflum, On Sun, 2015-04-12 at 23:50 +0000, Dean Sauer wrote: > On Sat, 11 Apr 2015 07:03:16 +0000, Philipp Schafft wrote: > > > You can request /admin/stats.xml. That file will return the overall > > server status including per source information. If the server returns > > 200 with the expected XML document the server is up and running. > > Thanks, my pseudo code already determined that and the underlying issue. > > If I query the server on port 8000 and get 200, then its up/running... > > Now the sources... > > > > You can > > look at the tags to find out if the sources are connected. > > Thanks, but no I am not scraping/parsing that. I despise the whole > concept of "scraping" sites like this, there is already one piece of > software doing this as it is in my arena. I think you misunderstood me. the admin/stats.xml file *is* the API interface. It's for usage such as yours. within /admin: stuff ending with .xsl is for non-API, stuff with no dot in the name or ending in .xml are for API usage. What you will get is a well formed XML document. Have a look at it! > doing a: > > urllib.urlopen("http://domain/source").getcode() > > just returns a 200 even if the actual source is down, and the source is > on a fall back. If I were following http expectations I should get 302, > temp redirection as used widely, or 307 if you stick to the strict > standard. No. I think you are misunderstanding the standard here: Icecast is *not* refusing to serve the resource. So it MUST return a 2xx-status code. The fallback isn't happening in the protocol layer. (This is because there are no mid-of-stream redirects on HTTP. So redirects (3xx) can't work for users already connected.) > Sadly right now the simple check that IceCast is UP will have to suffice, > and covers the main problem, right now. Again, see my hints on the admin/stats.xml file. It contains all the data you want. -- Philipp. (Rah of PH2) -------------- 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: From lion at lion.leolix.org Mon Apr 13 07:55:51 2015 From: lion at lion.leolix.org (Philipp Schafft) Date: Mon, 13 Apr 2015 07:55:51 +0000 Subject: [Icecast] Check feed connected, active - IceCast 2.4.x In-Reply-To: References: <20150411070319.4636612CF0@grassland.keep-cool.org> Message-ID: <20150413075554.5460012CF0@grassland.keep-cool.org> reflum, On Sun, 2015-04-12 at 22:55 -0300, Alejandro wrote: > Here can take a look other > alternative: https://github.com/cdgraff/icecast-mon Thank you for sharing! > We base our solution in avprobe/ffprobe, this test like a real > listener. > > > Feedback is welcome! this is just first release, but we use on > production. Have a little bit of feedback. :) in icecast_mon.py:80 you construct a string with an URL embedded. in icecast_mon.py:83 you split it again. I think you would be better off by constructing an array directly. The current implementation may be prone to errors based on meta characters in the URL. (This isn't super unlikely. Already had a similar case on a Icecast setup myself where mount points contained such special characters.) Thank you for your work! -- Philipp. (Rah of PH2) -------------- 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: From david at sojournmusic.net Wed Apr 22 19:52:05 2015 From: david at sojournmusic.net (David Martinez) Date: Wed, 22 Apr 2015 12:52:05 -0700 Subject: [Icecast] Lossless stream from MPD... Message-ID: Any way to setup a lossless stream from MPD? I know MPD can encode FLAC, but I don't know if Icecast can handle it. Any other lossless options? -------------- next part -------------- An HTML attachment was scrubbed... URL: From erm13martinez at gmail.com Wed Apr 22 20:10:10 2015 From: erm13martinez at gmail.com (Eduardo Martinez) Date: Wed, 22 Apr 2015 13:10:10 -0700 Subject: [Icecast] Lossless stream from MPD... In-Reply-To: References: Message-ID: Icecast can definitly handle OggFLAC. I usually use liquidsoap to stream flac to icecast. On Apr 22, 2015 12:52 PM, "David Martinez" wrote: > Any way to setup a lossless stream from MPD? I know MPD can encode FLAC, > but I don't know if Icecast can handle it. Any other lossless options? > > > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at sojournmusic.net Wed Apr 22 20:17:12 2015 From: david at sojournmusic.net (David Martinez) Date: Wed, 22 Apr 2015 13:17:12 -0700 Subject: [Icecast] Lossless stream from MPD... In-Reply-To: References: Message-ID: I am not familular with liquidsoap. Is it something I can use with MPD? On Wed, Apr 22, 2015 at 1:10 PM, Eduardo Martinez wrote: > Icecast can definitly handle OggFLAC. I usually use liquidsoap to stream > flac to icecast. > On Apr 22, 2015 12:52 PM, "David Martinez" wrote: > >> Any way to setup a lossless stream from MPD? I know MPD can encode FLAC, >> but I don't know if Icecast can handle it. Any other lossless options? >> >> >> >> _______________________________________________ >> 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: From erm13martinez at gmail.com Wed Apr 22 20:22:24 2015 From: erm13martinez at gmail.com (Eduardo Martinez) Date: Wed, 22 Apr 2015 13:22:24 -0700 Subject: [Icecast] Lossless stream from MPD... In-Reply-To: References: Message-ID: Liquidsoap is another encoder simular to ices or MPD. Liquidsoap doesn't work directly with MPD. On Apr 22, 2015 1:17 PM, "David Martinez" wrote: > I am not familular with liquidsoap. Is it something I can use with MPD? > > > > On Wed, Apr 22, 2015 at 1:10 PM, Eduardo Martinez > wrote: > >> Icecast can definitly handle OggFLAC. I usually use liquidsoap to stream >> flac to icecast. >> On Apr 22, 2015 12:52 PM, "David Martinez" >> wrote: >> >>> Any way to setup a lossless stream from MPD? I know MPD can encode FLAC, >>> but I don't know if Icecast can handle it. Any other lossless options? >>> >>> >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >>> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> >> > > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at sojournmusic.net Wed Apr 22 20:35:45 2015 From: david at sojournmusic.net (David Martinez) Date: Wed, 22 Apr 2015 13:35:45 -0700 Subject: [Icecast] Lossless stream from MPD... In-Reply-To: References: Message-ID: Will this work? # Stream it out output.icecast(%flac, host = "localhost", port = 8000, password = "hackme", mount = "basic-radio.flac", radio) On Apr 22, 2015 1:22 PM, "Eduardo Martinez" wrote: > Liquidsoap is another encoder simular to ices or MPD. Liquidsoap doesn't > work directly with MPD. > On Apr 22, 2015 1:17 PM, "David Martinez" wrote: > >> I am not familular with liquidsoap. Is it something I can use with MPD? >> >> >> >> On Wed, Apr 22, 2015 at 1:10 PM, Eduardo Martinez < >> erm13martinez at gmail.com> wrote: >> >>> Icecast can definitly handle OggFLAC. I usually use liquidsoap to stream >>> flac to icecast. >>> On Apr 22, 2015 12:52 PM, "David Martinez" >>> wrote: >>> >>>> Any way to setup a lossless stream from MPD? I know MPD can encode >>>> FLAC, but I don't know if Icecast can handle it. Any other lossless options? >>>> >>>> >>>> >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >>>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >>> >> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From erm13martinez at gmail.com Wed Apr 22 20:38:27 2015 From: erm13martinez at gmail.com (Eduardo Martinez) Date: Wed, 22 Apr 2015 13:38:27 -0700 Subject: [Icecast] Lossless stream from MPD... In-Reply-To: References: Message-ID: You first have to define source to point to your directory of flac files. On Apr 22, 2015 1:36 PM, "David Martinez" wrote: > Will this work? > > # Stream it out output.icecast(%flac, host = "localhost", port = 8000, > password = "hackme", mount = "basic-radio.flac", radio) > On Apr 22, 2015 1:22 PM, "Eduardo Martinez" > wrote: > >> Liquidsoap is another encoder simular to ices or MPD. Liquidsoap doesn't >> work directly with MPD. >> On Apr 22, 2015 1:17 PM, "David Martinez" wrote: >> >>> I am not familular with liquidsoap. Is it something I can use with MPD? >>> >>> >>> >>> On Wed, Apr 22, 2015 at 1:10 PM, Eduardo Martinez < >>> erm13martinez at gmail.com> wrote: >>> >>>> Icecast can definitly handle OggFLAC. I usually use liquidsoap to >>>> stream flac to icecast. >>>> On Apr 22, 2015 12:52 PM, "David Martinez" >>>> wrote: >>>> >>>>> Any way to setup a lossless stream from MPD? I know MPD can encode >>>>> FLAC, but I don't know if Icecast can handle it. Any other lossless options? >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> Icecast mailing list >>>>> Icecast at xiph.org >>>>> http://lists.xiph.org/mailman/listinfo/icecast >>>>> >>>>> >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >>>> >>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >>> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From david at sojournmusic.net Wed Apr 22 20:43:17 2015 From: david at sojournmusic.net (David Martinez) Date: Wed, 22 Apr 2015 13:43:17 -0700 Subject: [Icecast] Lossless stream from MPD... In-Reply-To: References: Message-ID: Peaking at the documentation, can I simply input from ALSA and output to a stream? On Wed, Apr 22, 2015 at 1:38 PM, Eduardo Martinez wrote: > You first have to define source to point to your directory of flac files. > On Apr 22, 2015 1:36 PM, "David Martinez" wrote: > >> Will this work? >> >> # Stream it out output.icecast(%flac, host = "localhost", port = 8000, >> password = "hackme", mount = "basic-radio.flac", radio) >> On Apr 22, 2015 1:22 PM, "Eduardo Martinez" >> wrote: >> >>> Liquidsoap is another encoder simular to ices or MPD. Liquidsoap doesn't >>> work directly with MPD. >>> On Apr 22, 2015 1:17 PM, "David Martinez" >>> wrote: >>> >>>> I am not familular with liquidsoap. Is it something I can use with MPD? >>>> >>>> >>>> >>>> On Wed, Apr 22, 2015 at 1:10 PM, Eduardo Martinez < >>>> erm13martinez at gmail.com> wrote: >>>> >>>>> Icecast can definitly handle OggFLAC. I usually use liquidsoap to >>>>> stream flac to icecast. >>>>> On Apr 22, 2015 12:52 PM, "David Martinez" >>>>> wrote: >>>>> >>>>>> Any way to setup a lossless stream from MPD? I know MPD can encode >>>>>> FLAC, but I don't know if Icecast can handle it. Any other lossless options? >>>>>> >>>>>> >>>>>> >>>>>> _______________________________________________ >>>>>> Icecast mailing list >>>>>> Icecast at xiph.org >>>>>> http://lists.xiph.org/mailman/listinfo/icecast >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Icecast mailing list >>>>> Icecast at xiph.org >>>>> http://lists.xiph.org/mailman/listinfo/icecast >>>>> >>>>> >>>> >>>> _______________________________________________ >>>> Icecast mailing list >>>> Icecast at xiph.org >>>> http://lists.xiph.org/mailman/listinfo/icecast >>>> >>>> >>> _______________________________________________ >>> Icecast mailing list >>> Icecast at xiph.org >>> http://lists.xiph.org/mailman/listinfo/icecast >>> >>> >> _______________________________________________ >> Icecast mailing list >> Icecast at xiph.org >> http://lists.xiph.org/mailman/listinfo/icecast >> >> > _______________________________________________ > Icecast mailing list > Icecast at xiph.org > http://lists.xiph.org/mailman/listinfo/icecast > > -------------- next part -------------- An HTML attachment was scrubbed... URL: