Icecast Streaming Media Server

[mkido]

Hello! everyone at here,

And especially, I thank you, karlH, for all the help last week. Now both Ices-cc-04 (Centova.com version) and IceCast 2.3 are running like daemons, but IceCast error log suggsted me "Reading, but not Sending".

Also, the simple host and 8000 port access returns in an access error.


I post a couple of running proofs and error logs, so, will you take a look at them? Any please suggest me any further debug probe. Thanks.

ices-cc-0.4

[mkido]

Because of this error, I reminded karl's comment, and I tried two ways of hostname in "icecast.xml", namely 64.214.83.249 or localhost. In either setting, the error.log of icecast shows the similar result. Reading but not sending.

mkido

[karlH]

looks to be operating normally. All you need now is to connect a player

karl.

[mkido]

Hi karl, thanks, thanks, again.

"now is to connect a player "

How to connect a player? The simplest HTML codes Web page as below was placed in a test directory in the server, and clicking from a Firefox 2.x wasn't enough.

[karlH]

The link will be on the status page, but it's basically http://address:port/mountpoint in this case http://address:8000/ices, you can add a .m3u to the end of that if you want an m3u playlist.

karl.

[mkido]

Hi! Dear karl,

I found "status.xsl" file at /usr/share/icecast/web/. I am not familiar with .XSL file, how to use it. It appears to generate a .HTML file by my quick study. When I placed "status.xsl" file in one of Web's HTML location, and I clicked the "status.xsl" file, it displayed almost HTML codes, rather than HTML page which is usually rendered by Firefox (if a file is .html).

Could you tell me briefly how to use "status.xsl" file? Or point me where to learn about it. Thanks.

mkido

[karlH]

you do not need to change the xsl file, it is placed in the webroot directory so that icecast can see it and present a html page to the browser. I repeat, no changes are required.

When you do http://address:8000/ in a browser, the request for / is translated by the alias in the xml to /status.xsl. icecast sees the status.xsl file, fills in the details based on the stream you have connected and sends back a web page for the browser.

karl.

[mkido]

I see. "status.xsl" file stays at the original (the standard) location.

/usr/share/icecast/web/ do I understand correctly?

[karlH]

The webroot is whatever you define in the icecast xml, If that is the path in webroot then that is where icecast will look for files when no streams match the specified request.

[mkido]

Great! karl,

Thank you always. I am getting by a step and a step into IceCast and Ices. Now I can recognize clearly <webroot>/usr/share/icecast/web</webroot> in icecast.xml file.

Now, I won't touch at all "status.xsl" file.

Because http://64.214.83.249:8000/ nor http://64.214.83.249:8000/ices have started a player yet. So, I will try the link of http://64.214.83.249:8000/ices.m3u, a little bit later.

Should I need to create a .m3u file somewhere, or adjust accordingly on a configuration file? Excuse me, a newbie is so vague at each step. Thanks, in advance.

mkido

[karlH]

no, the m3u link is automatically handled.

karl.

[mkido]

H! everyone and karl, how are you today? I feel great with your help.

As before, ices is working, and icecast is running, and reading mp3 files all the time like a daemon.

Unfortunately, I haven't gotten yet from firefox. My impression is that the port 8000 hasn't responded. Nor port 8000/ices did't reply well. It appears before the player issue. I tried to revise a HTTPdaemon configuration file (/etc/httpd/conf/http.conf) to make 8000 port listened, by adding a line "Listen 8000" after "Listen 80", then it complained that 8000 port is already in use by "make sock". Well, I will post the firefox's error snaps here. Any possible debug, or any probe idea? Thanks.


firefox can't establish a connection to the server at 64.214.83.249:8000


firefox can't establish a connection to the server at 64.214.83.249:8000/ices

[karlH]

If http://64.214.83.249:8000 is not connecting from an external address then check 2 things, the server is running and is listening on port 8000 and that you are forwarding external requests to the internal address. Obviously the latter will not apply if you try an internal address from within the LAN which you do have not reported yet.

karl.

[mkido]

yes, server is running,

[karlH]

netstat -tnlp | grep 8000

karl.