**Regarding this specific issue :** (Cry Timeout / metadata update issue)
I had the same problem trying on a physical server, so it was not some kind of 
network/socket lag on the cloud instance.
CentovaCast team said bogus mp3 could cause issues. My client retagged all his 
mp3 (and maybe re-encoded some) and his stations run (almost) flawlessly since. 
(with around 3000 listeners on several streams for this server). Total CPU 
usage is around 60% average.

**Another issue :** 
However, another person has a station with very huge/fast variations of 
listeners (not sure what he is doing exactly) and the station (and others 
stations on the same server) were restarting and restarting.. connection 
timeout / reset by peer / We must catchup XX seconds (we've been late for 100 
rounds) .... 
in liquidsoap logs. Despite the server beeing quite powerfull.
Yet again this is another cloud server from another hosting company and i will 
try to switch at some point.
I don't see how liquidsoap/icecast can be laggy if there is still like 50% cpu 
available

First thing is check if you see the same track coming during the various 
timeout, and to try retag/rencode it.




-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/savonet/liquidsoap/issues/463#issuecomment-429663033
_______________________________________________
Savonet-users mailing list
Savonet-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to