[Icecast] understanding error.log

j h joefederigo at yahoo.com
Thu Jul 28 12:42:12 PDT 2005

Hello.  A couple questions.

When I execute curl
http://myserver.xxx.xxx:8000/test.mp3 , I get "<b>The
source you requested could not be found.</b>"

I've placed my error.log and icecast.xml files below. 

Could someone help me understand my error.log a little
better - to maybe see why I'm not getting a stream
when I make the above curl call.

Also, you'll see in icecast.xml I'm relaying an
arbitrary MP3 streaming station.  Is this possible?
I've seen mention of only needing an MP3 stream as
source to relay and others saying that you need a
Shoutcast or Icecast server source stream?  If it has
to be one of these two, why?

Thanks for any help.  First file below is error.log
and the second is icecast.xml.


- - - -

error.log after server stop and then start:

[2005-07-28  10:34:42] INFO main/main Shutting down
[2005-07-28  10:34:42] INFO fserve/fserve_shutdown
file serving thread stopped
[2005-07-28  10:34:42] DBUG slave/slave_shutdown
waiting for slave thread
[2005-07-28  10:34:43] DBUG slave/_slave_thread
shutting down current relays
[2005-07-28  10:34:43] DBUG slave/relay_free freeing
relay /test.mp3
[2005-07-28  10:34:43] DBUG source/source_free_source
freeing source "/test.mp3"
[2005-07-28  10:34:43] INFO slave/_slave_thread Slave
thread shutdown complete
[2005-07-28  10:34:43] INFO yp/yp_shutdown YP thread
[2005-07-28  10:34:43] INFO stats/stats_shutdown stats
thread finished
[2005-07-28  10:34:46] INFO main/main Icecast 2.2.0
server started
[2005-07-28  10:34:46] DBUG yp/yp_recheck_config
Updating YP configuration
[2005-07-28  10:34:46] INFO yp/yp_update_thread YP
update thread started
[2005-07-28  10:34:47] DBUG slave/_slave_thread
checking master stream list
[2005-07-28  10:34:47] DBUG slave/check_relay_stream
Adding relay source at mountpoint "/test.mp3"
[2005-07-28  10:34:47] INFO slave/start_relay_stream
Starting relayed source at mountpoint "/test.mp3"
[2005-07-28  10:34:48] DBUG
connection/connection_complete_source sources count is
[2005-07-28  10:34:48] DBUG
connection/connection_complete_source source is ready
to start
[2005-07-28  10:34:48] DBUG source/source_init Source
creation complete
[2005-07-28  10:34:48] INFO format-mp3/mp3_get_no_meta
End of stream /test.mp3
[2005-07-28  10:34:48] INFO source/source_shutdown
Source "/test.mp3" exiting
[2005-07-28  10:34:48] DBUG source/source_clear_source
clearing source "/test.mp3"
[2005-07-28  10:34:48] DBUG stats/modify_node_event
update node source_relay_connections (1)
[2005-07-28  10:34:48] DBUG stats/process_source_event
new source stat /test.mp3
[2005-07-28  10:34:48] DBUG stats/process_source_event
new node public (0)
[2005-07-28  10:34:48] DBUG stats/process_source_event
new node listenurl
[2005-07-28  10:34:48] DBUG stats/modify_node_event
update node sources (1)
[2005-07-28  10:34:48] DBUG stats/modify_node_event
update node source_total_connections (1)
[2005-07-28  10:34:48] DBUG stats/process_source_event
new node listeners (0)
[2005-07-28  10:34:48] DBUG stats/modify_node_event
update node sources (0)
[2005-07-28  10:34:48] DBUG stats/process_source_event
delete source node /test.mp3
[2005-07-28  10:34:48] DBUG slave/_slave_thread
rescanning relay lists
[2005-07-28  10:34:48] DBUG slave/check_relay_stream
waiting for relay thread for "/test.mp3"

Here is my config file:

        <!-- If enabled, this will provide a burst of
data when a client
             first connects, thereby significantly
reducing the startup
             time for listeners that do substantial
buffering. However,
             it also significantly increases latency
between the source
             client and listening client.  For
low-latency setups, you
             might want to disable this. -->
        <!-- same as burst-on-connect, but this allows
for being more
             specific on how much to burst. Most
people won't need to
             change from the default 64k. Applies to
all mountpoints  -->

        <!-- Sources log in with username 'source' -->
        <!-- Relays log in username 'relay' -->

        <!-- Admin logs in with the username given
below -->

    <!-- Uncomment this if you want directory listings
    <!-- 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>localhost</hostname> -->

    <!-- You can use these two if you only want a
single listener -->
    <!--<port>8000</port> -->
    <!-- You may have multiple <listener> elements -->
        <!-- <bind-address></bind-address>
    <!-- Only define a <mount> section if you want to
use advanced options,
         like alternative usernames or passwords


        <authentication type="htpasswd">
                <option name="filename"
                <option name="allow_duplicate_users"


    <!-- set the mountpoint for a shoutcast source to
use, the default if not
         specified is /stream but you can change it
here if an alternative is
         wanted or an extension is required

                <!-- basedir is only used if chroot is
enabled -->

        <!-- Note that if <chroot> is turned on below,
these paths must both
             be relative to the new root, not the
original root -->

        <!-- Aliases: treat requests for 'source' path
as being for 'dest' path
             May be made specific to a port or bound
address using the "port"
             and "bind-address" attributes.
        <alias source="/foo" dest="/bar"/>
        <!-- Aliases: can also be used for simple
redirections as well,
             this example will redirect all requests
for http://server:port/ to
             the status page
       <!-- <alias source="/" dest="/status.xsl"/>-->

        <!-- <playlistlog>playlist.log</playlistlog>
        <loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2
Warn, 1 Error -->

    <!-- i run icecast as iceuser for now -->

Start your day with Yahoo! - make it your home page 

Start your day with Yahoo! - make it your home page 

More information about the Icecast mailing list