search

jaymoulin / docker-jdownloader

JDownloader 2 Docker Image (Multiarch) - 50M+ Downloads
https://brands.jaymoulin.me/me/docker-jdownloader
MIT License
180 stars 36 forks source link

jdownloader hangs after update #132

Open kinslayer1982 opened 5 months ago

kinslayer1982 commented 5 months ago

Not really sure if this is a bug related to this docker image or jdownloader itself, so I'll post it here just to make sure.

-->

Output of docker inspect jdownloader --format='{{index .Config.Labels.version}}':

2.1.2-amd64 (But happens on other platforms as well)

Description

Command line I used to start the container

docker-compose.yml: services: jdownloader: image: jaymoulin/jdownloader:2.1.2 container_name: jdownloader restart: always user: 1026:100 volumes:

Steps to reproduce the issue:

  1. create jdownloader container
  2. install updates if available

Describe the results you received: Jdownloader no longer available via myjdownloader. Restarting doesn't help.

Describe the results you expected: Jdownloader being available after updating.

Additional information you deem important (e.g. issue happens only occasionally): If the error occurs I have to stop the container and start it without the -d parameter. This way the container will start, jd will update and run fine until the same happens again after some more updates.

Could be related to #128 and similar as I have seen the "no console available" output in my logs too. And running it interactively once will fix the issue for a while.

peterpepo commented 4 months ago

It may be, as I receive "No console available" error message from time to time. Deleting the container, config files and recreating it always fixes it. But you have to set your settings(download speeds, accounts etc..) from scratch. And of course - don't do this in the middle of file download (not even paused), as you will loose progress.

grapemix commented 1 week ago

In k8s, restarting the pod can temp fix it, but this problem is really annoying. I suspect adding "-Djava.net.preferIPv4Stack=true" will do the trick.

ref: https://board.jdownloader.org/showthread.php?t=93571

kinslayer1982 commented 3 days ago

In k8s, restarting the pod can temp fix it, but this problem is really annoying. I suspect adding "-Djava.net.preferIPv4Stack=true" will do the trick.

ref: https://board.jdownloader.org/showthread.php?t=93571

No it doesn't, this is a totally different problem. Comparing being unable to contact the update server and getting stuck because of a missing console doesn't make sense. Just like saying a restart will fix something that isn't fixed by a simple restart.

I don't know how k8s work, but i think you are either mixing things up or are talking about a different problem.