Hi, I've a little bit trouble. I've set up an icecast 2.2.0 and an ices 0.4 system. Every song, sometimes every two songs my playler lost the connection to the stream and in DEBUG-Mode I found a logfileentry like: DBUG source/send_to_listener Client has fallen too far behind, removing. I changed the queue-size in icecast.xml from 102400 to 902400 (don't know if it is a good value) but the only result is the interrupt occur some songs later. I'm realy confused, cause it is not my first icecast-setup and on an other server I've installed the same: Icecast 2.1.0 (ok nearly the same) and ices.0.4. The config-files are the same. The main difference is a newer OS. On the working system it is SuSE 8.2 and on the failing system there is a SuSE 9.1 OS installed. Could that be the problem? I can't believe it! Any idea what I can do to solve the problem or what could the reason for it? Many thanks and greetings Anatol
On Tue, 2005-05-10 at 22:23, Anatol wrote:> Hi, > > I've a little bit trouble. I've set up an icecast 2.2.0 and an ices 0.4 > system. Every song, sometimes every two songs my playler lost the > connection to the stream and in DEBUG-Mode I found a logfileentry like: > DBUG source/send_to_listener Client has fallen too far behind, removing. > > I changed the queue-size in icecast.xml from 102400 to 902400 (don't > know if it is a good value) but the only result is the interrupt occur > some songs later.Increasing the value is not a problem. It just allows for more lag with the listeners before kicking them off (fallen too far behind)> I'm realy confused, cause it is not my first icecast-setup and on an > other server I've installed the same: Icecast 2.1.0 (ok nearly the same) > and ices.0.4. The config-files are the same. > > The main difference is a newer OS. On the working system it is SuSE 8.2 > and on the failing system there is a SuSE 9.1 OS installed. Could that > be the problem? > I can't believe it! > > Any idea what I can do to solve the problem or what could the reason for it?The problem is the icecast to listener connection, for some reason the connection is not able to maintain the stream bitrate to that listener. The reasons can vary from bad network connection, latency being too high for the TCP settings, proxies getting in the way or just congestion. karl.
On 5/10/05, Anatol <icecast@recordcaster.de> wrote:> Hi, > > I've a little bit trouble. I've set up an icecast 2.2.0 and an ices 0.4 > system. Every song, sometimes every two songs my playler lost the > connection to the stream and in DEBUG-Mode I found a logfileentry like: > DBUG source/send_to_listener Client has fallen too far behind, removing. > > I changed the queue-size in icecast.xml from 102400 to 902400 (don't > know if it is a good value) but the only result is the interrupt occur > some songs later.This usually means the client can't receive fast enough - possible because their connection is too slow. It's normal to get it occastionally with some songs. If it's dropping clients that are fast enough, maybe there's something wrong with your mp3 files? The ices log files might have more useful info. Increasing the queue size will almost always just delay a problem, not solve it. Mike> > I'm realy confused, cause it is not my first icecast-setup and on an > other server I've installed the same: Icecast 2.1.0 (ok nearly the same) > and ices.0.4. The config-files are the same. > > The main difference is a newer OS. On the working system it is SuSE 8.2 > and on the failing system there is a SuSE 9.1 OS installed. Could that > be the problem? > I can't believe it! > > Any idea what I can do to solve the problem or what could the reason for it? > > Many thanks and greetings > Anatol > > _______________________________________________ > Icecast mailing list > Icecast@xiph.org > http://lists.xiph.org/mailman/listinfo/icecast >
Michael Smith schrieb:>On 5/10/05, Anatol <icecast@recordcaster.de> wrote: > > >>[...] >> >> >This usually means the client can't receive fast enough - possible >because their connection is too slow. It's normal to get it >occastionally with some songs. > >If it's dropping clients that are fast enough, maybe there's something >wrong with your mp3 files? The ices log files might have more useful >info. > >Hm ... the two servers are in the same rack. From the one there is no problem to recive data and the other has the troubles. The connection can't be the bottle neck. The MP3 s seams to be ok. The ices.log told me nothing about an error with the MP3-Files. The only entry I found was: "Error during send: Libshout reported send error, disconnecting: Socket error" But I can't relate this message to the "to far behind"-Mesage. There are different timestamps.>Increasing the queue size will almost always just delay a problem, not solve it. > >Right! From there I wrote my mail ;-) Anatol