On 9/19/07, Vincent Tabard <[EMAIL PROTECTED]> wrote:
> * with restart = false, liq doesn't try to reconnect when the connection
> goes down. This behavior should definitely not be kept as a default,
> above all when you consider that liq doesn't stop or anything (even if
> no other output is defined): it just goes on with no output, sometimes
> appearing to try to reconnect ("Shout socket error..."), never
> successful. Worse, it eats 100 % CPU.This is odd. With restart=false liquidsoap tries to reconnect at least on Shout.Socket errors. I have successful reconnections on Dolebraï. But if the reconnection doesn't work immediately, liquidsoap should crash. At least, this is the intended behaviour. Concerning Romain's fix here, I'm not 100% sure but it seems off-topic: this behaviour is priori to the restart mode and there should be a way to fix it without half-using the devices created for the restart mode. (Also, I wonder if the reconnection won't be only after the restart_delay, with that fix.) > * with restart = true, things ain't much better. Liq sees disconnects > when everything is OK (other TCP connections don't seem affected by any > problem. maybe some dropped packets, but the connections generally hold, > and TCP can cope with lost packets). It sometimes drop the connection to > the Icecast server and eats 100 % CPU (see: http://paste.balbinus.org/135). You get a lot of Shout.Socket errors, we should figure out why. Then, the output does its job of reconnecting, but that frequent reconnections have a cost on the load, of course :\ ... -- David
