Sonarr High CPU

Nicholas_Britton · December 30, 2023, 2:47pm

Sonarr version (exact version): Linuxserver.io version:- 4.0.0.741-ls219
Mono version (if Sonarr is not running on Windows):
OS: Docker - Synology DSM 6.3
Debug logs:
Description of issue: After update via watchtower the app is unresponsive, and i see alot of ping commands.

Please let me know what logs would be good for this type of problem, and i am happy to provide.

atomicpunk · January 3, 2024, 11:10pm

I am experiencing the same issue. OS: Synology DSM 6.2.4 with the latest Sonarr V4. Since the update to V4 I am getting 2 processes of curl -sL http://localhost:8989/ping at the same time each utilizing ~23% cpu. And now I am having the same issue with sabnzbd v4.2

I am also running the latest version of radarr and it doesn’t have this issue.

PS
I did a fresh install, and the issue continues.

UPDATE:
I switched to hotio image and the problem was solved. 1% cpu usage at idle. There must be an issue with the linuxserver image.

ilike2burnthing · January 4, 2024, 4:26am

github.com/linuxserver/docker-sonarr

[BUG] Curl stuck at 100% usage on a core

opened 10:32AM - 03 Jan 24 UTC

closed 10:34AM - 03 Jan 24 UTC

arkangelll13

### Is there an existing issue for this? - [X] I have searched the existing iss…ues ### Current Behavior Happy new year everyone! Since the latest update to version 4.0.0.748 (1st of January) I'm seeing a curl process being stuck using 100% of a single core on my Synology NAS. If I kill the process, it comes back, so something is obviously restarting it. This is the most I could gather about it. |-containerd-shim-+-s6-svscan-+-rc.init---s6-rc---s6-svlisten1---s6-ftrigrd | | |-s6-notifyonchec-+-check---check-+-curl | | | | `-jq | | | `-s6-ftrigrd | | |-s6-supervise---s6-linux-init-s | | |-s6-supervise---s6-ipcserverd | | |-s6-supervise | | |-s6-supervise---busybox | | `-s6-supervise---Sonarr---26*[{Sonarr}] Here is a picture of the container creation, since it was done on the GUI. ![image](https://github.com/linuxserver/docker-sonarr/assets/34684661/9bd1d1ef-906d-4f99-92c7-99adf9bbd856) Could you please advise if I should go to Sonarr developers directly or you can look into it? Thank you. ### Expected Behavior Not running the core to 100% ### Steps To Reproduce Starting the Sonarr container. (Tested with a separate, completely new installation as well) ### Environment ```markdown - OS: (Synology) DSM 7.2.1-69057 Update 3 - How docker service was installed: Built-in package manager ("Container Manager") - Docker: 20.10.23-1437 ``` ### CPU architecture x86-64 ### Docker creation ```bash --- version: "2.1" services: sonarr: image: lscr.io/linuxserver/sonarr container_name: sonarr environment: - PUID=1030 - PGID=100 - TZ=Europe/Budapest volumes: - /volume1/docker/Sonarr:/config - /volume1/Videos/Series:/series - /volume1/Videos/Animated_Series:/animated - /volume1/Downloads/Sonarr:/downloads ports: - 8999:8989 restart: unless-stopped (Stole from another bug report and filled with my own variables, but I've also attached a screenshot) ``` ### Container logs ```bash sonarr date,stream,content 2024/01/03 11:15:00,stdout,crond[145]: USER root pid 403 cmd run-parts /etc/periodic/15min 2024/01/03 11:00:00,stdout,crond[145]: USER root pid 321 cmd run-parts /etc/periodic/hourly 2024/01/03 11:00:00,stdout,[39;49mcrond[145]: USER root pid 320 cmd run-parts /etc/periodic/15min 2024/01/03 10:57:36,stdout,"[39;49m[39;49m[37m[Info] RssSyncService: RSS Sync Completed. Reports found: 197, Reports grabbed: 0 " 2024/01/03 10:57:34,stdout,[39;49m[39;49m[37m[Info] DownloadDecisionMaker: Processing 197 releases 2024/01/03 10:57:34,stdout,[39;49m[39;49m[35m[Warn] Torznab: Indexer The Pirate Bay (Prowlarr) rss sync didn't cover the period between 1/3/2024 8:42:47AM and 1/3/2024 8:53:16AM UTC. Search may be required. 2024/01/03 10:57:32,stdout,[39;49m[37m[Info] RssSyncService: Starting RSS Sync 2024/01/03 10:45:00,stdout,[39;49mcrond[145]: USER root pid 234 cmd run-parts /etc/periodic/15min 2024/01/03 10:36:31,stdout,[39;49m[39;49m[37m[Info] Microsoft.Hosting.Lifetime: Content root path: /app/sonarr/bin 2024/01/03 10:36:31,stdout,[39;49m[39;49m[37m[Info] Microsoft.Hosting.Lifetime: Hosting environment: Production 2024/01/03 10:36:31,stdout,[39;49m[39;49m[37m[Info] Microsoft.Hosting.Lifetime: Application started. Press Ctrl+C to shut down. 2024/01/03 10:36:27,stdout,[39;49m[39;49m[37m[Info] Microsoft.Hosting.Lifetime: Now listening on: http://[::]:8989 2024/01/03 10:36:25,stdout,[39;49m[39;49m[37m[Info] MigrationController: *** Migrating data source=/config/logs.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 2024/01/03 10:36:25,stdout,[39;49m[39;49m[37m[Debug] Microsoft.Extensions.Hosting.Internal.Host: Hosting starting 2024/01/03 10:36:25,stdout,[39;49m[39;49m[37m[Debug] MigrationController: Took: 00:00:00.6874819 2024/01/03 10:36:24,stdout,[39;49m[39;49m[37m[Info] MigrationController: *** Migrating data source=/config/sonarr.db;cache size=-20000;datetimekind=Utc;journal mode=Wal;pooling=True;version=3;busytimeout=100 *** 2024/01/03 10:36:24,stdout,[39;49m[39;49m[37m[Info] AppFolderInfo: Data directory is being overridden to [/config] 2024/01/03 10:36:23,stdout,[39;49m[39;49m[37m[Info] AppFolderInfo: Data directory is being overridden to [/config] 2024/01/03 10:36:23,stdout,[39;49m[39;49m[37m[Debug] Bootstrap: Console selected 2024/01/03 10:36:23,stdout,[39;49m[39;49m[37m[Info] AppFolderInfo: Data directory is being overridden to [/config] 2024/01/03 10:36:23,stdout,[?1h=[39;49m[37m[Info] Bootstrap: Starting Sonarr - /app/sonarr/bin/Sonarr - Version 4.0.0.748 2024/01/03 10:36:21,stdout,"crond[145]: crond (busybox 1.36.1) started, log level 5 " 2024/01/03 10:36:21,stdout,"[custom-init] No custom files found, skipping... " 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout,─────────────────────────────────────── 2024/01/03 10:36:21,stdout,User GID: 100 2024/01/03 10:36:21,stdout,User UID: 1030 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout,─────────────────────────────────────── 2024/01/03 10:36:21,stdout,GID/UID 2024/01/03 10:36:21,stdout,─────────────────────────────────────── 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout,https://www.linuxserver.io/donate/ 2024/01/03 10:36:21,stdout,To support LSIO projects visit: 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout,Sonarr: https://sonarr.tv/donate 2024/01/03 10:36:21,stdout,To support the app dev(s) visit: 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout,─────────────────────────────────────── 2024/01/03 10:36:21,stdout, Brought to you by linuxserver.io 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout, ╚══════╝╚══════╝╚═╝ ╚═════╝ 2024/01/03 10:36:21,stdout, ███████╗███████║██║╚██████╔╝ 2024/01/03 10:36:21,stdout, ██║ ╚════██║██║██║ ██║ 2024/01/03 10:36:21,stdout, ██║ ███████╗██║██║ ██║ 2024/01/03 10:36:21,stdout, ██║ ██╔════╝██║██╔═══██╗ 2024/01/03 10:36:21,stdout, ██╗ ███████╗██╗ ██████╗ 2024/01/03 10:36:21,stdout, 2024/01/03 10:36:21,stdout,─────────────────────────────────────── 2024/01/03 10:36:21,stdout,usermod: no changes 2024/01/03 10:36:21,stdout,[migrations] no migrations found 2024/01/03 10:36:21,stdout,[migrations] started ```

system · March 4, 2024, 4:26am

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.