Hello, I noticed the following error occuring about once every 24h, even when outputs are instructed to restart after a connection failed:
These are the relevant log sections: 2010/03/07 10:28:46 [src_5032:3] Switch to src_5028 with forgetful transition. 2010/03/07 10:29:05 [root:2] We must catchup 1.77 seconds! 2010/03/07 10:29:06 [root:2] We must catchup 1.62 seconds! 2010/03/07 10:29:07 [root:2] We must catchup 1.48 seconds! 2010/03/07 10:29:08 [root:2] We must catchup 1.36 seconds! 2010/03/07 10:29:09 [root:2] We must catchup 1.13 seconds! 2010/03/07 10:29:09 [src_5032:3] Switch to extern with transition. 2010/03/07 10:29:12 [root:2] We must catchup 0.32 seconds! [...] 2010/03/07 10:44:18 [root:2] We must catchup 0.45 seconds! 2010/03/07 10:44:23 [root:2] We must catchup 0.85 seconds! 2010/03/07 10:44:24 [root:2] We must catchup 1.01 seconds! 2010/03/07 10:44:25 [root:2] We must catchup 1.12 seconds! [...] (this goes on for several minutes, the time to catch up is increasing) 2010/03/07 10:53:28 [root:2] We must catchup 59.78 seconds! 2010/03/07 10:53:29 [root:2] We must catchup 59.94 seconds! 2010/03/07 10:53:29 [root:2] Too much latency! Resetting active sources.. 2010/03/07 10:53:29 [low(dot)ogg:3] Closing connection... 2010/03/07 10:53:29 [low(dot)ogg:3] Connecting mount low.ogg for sou...@localhost... 2010/03/07 10:53:30 [low(dot)ogg:3] Connection setup was successful. 2010/03/07 10:53:30 [high(dot)ogg:3] Closing connection... 2010/03/07 10:53:30 [high(dot)ogg:3] Connecting mount high.ogg for sou...@localhost... 2010/03/07 10:53:30 [high(dot)ogg:3] Connection setup was successful. 2010/03/07 10:53:30 [output(dot)shoutcast(dot)aacplus:3] Closing connection... 2010/03/07 10:53:30 [output(dot)shoutcast(dot)aacplus:3] Connecting mount / for sou...@localhost... 2010/03/07 10:53:30 [output(dot)shoutcast(dot)aacplus:2] Connection failed: bad answer 2010/03/07 10:53:30 [output(dot)shoutcast(dot)aacplus:3] Connection failed, will try again in 3 sec. 2010/03/07 10:53:30 [output(dot)shoutcast(dot)aacplus:3] Closing connection... 2010/03/07 10:53:30 [output(dot)shoutcast(dot)mp3:3] Closing connection... 2010/03/07 10:53:30 [output(dot)shoutcast(dot)mp3:3] Connecting mount / for sou...@localhost... 2010/03/07 10:53:30 [output(dot)shoutcast(dot)mp3:2] Connection failed: bad answer 2010/03/07 10:53:30 [output(dot)shoutcast(dot)mp3:3] Connection failed, will try again in 3 sec. 2010/03/07 10:53:30 [output(dot)shoutcast(dot)mp3:3] Closing connection... 2010/03/07 11:01:39 >>> LOG START After the last "Closing connection..." (2010/03/07 10:53:30), Liquidsoap became unresponsive, and needed a manual restart. Please explain what "We must catchup XX.XX seconds!" means, and how I could circumvent that problem. Regards, --polemon ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Savonet-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/savonet-users
