similar to: Strange behaviour with admin/stats.xsl disappearing

Hi, On 2 Sep 2024, at 12:19, Marek Dziembowski wrote: > Greetings icecasting amigos! > > > I?ve had an incredibly frustrating journey getting a new icecast origin server going to supplant an older machine set for retirement. > > The setup is relatively simple ? a beefy Debian bookworm host running icecast as a relaying slave pulling the streamlist from an icecast2 2.4.4 ingest

Is something broken here? I'm trying to do a test of relaying between two servers running kh-57. Master-slave relaying fails: the connection fails on the master with: [2004-11-01 17:05:32] DBUG admin/admin_handle_request Got command (streamlist.txt) [2004-11-01 17:05:32] INFO admin/admin_handle_request Bad or missing password on admin command request (command: streamlist.txt) As far as

On Aug 29, 2004, at 8:54 PM, Karl Heyes wrote: > The hidden tag applies to <mount> sections, and therefore works with > relays or source clients. BTW I've done some more changes to the svn > branch to better handle the hidden mounts, so either use svn or wait > for > kh53 Karl, are there any appreciable differences between the KH branch and what could be considered

It should. I just tried it out my own instructions after letting them go a few days. I didn't want them fresh in my mind. I simply copied the configs and played dumb (not too hard). I then started up my playlist server and am listening to it right now. I tested out the streaming stuff a few days ago with good results. Hope it works out as well for you all. Find anything wrong, let me know and

Hi, icecast kh52 It would be great if <hidden> tag can be used inside <relay> block. ---------------------------------------------------- Kate Hudson w najnowszej komedii romantycznej tw?rc?w Pretty Woman i Uciekaj?cej Panny M?odej. -->> MAMA NA OBCASACH w kinach od 27 sierpnia! http://klik.wp.pl/?adr=http%3A%2F%2Ffilm.wp.pl%2Fp%2Ffilm.html%3Fid%3D24805&sid=230

This is to announce the release of Icecast 2.3.2 2.3.2 is mainly a bug fix release with a couple of new items that may be of interest to a few of you. Even if the new features are not of interest, it is still highly recommended that you update to 2.3.2. Downloads are here : http://downloads.xiph.org/releases/icecast/icecast-2.3.2.tar.gz

We are pleased to announce Icecast 2.5 beta2 (2.4.99.2). This is a beta release and not recommended for production use. ## Downloads -   Source:     http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz -   SHA256sum:     a83baf4ae3ee5c2822bcb4286b7438b01317ccb8387371922e9cd32fe1c453e8 -   Packages:     https://build.opensuse.org/repositories/multimedia:xiph:beta ## New features

We are pleased to announce Icecast 2.5 beta2 (2.4.99.2). This is a beta release and not recommended for production use. ## Downloads -   Source:     http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz -   SHA256sum:     a83baf4ae3ee5c2822bcb4286b7438b01317ccb8387371922e9cd32fe1c453e8 -   Packages:     https://build.opensuse.org/repositories/multimedia:xiph:beta ## New features

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

should there be a constant GET /admin/streamlist on a relay main server ?? this may be my problem ; what would cause this to stop updating ? but still remain running .. -- access.log on main server ( not relay ) 130.63.239.188 - - [03/Apr/2003:21:14:48 -0500] "GET /admin/streamlist HTTP/1.0" 200 46 "-" "-" 0 130.63.239.188 - - [03/Apr/2003:21:16:48 -0500] "GET

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

Hi there, My error log is full of these 2 lines [2015-05-12 08:08:07] INFO fserve/fserve_client_create checking for file /7.html (/usr/share/icecast2/web/7.html) [2015-05-12 08:08:07] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/7.html" No such file or directory I have checked the Icecast sources and couldn't find any file named 7.html, so I was

Hi, I realise that the web is littered with posts and discussions concerning the topic of getting icecast stats from the xsl files (status-son.xsl) in the icecast web directory. As you may know, many of the solutions are outdated and example links are broken. I have limited knowledge of how to write my own javascript to get this info to display on my own website. Wondering if anyone can refer me

Hi I'm clutching at straws here. I have a user who requires access to a status-json.xsl to publish now playing data for an Alexa skill and this can be accessed via a browser at: - http://example.com:8000/status-json.xsl He says that now his PHP script cannot access the file. I know that Alexa requires *streams* to be served over https but this has previously worked and his skill is

Hi... Can someone do me the favour of pointing us at a routine, library, script or technique that will grab Now Playing metadata (Title, Artist, Album) remotely (ie from another machine) from an Icecast 2.4.x server reliably for logging purposes, preferably using PHP? Ideally we would grab the metadata when it changes - all the methods we've tried so far require us to poll the server so

Consider this a Ticket for Icecast 2.4 ******************************************************************************** If you look at {{{ admin/stats.xml }}} on a Icecast-KH server (default setup) and an Icecast 2.4 server (default setup) the following is one of the things that the KH branch has as extra info. {{{ <listener id="3581"> <ID>3581</ID>

Hi there, I haven't been on this list until now, so I wasn't aware of this problem until last night ;-) - sorry for that. I am working on a patch for oggCut for that issue (looks good actually but I would like to do some testing befor I can release a patch.) Normal players are not effected by the page time misordering, so I took this issue as "minor". The reason for the

Okay, so here is what I have now. I am setting up an icecast server for our customers to use for streaming audio -- in particular there will be a couple of radio stations in town using it. I want it to run on a cluster of systems for redundancy. So I have the server running on two identical machines on one ip that is dedicated to streaming services, behind a foundry switch. The foundry switch

(see forwarded mail further below) Shoutcast v1, Shoutcast v2, Icecast-KH are all "compatible" with the way info is collected by StreamLicensing. Some may wonder why bothering to humor StreamLicensig, but the thing is that other licensing/royalty collectors did it the same way. StreamLicensing are now sadly the only ones that cater to small independent station that do not wish to be