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

[BUG] qt6-qtbase 6.6.2-r1 regression on Asustor NAS #301

Closed
1 task done
bloodysneaker opened this issue Mar 28, 2024 · 5 comments
Closed
1 task done

[BUG] qt6-qtbase 6.6.2-r1 regression on Asustor NAS #301

bloodysneaker opened this issue Mar 28, 2024 · 5 comments

Comments

@bloodysneaker
Copy link

bloodysneaker commented Mar 28, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Following the 4.6.4 update, my qBT installation starts as if it were a clean one. It lost every settings and every torrents.

Restoring an old config folder backup and recreating the container with qbittorrent:4.6.3 image solves the issue

Expected Behavior

Like every past updates, I'd expect that all my settings will be ported to the new container

Steps To Reproduce

  1. Stop the "outdated" container
  2. Repull the :latest image
  3. Recreate the container with the Portainer Recreate function
  4. The updated container starts like a celan installation

Environment

- OS: Asustor ADM 4.2.7
- How docker service was installed: by Asustor AppCentral 
- Docker managment: Portainer.io 2.19.4 BE

CPU architecture

arm64

Docker creation

First installation was made with Asustor AppCentral, then used portainer to repull and recreate the container to update it
Config screenshot https://imgur.com/a/muQQoBO

This is the original configuration made by AppCentral script
docker create -i -t --name=qBittorrent \
	-p 18181:18181 \
	-p 6881:6881 \
	-p 6881:6881/udp \
	-e PUID=$C_UID -e PGID=$ADMIN_GID \
	-e WEBUI_PORT=18181 \
	-v /etc/localtime:/etc/localtime:ro \
	-v /usr/builtin/etc/certificate/:/sslcerts/:ro \
	-v /share/Docker/qBittorrent/config:/config:rw \
	-v /share/Download:/downloads:rw \
	-v /share:/shared:rw \
	--restart unless-stopped \
	linuxserver/qbittorrent:latest
  	

Container logs

The TLS error are obviously caused by the lost of configuration path for the certificates

[migrations] started
[migrations] no migrations found
───────────────────────────────────────
      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝
   Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID:    999
User GID:    999
───────────────────────────────────────
[custom-init] No custom files found, skipping...
crond[148]: crond (busybox 1.36.1) started, log level 5
QIODevice::seek (QFile, "/config/qBittorrent/logs/qbittorrent.log"): Cannot call seek on a sequential device
WebUI will be started shortly after internal preparations. Please wait...
qt.core.plugin.loader: /usr/lib/qt6/plugins/tls/libqcertonlybackend.so: failed to map to memory: Invalid argument
qt.core.plugin.loader: /usr/lib/qt6/plugins/tls/libqopensslbackend.so: failed to map to memory: Invalid argument
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No TLS backend is available
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No TLS backend is available
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:18181
The WebUI administrator username is: ************
The WebUI administrator password was not set. A temporary password is provided for this session: ************
You should set your own password in program preferences.
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No TLS backend is available
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: No TLS backend is available
qt.network.ssl: No functional TLS backend was found
qt.network.ssl: QSslSocket::connectToHostEncrypted: TLS initialization failed
Connection to localhost (127.0.0.1) 18181 port [tcp/*] succeeded!
[ls.io-init] done.
crond[148]: USER root pid 194 cmd run-parts /etc/periodic/15min
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@bloodysneaker
Copy link
Author

Here the qBittorrent internal logs

(N) 2024-03-28T15:29:08 - qBittorrent v4.6.4 started
(N) 2024-03-28T15:29:08 - Using config directory: /config/qBittorrent
(N) 2024-03-28T15:29:08 - Trying to listen on the following list of IP addresses: "0.0.0.0:35449,[::]:35449"
(I) 2024-03-28T15:29:08 - Peer ID: "-qB4640-"
(I) 2024-03-28T15:29:08 - HTTP User-Agent: "qBittorrent/4.6.4"
(I) 2024-03-28T15:29:08 - Distributed Hash Table (DHT) support: ON
(I) 2024-03-28T15:29:08 - Local Peer Discovery support: ON
(I) 2024-03-28T15:29:08 - Peer Exchange (PeX) support: ON
(I) 2024-03-28T15:29:08 - Anonymous mode: OFF
(I) 2024-03-28T15:29:08 - Encryption support: ON
(W) 2024-03-28T15:29:08 - Failed to parse Categories configuration. File: "/config/qBittorrent/categories.json". Error: "illegal value"
(I) 2024-03-28T15:29:09 - Successfully listening on IP. IP: "127.0.0.1". Port: "TCP/35449"
(I) 2024-03-28T15:29:09 - Successfully listening on IP. IP: "127.0.0.1". Port: "UTP/35449"
(I) 2024-03-28T15:29:09 - Successfully listening on IP. IP: "172.168.0.2". Port: "TCP/35449"
(I) 2024-03-28T15:29:09 - Successfully listening on IP. IP: "172.168.0.2". Port: "UTP/35449"
(I) 2024-03-28T15:29:08 - UPnP/NAT-PMP support: ON
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "8993f785f4244e8384f241a6cecb881988e6de48". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "ef69be8a4047d60a102e6cf539f7b52a4a19e57b". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "0c571447fd5aa45c356b525d638e5760dee9c1fc". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "9863925a39047b56b0669f260bd3b40db215e59d". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "fb3d49d090549017a36999e62e0cc4bca5d842c8". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "9e9da91225eebc47a8ddcf97f0ce648859e77a69". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "d1391f8d2c193b0689bc7dfba12e6a48d9c121c9". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "a00d8b08e1069ca0fe49ef6f435a79648673bd05". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "3c43a9905f1ca415081e3cba02e94bb3924e90b4". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "4b8df77b1a05ddbb246bde883db1b51f32842378". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(C) 2024-03-28T15:29:09 - Failed to resume torrent. Torrent: "8d097045d04a03bf83af3eb31e68466e3cc9cf3c". Reason: "Cannot parse resume data: unexpected end of file in bencoded string"
(W) 2024-03-28T15:29:09 - Couldn't load IP geolocation database. Reason: Unknown error
(W) 2024-03-28T15:29:09 - Failed to parse Watched Folders configuration from /config/qBittorrent/watched_folders.json. Error: "illegal value"
(W) 2024-03-28T15:29:09 - Failed to parse RSS session data. File: "/config/qBittorrent/rss/feeds.json". Error: "illegal value"
(N) 2024-03-28T15:29:10 - Using built-in WebUI.
(W) 2024-03-28T15:29:10 - Couldn't load WebUI translation for selected locale (C).
(N) 2024-03-28T15:29:10 - WebUI: Now listening on IP: *, port: 18181
(W) 2024-03-28T15:29:13 - Couldn't download IP geolocation database file. Reason: An unknown network-related error was detected
(I) 2024-03-28T15:29:16 - Detected external IP. IP: "my external IP"

@j0nnymoe
Copy link
Member

Does it work if you roll back the image? From our smoke tests, all seems to be ok: https://ci-tests.linuxserver.io/linuxserver/qbittorrent/latest/index.html
It seems like it's having issues accessing your files or they're corrupted.

Note, no one within the team has an asustor nas device plus we do not support/recommend portainer for our containers.

@bloodysneaker
Copy link
Author

Made some other tests.
Clean deploy of the container with this docker create, so no "corrupted" configuration imported.

docker create -i -t --name=qBittorrent_464 \
	-p 18181:18181 \
	-p 6881:6881 \
	-p 6881:6881/udp \
	-e PUID=$C_UID -e PGID=$ADMIN_GID \
	-e WEBUI_PORT=18181 \
	-v /etc/localtime:/etc/localtime:ro \
	-v /usr/builtin/etc/certificate/:/sslcerts/:ro \
	-v /share/Docker/qBittorrent/config_464:/config:rw \
	-v /share/Download:/downloads:rw \
	-v /share:/shared:rw \
	--restart unless-stopped \
	linuxserver/qbittorrent:latest

It works fine until I restart the container, in that case the configuration is resetted again
The log is exactly the same as before.
I don't have a clue, at this point I suspect some regression on the application side

@bloodysneaker
Copy link
Author

bloodysneaker commented Mar 28, 2024

Ok, I can confirm it's some kind of regression. I've tried manually updating packages starting form 4.6.3 image.
Updating qt6-qtbase from 6.6.2-r0 to 6.6.2-r1 broke my installation.
I'm closing the issue since this is the wrong repo, please forgive me for the mistake

Workaround to use 4.6.4 without updating qt6-qtbase packages:
Start from :4.6.3 image:

docker exec -it container-name sh
apk add qt6-qtbase-sqlite=6.6.2-r0
apk add qt6-qtbase=6.6.2-r0
apk add -U --upgrade --no-cache qbittorrent-nox==4.6.4-r0
exit

Restart the container et voilà, qBT updated and working fine

@bloodysneaker bloodysneaker changed the title [BUG] Configuration lost after 4.6.4 update on arm64 [BUG] qt6-qtbase 6.6.2-r1 regression on Asustor NAS Mar 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants