Icecast Streaming Media Server Forum Index Icecast Streaming Media Server
Icecast is a Xiph Foundation Project
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Ices-0.4 and Icecast-2.3, running in the same Server, OK?

 
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Source Clients
View previous topic :: View next topic  
Author Message
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Mon Oct 18, 2010 7:46 am    Post subject: Ices-0.4 and Icecast-2.3, running in the same Server, OK? Reply with quote

hi Icecast Forum, a newbie want to verify the fundamental question.


Do I run Source Clients (Ices-0.4) and IceCast-2.3 in the same Server computer (one host computer)? My company is a small scale right now, and all Web cast is running from one static IP, namely, one Server computer. Am I able to running both of them in the same computer? Because some documentation shows a diagram of two different computers.


If yes (it is OK, both are in the same computer), what should I do for the following mount failed error when I run "Ices-cc-0.4"?


Detail explanation is here. Since I didn't want to compile the Ices-0.4 from source codes, I did the search of precompiled RPM package on Google.com. Luckily it came out, "www.centova.com" (a company Centova in British Columbia, Canada) offers Fedora Core 7 "ices-cc-0.4" RPM. My company's server is just Fedora Core 7, so I immediately tried it, and it partially worked. Here is an error I got,


biwa$ices
Logfile opened
Playing 2010-03.en_01_01_01.mp3
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Ices Exiting...
~
biwa$


The ices-cc-0.4's configuration file is /usr/local/ices/etc/ices.conf.dist And I edited the "ices.conf.dist" file's <Stream><Server><hostname> 64.214.83.249 </hostname> .. , yet I am getting "127.0.0.1:8000/ices, error:" Should I reboot the Server computer? Or, Server computer's /etc/hosts file has both info, 127.0.0.1 localhost.localdomain localhost; AND 64.214.83.249 my.company.domin_name ...
Should I delete "127.0.0.1 localhost.localdomain localhost;" this line?

Thanks for your help, because I am still vague about "Mount" setting at the first time run.

mkido
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Mon Oct 18, 2010 12:54 pm    Post subject: Reply with quote

I suspect you assumed the default xml read is /usr/local/ices/etc/ices.conf.dist when actually is it something else, eg /etc/ices.conf

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Mon Oct 18, 2010 4:52 pm    Post subject: Centova.com changed from /etc/ices.conf, to /usr/local/ices Reply with quote

Hi Dear karlH,

It is very nice to have your comment. Thanks many times.


Now, the Canadian company "Centova.com" made significant changes on ices-0.4 codes, and it offers own ices-cc-0.4 (Centova version). As briefly explained above, it was convenient for me, because it offers ready RPM ices-cc-0.4 -i386.fc7, and I can bypass own compilation from the C-codes. I used that, and that is why directory location is different at ices-cc-0.4, /usr/local/ices/etc/ices.conf.dist (the file content shown below).


May I still keep using it? Or, should I give it up, and reinstall more original ices-0.4 version from IceCast.org? Please suggest me. Thanks.

mkido


[code]
~
localhost$more /etc/ices.conf
/etc/ices.conf: No such file or directory
~
localhost$more /usr/local/ices/etc/ices.conf.dist
<?xml version="1.0"?>
<ices:Configuration xmlns:ices="http://www.icecast.org/projects/ices">
<Playlist>
<!-- This is the filename used as a playlist when using the builtin
playlist handler. -->
<File>/home/mkido/playlist.txt</File>
<!-- Set this to 0 if you don't want to randomize your playlist, and to
1 if you do. -->
<Randomize>1</Randomize>
<!-- One of builtin, script, perl, or python. -->
<Type>builtin</Type>
<!-- Module name to pass to the playlist handler if using a script,
perl, or python. Ignored for builtin -->
<Module>ices</Module>
<!-- Set this to the number of seconds to crossfade between tracks.
Leave out or set to zero to disable crossfading (the default).
<Crossfade>5</Crossfade>
-->
</Playlist>

<Execution>
<!-- Set this to 1 if you want ices to launch in the background as a
daemon -->
<Background>0</Background>
<!-- Set this to 1 if you want to see more verbose output from ices -->
<Verbose>0</Verbose>
<!-- This directory specifies where ices should put the logfile, cue file
and pid file (if daemonizing). Don't use /tmp if you have l33t h4x0rz
on your server. -->
<BaseDirectory>/tmp</BaseDirectory>
</Execution>

<Stream>
<Server>
<!-- Hostname or ip of the icecast server you want to connect to -->
<Hostname>64.214.83.249</Hostname>
<!-- Port of the same -->
<Port>8000</Port>
<!-- Encoder password on the icecast server -->
<Password>letmein</Password>
<!-- Header protocol to use when communicating with the server.
Shoutcast servers need "icy", icecast 1.x needs "xaudiocast", and
icecast 2.x needs "http". -->
<Protocol>http</Protocol>
</Server>

<!-- The name of the mountpoint on the icecast server -->
<Mountpoint>/ices</Mountpoint>
<!-- The name of the dumpfile on the server for your stream. DO NOT set
this unless you know what you're doing.
<Dumpfile>ices.dump</Dumpfile>
-->
<!-- The name of you stream, not the name of the song! -->
<Name>Default stream</Name>
<!-- Genre of your stream, be it rock or pop or whatever -->
<Genre>Default genre</Genre>
<!-- Longer description of your stream -->
<Description>Default description</Description>
<!-- URL to a page describing your stream -->
<URL>http://localhost/</URL>
<!-- 0 if you don't want the icecast server to publish your stream on
the yp server, 1 if you do -->
<Public>0</Public>

<!-- Stream bitrate, used to specify bitrate if reencoding, otherwise
just used for display on YP and on the server. Try to keep it
accurate -->
<Bitrate>128</Bitrate>
<!-- If this is set to 1, and ices is compiled with liblame support,
ices will reencode the stream on the fly to the stream bitrate. -->
<Reencode>0</Reencode>
<!-- Number of channels to reencode to, 1 for mono or 2 for stereo -->
<!-- Sampe rate to reencode to in Hz. Leave out for LAME's best choice
<Samplerate>44100</Samplerate>
-->
<Channels>2</Channels>
</Stream>
</ices:Configuration>
~
localhost$

[/code]
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Mon Oct 18, 2010 5:18 pm    Post subject: Reply with quote

I cannot comment on the changes they have made, but I find it very unlikely that they used that as the default. especially when the error reported indicates a url that you have not specified. try enabling verbose.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Mon Oct 18, 2010 10:00 pm    Post subject: Verbose option here. Reply with quote

Hi karlH, thanks, here is verbose option's response.


[code]
biwa$ices -v
Logfile opened
DEBUG: Sending following information to libshout:
DEBUG: Stream: 0
DEBUG: Host: 127.0.0.1:8000 (protocol: http)
DEBUG: Mount: /ices, Password: letmein
DEBUG: Name: Default stream name URL: http://www.icecast.org/
DEBUG: Genre: Default genre Desc: Default description
DEBUG: Bitrate: 128 Public: 1
DEBUG: Dump file: (null)
DEBUG: Initializing playlist handler...
DEBUG: Initializing builting playlist handler...
DEBUG: Startup complete

DEBUG: Builtin playlist handler serving: 2010-03.en_01_01_01.mp3
DEBUG: Filename cleaned up from [2010-03.en_01_01_01.mp3] to [2010-03.en_01_01_01]
DEBUG: MPEG-1 layer III, 192 kbps, 44100 Hz, j-stereo
DEBUG: Ext: 0 Mode_Ext: 0 Copyright: 0 Original: 0
DEBUG: Error Protection: 1 Emphasis: 0 Padding: 1
Playing 2010-03.en_01_01_01.mp3
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
DEBUG: Caught signal, shutting down...
Ices Exiting...
~
biwa$
[/code]
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Tue Oct 19, 2010 12:22 am    Post subject: Reply with quote

well it doesn't say which conf is has opened. it's obviously not the one you were thinking of. I would just use strace to see what file it is opening eg

strace -e open ices

one of those will be the conf file

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Tue Oct 19, 2010 6:48 am    Post subject: result of strace -e open ices Reply with quote

Dear karlH, thank you, thank you, for your reply. I couldn't pin point which conf file is opened, so I will post the server reply as usual. Thanks.

By the way, I am running Centova "ices" at user level mkido, and at first BASH shell didn't recognized the command $ ices, so I added the PATH /usr/local/ices/bin/ to the DOT file .bashrc. And "playlist.txt" was placed at /home/mkido/, and it appears to be recognized as I intended in "ices.conf.dist" file above.

mkido


[code]
~
biwa$strace -e open ices
open("/usr/local/ices//lib/tls/i686/libshout.so.3", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/ices//lib/tls/libshout.so.3", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/ices//lib/i686/libshout.so.3", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/ices//lib/libshout.so.3", O_RDONLY) = 3
open("/usr/local/ices//lib/libxml.so.1", O_RDONLY) = 3
open("/usr/local/ices//lib/libmp3lame.so.0", O_RDONLY) = 3
open("/usr/local/ices//lib/libvorbisfile.so.3", O_RDONLY) = 3
open("/usr/local/ices//lib/libvorbis.so.0", O_RDONLY) = 3
open("/usr/local/ices//lib/libogg.so.0", O_RDONLY) = 3
open("/usr/local/ices//lib/libm.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib/i686/nosegneg/libm.so.6", O_RDONLY) = 3
open("/usr/local/ices//lib/libpthread.so.0", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/lib/i686/nosegneg/libpthread.so.0", O_RDONLY) = 3
open("/usr/local/ices//lib/libc.so.6", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/lib/i686/nosegneg/libc.so.6", O_RDONLY) = 3
open("/etc/resolv.conf", O_RDONLY) = 3
open("/etc/nsswitch.conf", O_RDONLY) = 3
open("/usr/local/ices//lib/libnss_files.so.2", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/etc/ld.so.cache", O_RDONLY) = 3
open("/lib/libnss_files.so.2", O_RDONLY) = 3
open("/etc/hosts", O_RDONLY) = 3
open("ices.conf", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/ices//etc/ices.conf", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/tmp/ices.log", O_WRONLY|O_CREAT|O_APPEND, 0666) = 4
Logfile opened
open("playlist.txt", O_RDONLY) = 5
open("2010-03.en_01_01_01.mp3", O_RDONLY) = 6
Playing 2010-03.en_01_01_01.mp3
--- SIGCHLD (Child exited) @ 0 (0) ---
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://127.0.0.1:8000/ices, error: Couldn't connect
Ices Exiting...
~
biwa$

[/code]
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Tue Oct 19, 2010 12:17 pm    Post subject: Reply with quote

so it looks like
Quote:
open("ices.conf", O_RDONLY) = -1 ENOENT (No such file or directory)
open("/usr/local/ices//etc/ices.conf", O_RDONLY) = -1 ENOENT (No such file or directory)


all you are using is the defaults, as I suspected, the conf file is not being read, so you really do need to specify the -c option, or copy the file to the standard place.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Tue Oct 19, 2010 3:52 pm    Post subject: Now, 64.214.83.249 is recognized. Reply with quote

Dear karlH, thank you!


At first I moved "ices.conf.dist" to standard place /etc and renamed "ices.conf", it didn't work, the same 127.0.0.1 came back. Then I moved it back to /usr/local/ices/etc and made sure "ices.conf.dist" was renamed to "ices.conf". Then it worked as below. Since I am running ices at user mkido, and the PATH /usr/local/ ices/bin was enabled.


Now, playlist is running, localhost is set to my current server 64.214.83.249. What is the next step on ices setting, to respond to "Error during send: Mount failed on http://64.214.83.249:8000/ices, error". Excuse me, a newbie needs your help at every step.


mkido



[root@biwa etc]# mv ices.conf /usr/local/ices/etc/
[root@biwa etc]# cd /usr/local/ices/etc/
[root@biwa etc]# ll
total 8
-rw-r--r-- 1 root root 3146 2010-10-17 23:26 ices.conf
drwxr-xr-x 2 root root 4096 2010-10-17 22:54 modules
[root@biwa etc]# exit
logout

~
biwa$ices -v
Logfile opened
DEBUG: Sending following information to libshout:
DEBUG: Stream: 0
DEBUG: Host: 64.214.83.249:8000 (protocol: http)
DEBUG: Mount: /ices, Password: letmein
DEBUG: Name: Default stream URL: http://localhost/
DEBUG: Genre: Default genre Desc: Default description
DEBUG: Bitrate: 128 Public: 0
DEBUG: Dump file: (null)
DEBUG: Initializing playlist handler...
DEBUG: Initializing builting playlist handler...
DEBUG: Randomizing playlist
DEBUG: Startup complete

DEBUG: Builtin playlist handler serving: 2010-03.en_01_01_01.mp3
DEBUG: Filename cleaned up from [2010-03.en_01_01_01.mp3] to [2010-03.en_01_01_01]
DEBUG: MPEG-1 layer III, 192 kbps, 44100 Hz, j-stereo
DEBUG: Ext: 0 Mode_Ext: 0 Copyright: 0 Original: 0
DEBUG: Error Protection: 1 Emphasis: 0 Padding: 1
Playing 2010-03.en_01_01_01.mp3
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Error during send: Mount failed on http://64.214.83.249:8000/ices, error: Couldn't connect
Too many stream errors, giving up
Ices Exiting...
~
biwa$
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Tue Oct 19, 2010 6:19 pm    Post subject: Reply with quote

Now your ices is using the correct conf file so that aspect is fine. The problem now seems to be access to icecast. Make sure that you can access the icecast server from the same machine using that address (http://64.214.83.249:8000/), if that is an external address then it may be not what you want to use.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Tue Oct 19, 2010 11:09 pm    Post subject: Installed icecast, now editing icecast.xml file Reply with quote

Dear karlH, wonderful, wonderful, step by step, thank you so much.


Now, I just installed icecast by,
# yum install icecast (in the same server computer where ices-cc-0.4 is running)

the installed version is icecast-2.3.1-4.



Now, I started editing /etc/icecast.xml. I edited hostname as below,

[code]
<!-- This is the hostname other people will use to connect to your server.
It affects mainly the urls generated by Icecast for playlists and yp
listings. -->
<hostname>64.214.83.249</hostname>

[/code]


There are a few others, such as

<!-- You may have multiple <listener> elements -->
<!-- <bind-address>127.0.0.1</bind-address> -->

<!--<master-server>127.0.0.1</master-server>-->

<!--
<relay>
<server>127.0.0.1</server>
<port>8001</port>
<mount>/example.ogg</mount>
<local-mount>/different.ogg</local-mount>
<on-demand>1</on-demand>

<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
-->

Should I edit them, although they are all under comments.

By a quick test of "$ ices -v ", I still see the same error. Please help me again.

mkido
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Wed Oct 20, 2010 12:24 am    Post subject: Reply with quote

hmm, 2.3.1 is not the latest but it should suffice for you. Only set entries if you know what they are for. After that is done then run the server, that way, it will answer when ices tries to connect.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Wed Oct 20, 2010 4:27 pm    Post subject: Setting entries. Reply with quote

Hi! KarlH, thanks, now about "entries".

I did a little self-studies, and your comment "entries" sounds like Web's XML's page's xml code tag. Do I understand you correctly? Before I do further studies about "entries", I am posting here to be sure. Like below?

mkido


[code]
<?xml>
<title></title>

<entries>
<ref href ="http://64.214.83.249:8000/mount">
</entries>

</xml>
[/code]
Back to top
View user's profile Send private message Visit poster's website
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Wed Oct 20, 2010 5:52 pm    Post subject: Reply with quote

I should of been more clear, I meant tags not entries. For instance you do not set <relay> unless you intend to relay a stream. For a source client you don't need a <mount> but if you do need to set any specific setting like say <max-listeners> then you will need a mount section.

start with the basics and work from there, you will soon find that this is all rather trivial.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
mkido



Joined: 22 Jan 2010
Posts: 63
Location: Los Angeles, California

PostPosted: Thu Oct 21, 2010 12:56 am    Post subject: Study time on other posts in Forum and documentations. Reply with quote

Hi! KarlH, Thanks so much.


What you meant is "tag"(s) in icecast.xml and ice.conf. Alright, I will take a little break here for me to study as much as basics from other posts and documentations. After that, when it comes to another tests and experiments, I will post a question somewhere in this Forum. Thanks so much for your help of installation, especially of ices 0,4 (Centova version).


mkido
Back to top
View user's profile Send private message Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Source Clients All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2002 phpBB Group
subRebel style by ktauber