[Icecast] Icecast dropping streams

Karl Heyes karl at xiph.org
Mon Feb 7 06:41:15 PST 2005

On Mon, 2005-02-07 at 14:22, Alek Andreev wrote:
> > These are usually down to non-utf8 chars being sent to icecast. Check
> > the metadata being sent
> That's quite likely, since some of the tracks have cyrillic ID3 tags. 
> What should I do to cirvumvent that?

use iconv to convert the metadata text to UTF8 and update the metadata.

> > That message occurs if icecast hasn't received any data after a certain
> > amount of idle time (<source-timeout> seconds).  This could be down to
> > the source client (ezstream) not sending anything or may be a network
> > outage. If icecast disconnects the source client or if the network has a
> > problem then the source client should try to reconnect.
> Not the case, since the source and Icecast run on the same machine.

If icecast drops the connection then the ezstream app will have to
attempt to reconnect, it can't keep feeding data to a dead socket for a
long time.

A syscall tracer like strace (eg strace -o output -p `pidof ezstream`)
can monitor what is happening to the app, see if data is being sent. You
could do the same thing with icecast but you need to identify the right
thread to monitor.


More information about the Icecast mailing list