rembo10 / headphones

Automatic music downloader for SABnzbd
GNU General Public License v3.0
3.36k stars 602 forks source link

Failed to start on port: 8181. Is something else running? #3224

Open SSoft7 opened 4 years ago

SSoft7 commented 4 years ago

Hi,

I am running headphones under docker and the following error appears when I try to restart via WebUI (restarting container works fine). Since this is the only application running within docker, I think its a bug within headphones app. Few things to note 1) I can access headphones UI when this error message appears, so its a false error. 2) This message keeps repeating itself (infinite loop) 3) Sometimes it does not happen but it is happening most of the time (when restarting via WEBUI).

You can find debug log here. It does not have Failed to start on port: 8181. Is something else running? message which I can only see on docker logs. But you can see it's trapped in a restart loop.

Thanks.

raymondjstone commented 4 years ago

Did you follow the guide for setting it up via docker? https://hub.docker.com/r/linuxserver/headphones/

SSoft7 commented 4 years ago

Did you follow the guide for setting it up via docker? https://hub.docker.com/r/linuxserver/headphones/

Yes, I have followed that guide, I think my configuration is fine.

SSoft7 commented 4 years ago

Just wanted to clarify one thing, the following message output comes from headphones log, not docker logs. Failed to start on port: 8181. Is something else running?

raymondjstone commented 4 years ago

and does that match the command line params for docker?

SSoft7 commented 4 years ago

and does that match the command line params for docker?

I am not sure what you actually mean, but I use the following port mapping in Docker CLI

-p <some_other_random_port>:8181 \

raymondjstone commented 4 years ago

so what exactly did you enter for other port?

SSoft7 commented 4 years ago

so what exactly did you enter for other port?

like I said above, it's a random port I choose (and the port is not used by any other application.), I have tried with different port .

robkamp commented 4 years ago

-p :8181 \

I assume that you will be fine, when you remove the <some_other_random_port> from your config line -p <some_other_random_port>:8181 \.

raymondjstone commented 4 years ago

I followed the instructions and it all worked perfectly fine for me, so without more info as requested there seems little that can be done to help

SSoft7 commented 4 years ago

-p :8181 \

I assume that you will be fine, when you remove the <some_other_random_port> from your config line -p <some_other_random_port>:8181 \.

Not sure why people are confused with this, but I use an actual port rather than the exact string <some_other_random_port> So, for example, let's say that's my configuration. -p 45678:8181 \

I followed the instructions and it all worked perfectly fine for me, so without more info, as requested there seems little that can be done to help

Did you actually restart from the WebUI? (not docker restart) I have just tried it again, and the issue still exists.

Here is the full command

docker run \
  --name=headphones-test \
  -e PUID=1002 \
  -e PGID=1002 \
  -p 45678:8181 \
  -v /tmp/appdata/config:/config \
  -v /tmp/appdata/downloads:/downloads \
  -v /tmp/appdata/music:/music \
  --restart unless-stopped \
  linuxserver/headphones

Screenshot

image

I would like to mention again that, this issue only appears when restarting via WebUI. and sometimes it does not happen (which is rare), but most of the time it appears. I hope i have given all info this time. let me know if you need more. :-)

switch48 commented 4 years ago

Anyone got a fix for this I got the same error after install