Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

jdownloader hangs after update #132

Open
kinslayer1982 opened this issue Mar 27, 2024 · 1 comment
Open

jdownloader hangs after update #132

kinslayer1982 opened this issue Mar 27, 2024 · 1 comment

Comments

@kinslayer1982
Copy link

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:
- /volume1/docker/data/jdownloader:/opt/JDownloader/app/cfg
- /volume1/downloads:/opt/JDownloader/Downloads
- /etc/localtime:/etc/localtime:ro
environment:
MYJD_USER: xxx
MYJD_PASSWORD: xxx
MYJD_DEVICE_NAME: xxx
XDG_DOWNLOAD_DIR: /opt/JDownloader/Downloads
ports:
- 0.0.0.0:3129:3129

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
Copy link

peterpepo commented May 17, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants