jlesage / docker-jdownloader-2

Docker container for JDownloader 2
MIT License
820 stars 71 forks source link

[Bug] Abruptly broken? #164

Closed BasadoBased closed 1 year ago

BasadoBased commented 1 year ago

Current Behavior

After using this for a few months, today it's broken. The VNC interface just shows a black feed. The clipboard and such are working. Checking the logs, it seems to be in a boot loop. Did a recent JDownloader update break this? I haven't been messing with the container otherwise. Reinstalling and pulling latest did not help

Expected Behavior

No response

Steps To Reproduce

No response

Environment

Container creation

Portainer

Container log

`[supervisor  ] starting services...
[supervisor  ] starting service 'xvnc'...
[xvnc        ] Xvnc TigerVNC 1.13.1 - built May 16 2023 17:43:49
[xvnc        ] Copyright (C) 1999-2022 TigerVNC Team and many others (see README.rst)
[xvnc        ] See https://www.tigervnc.org for information on TigerVNC.
[xvnc        ] Underlying X server release 12014000
[xvnc        ] Wed Aug 23 03:17:38 2023
[xvnc        ]  vncext:      VNC extension running!
[xvnc        ]  vncext:      Listening for VNC connections on /tmp/vnc.sock (mode 0660)
[xvnc        ]  vncext:      Listening for VNC connections on all interface(s), port 5900
[xvnc        ]  vncext:      created VNC server for screen 0
[supervisor  ] starting service 'openbox'...
[supervisor  ] starting service 'nginx'...
[nginx       ] Listening for HTTP connections on port 5800.
[xvnc        ] Wed Aug 23 03:17:39 2023
[xvnc        ]  Connections: accepted: /tmp/vnc.sock
[xvnc        ]  SConnection: Client needs protocol version 3.8
[xvnc        ]  SConnection: Client requests security type None(1)
[xvnc        ]  VNCSConnST:  Server default pixel format depth 24 (32bpp) little-endian rgb888
[xvnc        ]  VNCSConnST:  Client pixel format depth 24 (32bpp) little-endian bgr888
[xvnc        ]  ComparingUpdateTracker: 0 pixels in / 0 pixels out
[xvnc        ]  ComparingUpdateTracker: (1:-nan ratio)
[supervisor  ] starting service 'app'...
[supervisor  ] all services started.`

Container inspect

No response

Anything else?

No response

jlesage commented 1 year ago

Yes, it's possible that JDownloader updated itself and created an issue. You can try the following instructions: https://support.jdownloader.org/Knowledgebase/Article/View/fix-jdownloader-installation

Your "JD installation directory" is the directory that you mapped to /config. You can create a copy of this directory if you want a backup. Make sure to stop the container before removing files/folder stated in the article.

BasadoBased commented 1 year ago

Thanks! I tried that and it didn't work until I also deleted JDownloader.jar. It's back to working.

jlesage commented 1 year ago

Great, thanks for the update.