Closed webtent closed 6 years ago
Hi,
Buffer overrun logs usually happen when the input.http
source receives too much data. This can have several reasons, such as the sender sending data at a rate above real-time or by bursts, or the two machines having clocks that are slightly out of sync.
One way to mitigate the issue is to raise the max
buffer in input.http
:
s = input.http(max=20., ...)
This did not work for me either:
input.http(buffer=10.0, max=20.0, id="http", starturl)
Beside other issues, one reason might be, that the input stream is not routed to any output (yet). In such case, the buffer piles up and is never consumed by an output. As a consequence you'll get a buffer overrun.
I solved this be routing the input stream to some dummy output, which is fallible:
output.dummy(id="DUMMY_STREAM_OUTPUT", fallible=true, input_http)
Hi, I am a complete newbie with Liquidsoap. We have been running Icecast2 with Darkice for a long time at our community radio station, setup by someone else. I've been tasked with upgrading since the install is very old on Ubuntu 10.04 and we need secure streaming. I've decided to start fresh and give Liquidsoap a try.
The install went great following a Linux Journal article from this past January, I installed the latest Icecast2 compiled with SSL support and the latest Liquidsoap from source using opam. Everything plays fine and I've mounted the other streaming server streams to my new server to provide the secure stream until we can get another card to add the input directly. The only thing is this error in the Liquidsoap log....
2018/04/24 08:59:26 [http_6166:3] Buffer overrun: Dropping 0.00s.
I'm seeing this over and over again, but the streams all seem to play fine, here is my config....
And then my included config....
Can someone help me understand what is causing the log entry or any other recommendations?