| View previous topic :: View next topic |
| Author |
Message |
copycat
Joined: 26 Feb 2009 Posts: 3
|
Posted: Thu Feb 26, 2009 8:47 am Post subject: Having strange problem with Icecast2 status page |
|
|
I have one problem which I cant solve by myself because my knowledhe is limited so I need your help.
I have Icecast2 installed on VPS server with Centova Cast panel..Icecast works fine, but the problem is that Icecast2 Status page looks deformed. In Firefox I can open status page but its deformed, but I cant open in IE6..I get this error:
The XML page cannot be displayed
Cannot view XML input using style sheet. Please correct the error and then click the Refresh button, or try again later.
--------------------------------------------------------------------------------
The server did not understand the request, or the request was invalid. Error processing resource 'http://www.w3.org/TR/xhtm...
I have another server and on this server status page is displayed correctly..When I check page Info with Firefox on this server It says type: text/html but on this VPS server with problematic status page it says type: text/xml
You can check and see it: http://94.76.198.94:8002/
So what can be the problem?
Thanks,
[/img]
Last edited by copycat on Thu Feb 26, 2009 12:06 pm; edited 1 time in total |
|
| Back to top |
|
 |
jcr Modérateur français

Joined: 14 Apr 2006 Posts: 544 Location: France, Auvergne
|
Posted: Thu Feb 26, 2009 10:03 am Post subject: |
|
|
I tried your page with firefox 3, konqueror & Opera. Your page comes fine here.
I can see no problem at all with it. except you have no source connected  _________________ Epsilon Friends Radio Icecast Radio on CentovaCast admin panel. Icecast hosting |
|
| Back to top |
|
 |
copycat
Joined: 26 Feb 2009 Posts: 3
|
Posted: Thu Feb 26, 2009 12:16 pm Post subject: |
|
|
Strange, this is how I see it in FF 2 and FF3
 |
|
| Back to top |
|
 |
jcr Modérateur français

Joined: 14 Apr 2006 Posts: 544 Location: France, Auvergne
|
|
| Back to top |
|
 |
copycat
Joined: 26 Feb 2009 Posts: 3
|
Posted: Mon Apr 06, 2009 8:31 am Post subject: |
|
|
So doesn't any one know what can cause this problems with status.xls page?
http://94.76.216.94:1270/ |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Apr 06, 2009 1:46 pm Post subject: |
|
|
whenever I've seen this, it's because people hare running 2.3.1 web/adminroot xsl pages on a 2.3.2 server. 2.3.1 made assumptions about what an xsl content type was set to.
karl. |
|
| Back to top |
|
 |
nightwolff
Joined: 22 Apr 2009 Posts: 2
|
Posted: Wed Apr 22, 2009 10:57 pm Post subject: Status page broken |
|
|
I have had similar problems with the status page. It seems to happen most frequently whenever I have 3 or more users connected to streams. I am running version 2.3.2 for windows and the xsl file dates appear to be current.
Is there a known resolution to this problem?
Thanks,
Nightwolff
*edit*
Just looked at your error page Copycat. It looks the same as when I try to open status2.xsl on my server instead of status.xsl. Status2 is only 903 bytes and status is 4,748 bytes.
My problem is more with the page not loading the same way each time and my SAM statistics relay not liking what it sees. When I refresh the page multiple times it goes between formatted and unformatted with images randomly showing or not showing. http://67.171.204.23:8000/status.xsl
Last edited by nightwolff on Wed Apr 22, 2009 11:04 pm; edited 1 time in total |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Apr 22, 2009 11:01 pm Post subject: |
|
|
As I've already stated, the example shown was down to old xsl pages. If you are hitting a clients limit then you get a different effect.
karl. |
|
| Back to top |
|
 |
nightwolff
Joined: 22 Apr 2009 Posts: 2
|
Posted: Wed Apr 22, 2009 11:11 pm Post subject: |
|
|
It would still appear to be under my client limit. Should I be allowing for more than a few extra slots? Current limit is 6 users and 3 sources and I have issues with 2 servers and 3 users plus the statistics relays for that.
*edit*
Ah, nevermind. It seems you have pointed me to the problem. I have set individual listener limits for each mount point and increased the client limit to a much higher number to allow web browsers to multi-thread as seems to be the case. Thank you.
Nightwolff |
|
| Back to top |
|
 |
|