search

DyonR / docker-qbittorrentvpn

Docker container which runs a qBittorent-nox client with an optional WireGuard or OpenVPN connection
https://hub.docker.com/r/dyonr/qbittorrentvpn/
GNU General Public License v3.0
250 stars 73 forks source link

qbittorrent-nox process takes an unusually long time to start #174

Open ItsLogic opened 1 year ago

ItsLogic commented 1 year ago

I am assuming this is not normal behaviour as there isn't any mention of a long startup time in the readme.

After launching the docker container one of my CPU cores is pinned at 100% usage for about 10 minutes before the qbittorent-nox process is actually started (see STIME in the image below). This usage comes from the start-stop-daemon process. After the qbittorrent-nox process is started the core usage goes back down to a more reasonable 2-3%.

image

The CPU I'm running this on is an i5 7500t which is a bit dated but shouldn't have any issues with launching qbittorrent-nox.

The log shows nothing during the CPU usage. The last thing printed is this which happens about 10 minutes before the process starts:

 2023-04-11 05:14:39.057539 [WARNING] ENABLE_SSL is set to '', SSL is not enabled. This could cause issues with logging if other apps use the same Cookie name (SID).
 2023-04-11 05:14:39.079018 [WARNING] Removing the SSL configuration from the config file...
 2023-04-11 05:14:39.103050 [INFO] A group with PGID 1000 does not exist within this container, adding a group called 'qbittorrent' with PGID 1000
 2023-04-11 05:14:39.185579 [INFO] An user with PUID 1000 does not exist within this container, adding an user called 'qbittorrent user' with PUID 1000
 2023-04-11 05:14:39.295047 [INFO] UMASK defined as '000'
 2023-04-11 05:14:39.318090 [INFO] Starting qBittorrent daemon...
 Logging to /config/qBittorrent/data/logs/qbittorrent.log.
 2023-04-11 05:14:40.348034 [INFO] Started qBittorrent daemon successfully...
 2023-04-11 05:14:40.371101 [INFO] qBittorrent PID: 211
 2023-04-11 05:14:40.393552 [INFO] HEALTH_CHECK_HOST is not set. For now using default host one.one.one.one
 2023-04-11 05:14:40.415068 [INFO] HEALTH_CHECK_INTERVAL is not set. For now using default interval of 300
 2023-04-11 05:14:40.436648 [INFO] HEALTH_CHECK_SILENT is not set. Because this variable is not set, it will be supressed by default
 2023-04-11 05:14:40.459544 [WARNING] RESTART_CONTAINER not defined,(via -e RESTART_CONTAINER), defaulting to 'yes'
 2023-04-11 05:14:40.481741 [INFO] HEALTH_CHECK_AMOUNT is not set. For now using default interval of 1
 2023-04-11 05:14:40.503227 [INFO] HEALTH_CHECK_AMOUNT is set to 1

System info: arch linux: 6.2.10-arch1-1 docker 23.0.3, build 3e7cbfdee1

sebbe662 commented 1 year ago

i have the same issue, but i have disabled the health check variable in the environment section of my docker-compose.yml

Screenshot 2023-04-11 220958