search

kessibi / libretime-docker

ATTENTION: Libretime now offers a way of running it in docker containers. This project wont see anymore development. One way to get libretime to work within a Docker container
27 stars 12 forks source link

Unable to connect to the Airtime server (Liquidsoap starts, then stop itself) #21

Closed valerio-bozzolan closed 3 years ago

valerio-bozzolan commented 3 years ago

Hello everybody,

I've a fresh host and I've executed

docker run -p 80:80 -p 8000:8000 -p 8001:8001 --name=libretime odclive/libretime-docker:latest

Then completed the installation. The strange part is that for some seconds Liquidsoap is marked as running:

image

Then it shutdown itself:

image

After that, In the logs I see:

$ docker exec -ti libretime /bin/bash
$ tail -f airtime-liquidsoap.service.log 
Unable to connect to the Airtime server.
Unable to connect to the Airtime server.
Unable to connect to the Airtime server.
Unable to connect to the Airtime server.
Unable to connect to the Airtime server.

And this is the airtime_analyzer.log:

2020-11-24 22:16:32,451 [message_listener] [ERROR]  Connection to 127.0.0.1:5672 failed: [Errno 111] Connection refused

Any clue about how I was able to mess up this docker? :see_no_evil:

Additional information:

This web page is served via a simple HTTP proxy made with Apache, too keep the Docker internal. Something very usual I think. But this may be the problem because I'm not able to reproduce this issue when running this Docker not on this server but on my computer and visiting via localhost.

Any troubleshooting tip?

kessibi commented 3 years ago

I tried a sample installation using docker run -p 80:80 -p 8000:8000 -p 8001:8001 --name=libretime odclive/libretime-docker:latest which pulled the image from the web. It started correctly and when asked to start liquidsoap services I executed docker exec libretime sh /libre_start.sh. The install works on my side and liquidsoap doesn't stop like it does on your side (can correctly create shows, import and play musics).

So it might indeed be a problem from your HTTP proxy, I am not sure I understand what's going on with it...

valerio-bozzolan commented 3 years ago

In this case I suggest to mark this issue as invalid and cannot reproduce or something like that.

Thanks for your work and apologies if I have not enough time to provide further troubleshooting.

To be honest at the end we fixed adopting this Docker image:

https://github.com/ned-kelly/docker-multicontainer-libretime/blob/master/README.md

kessibi commented 3 years ago

Alright, glad it works for you in the end.