[Icecast] Icecast Fedora9 migration problems

[Karl Heyes]

Seann Clark wrote:

> The biggest being is that the server binds to whatever port it feels 
> like instead of the bind port specified. The rest of the issues I have 

a random port bind is a new issue. Can you show us the
netstat -tnlp | grep icecast
for the xml provided?

> with Icecast are minor (stats? What stats?) so here is the startup 
> script and config I am using:

if you have suggestions for extra stats which are shown on the web pages 
like /admin/stats then feel free to mention them.

> 
> Icecast 2.3.1:

ok, so slightly out of date.


> #################CONFIG#################
> <icecast>
...
>     <!-- You may have multiple <listener> elements -->
>     <listen-socket>
>         <port>8000</port>
>         <bind-address>192.168.10.5</bind-address>
>     </listen-socket>

looks straight forward enough

>     <master-server>192.168.10.5</master-server>
>     <master-server-port>8001</master-server-port>
>     <master-update-interval>120</master-update-interval>
>     <master-password></master-password>

so this is a slave icecast? the master is on port 8001


> <stats_log>/var/log/icecast/stats.log</stats_log>
> <statshtml_log>/var/www/html/icestat.html</statshtml_log>
> <stats_time>30</stats_time>

not sure where these come from, icecast2 will ignore them

>     <shoutcast-mount>/listen.pls</shoutcast-mount>

You have only specified 1 port so shoutcast source clients won't be 
streaming, but if you do intend to use one of those then you'll want a 
better mountpoint name as this implies a playlist.

>     <logging>
>         <accesslog>access.log</accesslog>
>         <errorlog>error.log</errorlog>
>         <playlistlog>playlist.log</playlistlog>
>         <loglevel>3</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
>     </logging>

level 4 gives more details, but do check the logs and in the case of 
port bindings, use the netstat command.

karl.