QNAP Container Station (Erorr)

[pieromobile]

After installation on my qnap container station, when starting jdownloader various update errors are displayed with consequent program shutdown.

Error GUI

Error Console

[pieromobile]

After reinstal application

[jlesage]

How did you created the container ? Can you share the docker run command you used and/or the config ?

[mLgz0rn]

I got the same issue on unraid. With both yours and ich777's image. It happened after a recent update.

[jlesage]

After an update of what ?

[mLgz0rn]

After an update of what ?

Of Jdownloader itself.

[pom2ter-git]

Hi ! Exactly the same problem for me. It may be a Container Station update that introduced this malfunction. By digging a bit, I realize that what causes this crash for me is due to the fact that I modify the USER_ID, because I use a shared volume from the NAS to save my downloaded files... JDownloader is therefore no longer usable, because if I leave the default USER_ID=1000, this certainly allows me to correctly install my container and start JDownloader, but I no longer have access to my directory for writing (and I have then an error message from JDownloader)

[jlesage]

Is this still an issue with the latest image?

[liuk4friends]

Hi @jlesage,

Latest image (v22.11.1) doesn't work with my Qnap Container Station (version 2.6.2.574 2022/10/31).

Last working version for me is 1.72.1.

Below you can find my docker compose file that is working right now:

version: '3'
services:
  jdownloader2:
    image: jlesage/jdownloader-2:v1.7.2
    ports:
      - "5800:5800"
      - "3129:3129"
    volumes:
      - "/share/CACHEDEV1_DATA/Container/container-station-data/application/jdownloader2:/config:rw"
      - "/share/CACHEDEV2_DATA/Download/jd2:/output:rw"

[jlesage]

What is the problem exactly?

[liuk4friends]

hi @jlesage,

I reinstalled the latest version to reproduce the problem and to give you some debug information. With latest jdownloader2 version the Container crashes when vnc service is starting.

You can find the log here below: https://pastebin.com/D6XWpzs6

And here you can find a screenshot :

I hope this can help...

Edited on 23/111/2022

[jlesage]

Do you also have the log from v1.7.2 ?

[liuk4friends]

Ok, I restarted the container. Here is the log:

LOG deleted (incomplete)

Message edited on 23/11/2022

[jlesage]

Log is incomplete. Did you run docker logs <container name> to get it ?

[liuk4friends]

Sorry, no. I've got the log from Portainer (running "inside" my Container Station). If it could be useful, tonight I could try your suggestion.

[liuk4friends]

So here I am. Below you will find the log of 1.7.2 working version, that I obtained following your indication (after I gave the "restart" command of the container).

https://pastebin.com/VwWugbZy

During the boot phase, the web interface on port 5800 reports an error. Only if you close the dialog boxes with the 'ok' button the boot will be successful. I took a screenshot:

[jlesage]

Could you expand the error window so we can see the full messages ?

[MeisterBAP]

I was using this on my QNAP for some month. After having some troubles I decided to reinstall and now I can't bring it back to work again. Whenn connecting to the GUI I see similar pictures. It tries to connect to update.appworker.org and fails. Using the terminal I made sure that outbound connections are working correcty.

[liuk4friends]

Could you expand the error window so we can see the full messages ?

Ok. I restarted again the container. Below you can find two screenshot:

As explained in my previous posts, this error appears when starting version 1.7.2. I guess it's the update to version 22.11.1 that doesn't work (at least in my case).

And just to be as clear as possible, version 1.7.2 of the container presents this "update error" during the boot phase but, once the dialog box is closed, jdownloader2 starts and works perfectly. Instead the 22.11.1 version of the container doesn't work at all.

[MeisterBAP]

I tried to do a fresh install with every version beginnig with the latest back to 1.6.0 and I was not able to start jdownloader. On first boot it tries to connect to update.appwork.org. Anything I did made the container shut down.

My last Test was to set up a proxy server. Instead of direct connection I choose proxy and entered the proxy IP and prort. It downloaded and installed updates. I had to do this a second time. After this jdownloader started completely.

Next step is to use it, i'll get back in some minutes.

[jlesage]

@MeisterBAP, you issue is different. It's probably better to create a new issue if needed.

[jlesage]

@liuk4friends, it's clear. 22.11.1 has a different problem, but I would like first to understand why you get an error with 1.7.2 (the same as originally posted).

Could you provide the output of the following commands:

docker inspect <container name>

docker exec <container name> ls -l /

[MeisterBAP]

I am not sure if it is really different. If liuk4friends has his problem with a fresh install, than i am sure it is a different problem. But if he is using a backup of his 1.7.2 without updating than it might end up the same.

I can confirm that at least I am not possible to install this container anymore (tested with latest down to 1.6.0) when using direct connection. When using a proxy it works without any problems. With proxy settings my container is working again.

[jlesage]

The original issue is about temporary directory that fails to be created, while yours is about failure to reach the Internet. Note that if you normally need to use a proxy on your network, then the container should also need it. But if other applications or machines on your network don't need it, then the container's network settings might have to be reviewed (e.g. are you using the default bridge network?).

[MeisterBAP]

Call me stupid, but as far as I see this topic its origin is about not beeing able to update:

I know my network very well. When I installed this container I used the terminal connection to assure that the container has full outbound internet access. Unfortunatelly it was not possible to finish the jdownloader installation because it was not able to connect to update.artwork.org.

When using a proxy instead of direct connection it is working. For me this is ok and don't need more help at this time. But looking at the original topic and the messages of other users like "liuk4friends" I have the feeling that there might be a problem with direct connection on QNAP devices.

Anyway, your are doing a great job and I am very thankful.

[liuk4friends]

Could you provide the output of the following commands:

ok

docker inspect <container name>

https://pastebin.com/REQ0acVX

docker exec <container name> ls -l /

https://pastebin.com/iXJxdAXk

Please, let me know when I could delete all these pastebin Thank you for all your efforts

[jlesage]

The pastebin for the docker inspect command output is not accessible:

Error, this is a private paste or is pending moderation. If this paste belongs to you, please login to Pastebin to view it.`

[liuk4friends]

Strange. It is public.

I have edited it and saved it again as public. May you try again?

[jlesage]

Same thing :(

[liuk4friends]

I believe that the problem was not the "public/private" setting of Pastebin website but rather the "pending moderation" by their administrators. I've uploaded another time my "docker inspect result" on Pastebin but also the new version is in "pending moderation" state.

I have no idea how much time it will be "rest" this way so I think that the best is to paste it entirely here:

content deleted by author

[jlesage]

It's strange, the /tmp folder doesn't have the correct permissions. I'm not sure why.

Could you provide the output of the following commands:

docker run --rm jlesage/jdownloader-2 ls -l /
docker run --rm jlesage/jdownloader-2:v1.7.2 ls -l /