Hi Alexander,
Here is a list of features that use pipes in liquidsoap:
src/decoder/external_decoder.ml
src/decoder/gstreamer_decoder.ml
src/encoder/gstreamer_encoder.ml
src/io/gstreamer_io.ml
src/operators/video_text_gstreamer.ml
src/outputs/pipe_output.ml
src/protocols/extproto.ml
Hello!
After 2 or 3 days uptime liquidsoap processes started to crash again :((
Error messages in log seems to be same.
Hoping for a miracle :)
2014-01-31 David Baelde david.bae...@gmail.com:
Hi guys,
Just a thought for Romain: how about pipes used as locks inside duppy?
Could there be a
Hi Alexander,
Thanks for the extra info. Nothing to worry about regarding liquidget,
it's a harmless wrapper around wget. The logs are useful, as they
point to pipes rather than downloaded files. You must be using some
feature (external encoder, maybe) that uses pipes for interprocess
Hello!
No, we don't use external encoder. But, as we support mp3/ogg/aac with big
variety of bitrates, we have a lot of definitions for each format. I will
send library we use to create/remove outputs (we allow to change output
formats/bitrates on the fly) in a separate main directly to you, just
Hi all,
I think the open pipes point to the problem. Beside external encoders,
calling external processes may also open pipes and it's possible that
that would be the issue.
I see that you are using an external command for your php bridge. Can
you test without it and, if so, do you observe the
It is impossible... Our script contains nothing itself, all data it
receives from bridge. It is very-very dynamic. We call this (one) script
with station id as a parameter and after it receives all configuration via
bridge. Perhaps there is another way to research this issue? Below there is
some
Hello!
I've also added your email directly to recipients list (in case
sourcefourge lists will crop attachments). Please find answers on your
questions below:
Are you using the standard resolver for http, that is wget?
Hmm.. i suppose that we use wget. ./configure script shows in table
following
Hi,
No clue so far, so I'll ask a few questions instead.
* Are you using the standard resolver for http, that is wget?
* Do you have a reasonable number of alive requests? You can see this
using the request.alive server command. On the server you can also
perform request.trace to see what
Hi Alexander,
Could you please describe a little bit how you use dynamic requests?
At least, I need to know what parameters (queue, etc.) you are using
but the kind of protocol involved is probably useful too.
Cheers,
David
On Fri, Jan 24, 2014 at 10:26 AM, Alexander truenr...@gmail.com wrote:
Issue still reproduces, every day.
I found http://dev.sourcefabric.org/browse/LS-508, where it is said that
bug was fixed...
Have no idea how to workaround this... please assist :(
2014/1/19 Alexander truenr...@gmail.com
Hello,
We use request.dynamic to play files from remote server (via
Hello,
We use request.dynamic to play files from remote server (via http).
Yesterday i've found liquidsoap crashed, could you please help to research?
In log i saw following lines:
2014/01/18 14:55:16 [request.dynamic_5970:3] Finished with
/tmp/liq7e1fc7.mp3.
2014/01/18 14:55:16
11 matches
Mail list logo
