Failed Migration From Windows to Linux

Linux specific questions, problems.
Post Reply
ticedoff8
Member
Member
Posts: 21
Joined: Sat Jul 20, 2024 1:16 am

Failed Migration From Windows to Linux

Post by ticedoff8 »

I started this thread on the docker forum, but it turns out it may be more of a migration issue from Windows to Linux.

The main issue is that even though the docker image starts, the WebUI completely dead. The browser times out and will not connect with a simple "... refused to connect".

The Windows system was running the last version of qBittorrent before 5.0 was released and the docker image is the same.
I copied all the qBt config files off the Windows 10 machine and into a Linux directory that is being used for config directories.
I already changed the names of qBittorrent-data.ini and qBittorrent.ini to qBittorrent-data.conf and qBittorrent.conf.

There are no qBittorrent logs being generated when I start the docker container. I edited the qBittorrent.conf file to change the log file destination to the NAS config/qBittorrent/logs and still no logs.
The only log I have comes from docker:

Code: Select all

[root@docker01 qBittorrent]# docker logs qbt-win
[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:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 4.6.7-r0-ls352
Build-date: 2024-09-22T06:52:38+00:00
───────────────────────────────────────

[custom-init] No custom files found, skipping...
QtSingleCoreApplication: listen on local socket failed, QLocalServer::listen: Unknown error 5
WebUI will be started shortly after internal preparations. Please wait...

******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8084

The WebUI administrator username is: admin
The WebUI administrator password was not set. A temporary password is provided for this session: ZrqzgL4yS
You should set your own password in program preferences.
[root@docker01 qBittorrent]#
I can't find anything about "QtSingleCoreApplication: listen on local socket failed, QLocalServer::listen: Unknown error 5".
This error comes up when I start one of the known-good qbt docker images.

Something that may be important missing lines that are in a docker log from a known-good image:

Code: Select all

...
...
******** Information ********
To control qBittorrent, access the WebUI at: http://localhost:8080

Connection to localhost (::1) 8080 port [tcp/http-alt] succeeded!
[ls.io-init] done.
[root@docker01 qBittorrent]#
I assume this is a startup script that may be stuck.

The Windows qBittorrent.conf file is much (much) larger than the qBittorant.conf file that is created by a fresh docker image. There is (maybe) 50 lines in a docker image's file vs 300 or 400 in the Windows file. I assume that's mainly due to age and the built-in GUI that comes with Windows.

I'm not at the point where I'm worried about the BT_Backup folder.
Unless I can get the WebUI running, I'll have to bail on the idea of migrating to Linux and be stuck with Windows.

Background:
I started qBittorrent on an old Windows 7 (64bit) laptop several years ago. When the laptop got too old and tired, I successfully moved qBt to a newer desktop system running Windows 10 (64bit) without losing any torrents, seeds or stalled download.
The desktop system cannot be upgraded to Windows 11, so I want to move to a docker host I have setup on Rocky Linux.
I played with the qBt docker images and proved that I could get a couple qBt images running using different WebUI and Torrenting ports for each without conflicts.

The qBt temp directories, downloads, .torrent files are still on a NAS (was the G-drive) and the qBittorrent config stuff was in the standard Windows locations.
I copied all the files and directories and keep them as backups on the NAS. But they are all still in Windows format.
c:\Users\<Username>\AppData\local\qBittorrent

Code: Select all

Directory of K:\qBt-Config_Backups\qBt_Config-Alien_Backup-Windows\Users;me.mine-US;AppData;Local\qBittorrent

10/12/2024  01:35 PM    <DIR>          .
10/12/2024  01:34 PM    <DIR>          ..
10/12/2024  01:35 PM    <DIR>          BT_backup
12/16/2019  10:49 PM    <DIR>          cache
10/12/2024  01:35 PM    <DIR>          GeoDB
10/12/2024  01:35 PM    <DIR>          GeoIP
10/12/2024  01:35 PM    <DIR>          logs
10/12/2024  01:35 PM    <DIR>          nova3
10/12/2024  01:35 PM    <DIR>          rss
c:\Users\<Username>\AppData\roaming\qBittorrent

Code: Select all

 Directory of K:\qBt-Config_Backups\qBt_Config-Alien_Backup-Windows\Users;me.mine-US;AppData;Roming\qBittorrent

10/12/2024  03:16 PM    <DIR>          .
10/12/2024  03:16 PM    <DIR>          ..
09/24/2024  04:13 PM             1,592 categories.json
10/04/2024  12:25 PM               199 qBittorrent-data.ini
10/04/2024  12:26 PM            16,899 qBittorrent.ini
10/12/2024  03:16 PM    <DIR>          rss
10/19/2023  04:33 PM                 4 watched_folders.json
The Linux config folder from the Windows migration and a docker image that has full functionality:

Code: Select all

[root@docker01 qBittorrent]# ls -la
total 32
drwxrwxrwx. 2 root root     0 Dec 12 17:07 .
drwxrwxrwx. 2 root root     0 Dec 11 23:48 ..
drwxrwxrwx. 2 root root     0 Dec 12 17:07 BT_backup
-rwxrwxrwx. 1 root root  1592 Dec 11 23:48 categories.json
drwxrwxrwx. 2 root root     0 Dec 11 23:54 GeoDB
-rwxrwxrwx. 1 root root     0 Dec 11 23:48 lockfile
drwxrwxrwx. 2 root root     0 Dec 12 11:08 logs
drwxrwxrwx. 2 root root     0 Dec 12 17:05 nova3
-rwxrwxrwx. 1 root root 16571 Dec 12 11:09 qBittorrent.conf
-rwxrwxrwx. 1 root root   200 Dec 12 16:59 qBittorrent-data.conf
drwxrwxrwx. 2 root root     0 Dec 11 23:48 rss
-rwxrwxrwx. 1 root root     4 Dec 11 23:48 watched_folders.json

[root@docker01 qBittorrent]# ls -la ../../qbt-prime.appdata/qBittorrent/
total 16
drwxrwxrwx. 2 root root    0 Dec 12 11:26 .
drwxrwxrwx. 2 root root    0 Dec 11 21:30 ..
drwxrwxrwx. 2 root root    0 Dec 12 11:26 BT_backup
-rwxrwxrwx. 1 root root  343 Dec 11 21:30 categories.json
drwxrwxrwx. 2 root root    0 Dec 11 21:30 GeoDB
drwxrwxrwx. 2 root root    0 Dec 11 21:30 logs
drwxrwxrwx. 2 root root    0 Dec 11 21:30 nova3
-rwxrwxrwx. 1 root root 2102 Dec 12 11:26 qBittorrent.conf
-rwxrwxrwx. 1 root root  196 Dec 12 11:26 qBittorrent-data.conf
drwxrwxrwx. 2 root root    0 Dec 12 11:26 rss
-rwxrwxrwx. 1 root root    4 Dec 11 21:30 watched_folders.json
[root@docker01 qBittorrent]#
The docker image is running as UID=1000 GID=1000 and there is a linux user with that GID/UID and it has all the privileges needed.
Keep in mind that a fresh docker image starts right up using this GID/UID and has access to the NAS folders for a new set of qBt support folders.
Post Reply