similar to: Pyhton Class/library for Icecast 2.32 Stats and other info access?

Hi, if i am not mistaken 2.4 has a servlet which provides json output for active mounts and stats. You can check it out at http://your host:8000/status-json.xsl Just upgrade your version and you should be fine. Hth In a search for access to various ways to interact with Icecast via Python, I ran across this: http://xiph.org/~brendan/pyshout2/pyshout2-0.0.1.tar.gz Which is now dead (404). I

Hello, On 08-03-18 05:54, ScanCaster wrote: > Is there some simple way to get just the listener count on mounts out of > IceCast, specifically 2.4.1 > > Via BASH preferred, or CLI php if I must, I guess python 2.x would be an > option too. (3.x is not an option though!) > > All the stuff I've seen is scrapping things from the status.xsl, which is > bad form. Well,

just parse status-json.xsl with php's curl/json_parse... ScanCaster: > On Mon, 12 Mar 2018 22:07:34 +0100, Jeroen van Oosten wrote: > > > Well, you can create your own XSL with less data. I use this (as > > web/simple.xsl): > > Well since I don't know XSL, BASH etc. was my go to choice... > > BUT... > > Doing this gets > 404's from a

Hello, On 06-12-15 13:58, Yahav Shasha wrote: > > >To me it sounds like a bug; surely the fallback never needs > statistics, > only the real steam because this is where listeners connect to. > > > Well, the fallback mount is still a mount-point nonetheless. you could > still use it as a "regular" mount-point even if its configured as a >

I got the following script from this mailing list but when i try using it doesnt really seem to work and gives me the following error. Warning: fopen(http://...@64.157.204.179:9095/admin/stats): failed to open stream: Bad file descriptor in E:\Public ftp\epakimusic\test.php on line 9 Error reading Icecast data from 64.157.204.179:9095. So could someone please help me out with this.. or if

ok well i uploaded at a webhosting and no errors are there but it aint displaying any stats.... listeners are currently connected. Currently playing: nothing is displayed with it... wht could possibly be wrong now? must be some settings of the encoder or icecast.. btw i am using winamp and sam plugin also tried it with sam broadcaster.. the one with encoder nd player ... ----- Original Message

Thank you Philipp. I'm running icecast 2.4.2 and based on the "Available Raw Data" in the Icecast docs page (http://icecast.org/docs/ icecast-2.4.0/server-stats.html), it doesn't appear "album" or "year" are available for the stats-json.xsl file to get. But it may be misunderstanding what I'm seeing and just don't know how to properly customize the

I've been trying to track down this mysterious 'icestats' file that the status.xsl and status2.xsl read data from. There is no physical file as far as I can tell, but a perusal of the code seems to indicate that the server generates it on the fly when the XSL file requests it. So then I tried servername.com:8000/icestats but I got nothing. So I really got nothing, I would prefer

Hi Reaz, IP Address != Location of user in many cases. Think VPNs for instance. Of course if you're set on going that route, I'm pretty sure that status-json.xsl (in your webroot) has the IP address option simply added to a section that does not show it: <xsl:template match="icestats/source/source_ip"><xsl:if

Hello, I've upgraded from 2.3.1 to 2.3.2. I've been used to list all mount points by <xsl:for-each select="source"/> under /icestats. Howver now the /icestats elemets contains only source elemets which have been requested at least once. That means the list (e.g. /stats.xsl under web directory) is empty after server start. I've found out this regresion presents only

Hello Jordan Thanks for the reply.  I commented out all the fields in the status-json.xsl but it didn't give me the listener IP.  The example below would show me the source IP.  I can get the IP from the web interface at this location, http://xxx.xxx.xxx.xxx:8000/admin/listclients.xsl?mount=/dhantal, but that means I would have to scrape the web interface which I don't want to do.

Too much work. If I am able to see it on the web interface I should be able to get a Json or XML file with this in it. The reason I need this is to show current listeners and from where they are listening. I do this with the other streaming software without any modifications or adjustments. This should be easy. Reaz > On Sep 22, 2020, at 11:16 AM, <jorr at streamguys.com> <jorr at

M Edwards <medwards@ualberta.ca> said: > I've been trying to track down this mysterious 'icestats' file that the > status.xsl and status2.xsl read data from. There is no physical file as far as > I can tell, but a perusal of the code seems to indicate that the server > generates it on the fly when the XSL file requests it. So then I tried >

On Thursday 22 July 2004 04:56, Myke Place wrote: > I'm curious if it is possible to create custom .xsl files in the /admin > directory, using the same xsl params that appear in in the web > interfaces that ship with Icecast2. Yes. Though I don't know if using an arbitrary one works from the admin directory. Certainly you can put them in icecast's webroot directory (or some

Hello Thanks for the replies. I apologize for the rash statements but, not an excuse but an explanation, I was working for about a week and a half to get this to work without any success. Checked every post related to Icecast and read the manuals but nothing came up to resolve this. I did try try to remove the xsl from the site but that just gave me a 400 unknown admin request error. I also

What about scrapping the access logs for connections that have completed, or utilizing netstat outputs to get active listeners (minus sources)? Either of those options would get you remote IP addresses, both a slightly different view in that logs are after a connection closes, while netstat is while the connection is open. -----Original Message----- From: Icecast-dev <icecast-dev-bounces at

I think I got it. I needed to change the following: http://xxx.xxx.xxx.xxx:8000/admin/listclients.xsl?mount=/mountpoint to http://xxx.xxx.xxx.xxx:8000/admin/listclients?mount=/mountpoint and that gives me the XML. No need to change or modify anything. Now how do I get the json as I prefer json? Reaz > On Sep 22, 2020, at 1:51 PM, Reaz Baksh <reaz at dhantal.com> wrote: > >

Good afternoon, On Tue, 2020-09-22 at 11:43 -0400, Reaz Baksh wrote: > Too much work. I would like to refer to Jordan Erickson's comment here. > If I am able to see it on the web interface I should be able to get a Json or XML file with this in it. Why not just use the API? Remove the ".xsl" from any URL in the admin interface and get the raw XML. The rendered webinterface

Hi, I installed icecast2 on Debian 10 via backports for buster so that I could get ssl support. I’ve successfully configured iceacst to stream via ssl within the browser. No problems there. For instance I can successfully open a https link to the stream with a URL like https://domain-name.net:8433/mountname <https://domain-name.net:8433/mountname> However, the same URL with .m3u at the

I solved the issue by adding my own m3u files to /usr/share/icecast/web but I am not sure if this is icecast best-practice. This also raises a few other issues as well… http stream links don’t appear on the icecast stream directory and stream titles and track metadata does not display when opening m3u files created in this way. I assume that there are various reasons for this…mainly that https