Hi, I had my stream running from ezstream 0.1.2 to icecast 2.2.0. It's been going for about a week, but two days ago I changed my icecast.xml. Since then, Icecast dropped my sources and stopped transmission twice. Everytime, it spew out xmlEncodeEntitiesReentrant : char out of range on STDERR and [2005-02-07 01:14:47] WARN source/get_next_buffer Disconnecting source due to socket timeout in the error log. I'm pretty sure my source is still running when it gets cut off, because I can see it's output. Any ideas? -- Regards, Alek Andreev alek@zvuk.net
On Mon, 2005-02-07 at 14:05, Alek Andreev wrote:> Hi, > > I had my stream running from ezstream 0.1.2 to icecast 2.2.0. It's been > going for about a week, but two days ago I changed my icecast.xml. Since > then, Icecast dropped my sources and stopped transmission twice. > Everytime, it spew out > > xmlEncodeEntitiesReentrant : char out of rangeThese are usually down to non-utf8 chars being sent to icecast. Check the metadata being sent> [2005-02-07 01:14:47] WARN source/get_next_buffer Disconnecting source > due to socket timeout > > in the error log. I'm pretty sure my source is still running when it > gets cut off, because I can see it's output. Any ideas?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. karl.
> These are usually down to non-utf8 chars being sent to icecast. Check > the metadata being sentThat's quite likely, since some of the tracks have cyrillic ID3 tags. What should I do to cirvumvent that?> 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. -- Regards, Alek Andreev alek@zvuk.net