Hi! 2011/6/16 Dennis Heerema <[email protected]>: > Hello Romain, > > Thanks for the reply! > > >> transition. >> 2011/06/10 23:54:09 [src_4336:4] Activations changed: static=[], >> dynamic=[mksafe:studio(dot)mp3:studio(dot)mp3]. >> 2011/06/10 23:54:09 [safe_blank:4] Activations changed: >> static=[mksafe:studio(dot)mp3:studio(dot)mp3], >> dynamic=[mksafe:studio(dot)mp3:studio(dot)mp3]. >> 2011/06/11 10:51:53 [clock.wallclock_main:2] We must catchup 1.48 seconds! > > Hmmm.. I am not sure about what exactly is going on. First, I cannot > see any obvious indication of a bug in liquidsoap. > > The buffer overrun should be avoided. I'd suggests looking at > increasing the buffer and max parameters. > > > > I think you mean for the input stream?!
Yup! > However, I do not think this is the main issue. From what I read in > the logs, it seems that the connection is stopped some time before: > 2011/06/10 23:52:18 [src_4336:4] Buffer emptied, buffering needed. > > Then liquidsoap tries to fill the buffer again but never reach a > stable point. Finally, we see a catchup, which indicates that > liquidsoap got late while processing its sources. > > > Is it possible to restart / reconnect the input every x hours? Since the mp3 > output stream keeps running, no audio but stream says up, the listeners stay > connected. I restart liquidsoap as a program every 12 hours to get it > running again, even if it's not needed and then the users need to connect > again. So if i could restart /reconnect the input, it would much more > unnotisable. You can do that using the telnet commands. The input.http should have two start/stop commands that you can use for this purpose. > I'd suggests investigating on two points: > * Check if the internet connection was working ok. It has happened in > the past that a user had its internet connection restarted every 24h > for instance or had a temporary network failure. > > > Even when there is a longer failure, i would nice to have an automatic > restart / reconnect of the input stream. > > * Check if another "heavy" process could have been running on the > maching running liquidsoap. It has also happened in the past that a > user had trouble with liquidsoap because another process was suddenly > taking all CPU resources, leaving peanuts for liquidsoap.. > > I will check that to! Good, let us know about your progress so that we do not discard an issue in liquidsoap :) Romain ------------------------------------------------------------------------------ EditLive Enterprise is the world's most technically advanced content authoring tool. Experience the power of Track Changes, Inline Image Editing and ensure content is compliant with Accessibility Checking. http://p.sf.net/sfu/ephox-dev2dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
