Medusa icon indicating copy to clipboard operation
Medusa copied to clipboard

Published 20 hours ago • verified publisher icon pymedusa

Intermittent high CPU use

Open johnvick opened this issue 1 year ago • 46 comments

Medusa Info: Branch: master Commit: e4870f8f4a322e67c77434597ccc09aa6524aa05 Version: 1.0.13 Database: 44.19 Python Version: 3.10.11 (main, Apr 6 2023, 01:16:54) [GCC 12.2.1 20220924] SSL Version: OpenSSL 3.0.8 7 Feb 2023 OS: Linux-6.2.11-2-pve-x86_64-with Locale: en_US.UTF-8 Timezone: NZST

User: abc Program Folder: /app/medusa Config File: /config/config.ini Database File: /config/main.db Cache Folder: /config/cache Log Folder: /config/Logs Arguments: --nolaunch --datadir /config Runs in Docker: Yes

A recent change is that every so often Medusa uses 100% of two CPUs on the six core Proxmox Ubuntu VM it is running on. The fan noise alerts me to this. At these time web interface cannot be accessed. Restarting the container fixes it for a while.

The only abnormality in the logs is :

2023-05-13 17:47:29 INFO SEARCHQUEUE-DAILY-SEARCH :: [e4870f8] Using daily search providers /app/medusa/ext/bs4/builder/init.py:545: XMLParsedAsHTMLWarning: It looks like you're parsing an XML document using an HTML parser. If this really is an HTML document (maybe it's XHTML?), you can ignore or filter this warning. If it's XML, you should know that using an XML parser will be more reliable. To parse this document as XML, make sure you have the lxml package installed, and pass the keyword argument features="xml" into the BeautifulSoup constructor. warnings.warn(

Any clues to fix this? Thanks.

johnvick avatar May 13 '23 06:05 johnvick

Hello, I have the same problem with my docker image https://github.com/jee-r/docker-medusa

I don't know what produces this cpu consumption

jee-r avatar May 13 '23 08:05 jee-r

@johnvick Do you know which provider is causing that warning? Try disabling it.

medariox avatar May 13 '23 10:05 medariox

Same problem with my Docker container. High CPU use alert, and it's the Medusa container. I can still access Medusa when this happens. A restart of the container fixed it until the next morning. Seems to be something happening overnight.

GldRush98 avatar May 13 '23 14:05 GldRush98

I'm not sure how to work out which is the offending provider?

The log below is from overnight - similar entries recur repeatedly. AniDB is mentioned.

2023-05-14 00:24:25 WARNING GENERICQUEUESCHEDULER-UPDATE-RECOMMENDED-ANILIST :: [e4870f8] Could not parse AniDB show, with exception: Traceback (most recent call last): File "/app/medusa/medusa/show/recommendations/anilist.py", line 95, in fetch_popular_shows recommended_show = self._create_recommended_show(show) File "</app/medusa/ext/decorator.py:decorator-gen-54>", line 2, in _create_recommended_show File "/app/medusa/ext/dogpile/cache/region.py", line 1577, in get_or_create_for_user_func return self.get_or_create( File "/app/medusa/ext/dogpile/cache/region.py", line 1042, in get_or_create with Lock( File "/app/medusa/ext/dogpile/lock.py", line 185, in enter return self._enter() File "/app/medusa/ext/dogpile/lock.py", line 87, in _enter value = value_fn() File "/app/medusa/ext/dogpile/cache/region.py", line 977, in get_value value = self._get_from_backend(key) File "/app/medusa/ext/dogpile/cache/region.py", line 1265, in _get_from_backend self.backend.get_serialized(key) File "/app/medusa/ext/dogpile/cache/backends/file.py", line 217, in get_serialized with self._dbm_file(False) as dbm_obj: File "/usr/lib/python3.10/contextlib.py", line 135, in enter return next(self.gen) File "/app/medusa/ext/dogpile/cache/backends/file.py", line 213, in _dbm_file with dbm.open(self.filename, "w" if write else "r") as dbm_obj: File "/usr/lib/python3.10/dbm/init.py", line 91, in open raise error[0]("db type is {0}, but the module is not " dbm.error: db type is dbm.gnu, but the module is not available Traceback (most recent call last): File "/app/medusa/medusa/show/recommendations/anilist.py", line 95, in fetch_popular_shows recommended_show = self._create_recommended_show(show) File "</app/medusa/ext/decorator.py:decorator-gen-54>", line 2, in _create_recommended_show File "/app/medusa/ext/dogpile/cache/region.py", line 1577, in get_or_create_for_user_func return self.get_or_create( File "/app/medusa/ext/dogpile/cache/region.py", line 1042, in get_or_create with Lock( File "/app/medusa/ext/dogpile/lock.py", line 185, in enter return self._enter() File "/app/medusa/ext/dogpile/lock.py", line 87, in _enter value = value_fn() File "/app/medusa/ext/dogpile/cache/region.py", line 977, in get_value value = self._get_from_backend(key) File "/app/medusa/ext/dogpile/cache/region.py", line 1265, in _get_from_backend self.backend.get_serialized(key) File "/app/medusa/ext/dogpile/cache/backends/file.py", line 217, in get_serialized with self._dbm_file(False) as dbm_obj: File "/usr/lib/python3.10/contextlib.py", line 135, in enter return next(self.gen) File "/app/medusa/ext/dogpile/cache/backends/file.py", line 213, in _dbm_file with dbm.open(self.filename, "w" if write else "r") as dbm_obj: File "/usr/lib/python3.10/dbm/init.py", line 91, in open raise error[0]("db type is {0}, but the module is not " dbm.error: db type is dbm.gnu, but the module is not available 2023-05-14 00:24:25 WARNING GENERICQUEUESCHEDULER-UPDATE-RECOMMENDED-ANILIST :: [e4870f8] Could not parse AniDB show, with exception: Traceback (most recent call last): File "/app/medusa/medusa/show/recommendations/anilist.py", line 95, in fetch_popular_shows

johnvick avatar May 13 '23 19:05 johnvick

Ok so it's not just me! Caused a bit of havoc on my proxmox machine.

CONTAINER ID NAME CPU % MEM USAGE / LIMIT MEM % NET I/O BLOCK I/O PIDS 8a949e0e32cb medusa 95.30% 147.3MiB / 2.745GiB 5.24% 7.04MB / 1.9MB 257MB / 84.4MB 26

jaxjexjox avatar May 13 '23 23:05 jaxjexjox

If there's any information I can provide to solve this, let me know.

jaxjexjox avatar May 14 '23 05:05 jaxjexjox

Also suddenly having issues adding new shows too, may be unrelated.

jaxjexjox avatar May 14 '23 07:05 jaxjexjox

Try deleting the .dbm files in your cache folder and restart.

medariox avatar May 14 '23 10:05 medariox

Thanks I tried this a few hours ago and also cleaned out the old db files, all good so far.

johnvick avatar May 14 '23 10:05 johnvick

I would also enable these 2 settings if you haven't already:

General > Misc > Recommended shows cache and Search Settings > Episode Search > General Search Settings cache trimming

medariox avatar May 14 '23 12:05 medariox

Have done thanks I'll report back, it has been firing up around 5PM NZ time.

johnvick avatar May 14 '23 18:05 johnvick

No luck I am afraid around 5:40 pm fans started up Medusa using 100% CPU on 2 of 6 cores. Restart the container all quiet. Nothing unusual in the logs but just realised I did not have debug logs enabled which I have now done.

johnvick avatar May 15 '23 06:05 johnvick

Same here - 100% 2 cores, web interface unresponsive.

Didn't have any luck purging the cache files, nor restoring from a month old ZFS snapshot

dcrdev avatar May 15 '23 06:05 dcrdev

Same issue here, GUI becomes unresponsive

GamerGun avatar May 15 '23 15:05 GamerGun

Mine has consistently been starting around 3:30am CDT (America/Chicago) time.

I tried the above cache purge and settings changes, and this did not help.

I am not seeing any errors or anything unusual in the logs around this time. Just standard items from SHOWUPDATER, POSTPROCESSOR, and SEARCHQUEUE-DAILY-SEARCH doing their normal routine things.

I have only 4 providers enabled. Is there commonality with any one else seeing this? -Rarbg -Jackett -Eztv -Limetorrents

I exclusively run torrents, handled by Transmission. Medusa has otherwise been working as expected, episodes are still being downloaded and processed.

This started ~3:30am 5/12/2023 and has happened every night around the same time since then. I have enabled the debug logs as of now and will see if they show anything additional tomorrow as I'm positive it will happen again tonight.

GldRush98 avatar May 15 '23 15:05 GldRush98

@GldRush98 Sounds like the Backlog Search running (by default, it runs every 12 hours). How many items do you have in the backlog? If you have a huge backlog, it's normal to see CPU usage spike until the search is done.

medariox avatar May 15 '23 15:05 medariox

That is not the cause as we are not talking about a CPU "spike" until the search is done. We are talking about sustained 100% CPU use until the Medusa container is killed. Typically by the time I get around to killing it the container has pegged the CPU at 100% for 6+ hours straight.

FWIW, there are currently all of 3 episodes in the backlog, and all are recent episodes that just haven't downloaded yet and will likely clear out in the next few days. There is nothing unusual/unexpected in the backlog.

GldRush98 avatar May 15 '23 16:05 GldRush98

Got it, in that case you should be able to post the debug logs from the moment the issue starts until the reboot. That would probably help. Please no more +1s without debug logs.

medariox avatar May 15 '23 16:05 medariox

I wonder, but I guess this can be related to #11218

bassduh avatar May 15 '23 19:05 bassduh

I think you may be on to something there. I just checked my "Server Status" page and my "Show Update" process start time says "03:12:00". About 20-25 minutes before I get the maxed out CPU alerts. This would make sense if one show is causing a loop some place it probably takes a bit for the loop to build up enough times that it starts really chewing the CPU up. Is there a way to trigger the Show Update process now? This will tell me pretty quick if this is the cause.

edit: I believe I triggered the Update for all shows via Mass Update. Will report if I see the issue pop up soon. I have debug log turned on but I'm concerned that I don't see any debug messages in my log. Not sure...

GldRush98 avatar May 15 '23 20:05 GldRush98

Is there a way to trigger the Show Update process now? This will tell me pretty quick if this is the cause.

edit: I believe I triggered the Update for all shows via Mass Update. Will report if I see the issue pop up soon. I have debug log turned on but I'm concerned that I don't see any debug messages in my log. Not sure...

You could hit "Force Full Update" on a Show's page.

And have you change the "Logging level" to "Debug" on the View log page?

bassduh avatar May 15 '23 20:05 bassduh

Yup, I have hit the bug. I now believe this is the same as #11218 referenced above. Chicago Med returning a null data field is causing it in my situation: https://api.thetvdb.com/series/295640/episodes/query?page=2

edit: The debug log started working after I restarted the container again and confirmed...:

2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002) 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] GET URL: https://api.thetvdb.com/series/295640/episodes/query?page=2 [Status: 200] 2023-05-15 15:53:19 DEBUG SHOWQUEUE-UPDATE :: [e094759] User-Agent: Medusa/1.0.13 (Linux; 4.4.180+; 425125f3-f362-11ed-84ae-0242ac110002)

etc....

GldRush98 avatar May 15 '23 20:05 GldRush98

Debug log gives below repeatedly - show is BBC Documentaries.

2023-05-16 17:56:16 DEBUG SHOWUPDATER :: [e4870f8] User-Agent: Medusa/1.0.13 (Linux; 6.2.11-2-pve; 64f1362c-f3a7-11ed-a36c-0242ac16000b) 2023-05-16 17:56:16 DEBUG SHOWUPDATER :: [e4870f8] GET URL: https://api.thetvdb.com/series/79660/episodes/query?page=12 [Status: 200]

johnvick avatar May 16 '23 05:05 johnvick

Around 5am my time in Aus it kicked in for me, 100% CPU just totally thrashed. I tend to update my docker containers regularly so I couldn't identify precisely when this first began.

I also had issues adding a new show, unsure if it was just the show but it failed.

jaxjexjox avatar May 17 '23 00:05 jaxjexjox

Yeah, don't use TVDB any more, pick a different indexer. CPU bug is triggered by an existing show that's trying to pull bad data from TVDB's broken API.

GldRush98 avatar May 17 '23 00:05 GldRush98

Funny you should mention that.......... I have no choice.

https://i.imgur.com/2nDdFsb.png

jaxjexjox avatar May 17 '23 00:05 jaxjexjox

which indexer would people recommend to use instead of tvdb with its broken API?

spattersTatt avatar May 18 '23 08:05 spattersTatt

Any should be fine. I switched the majority of mine to tvmaze with a few tmdb and imdb in there if I didn't like how the episodes were listed on tvmaze.

GldRush98 avatar May 18 '23 13:05 GldRush98

Funny you should mention that.......... I have no choice.

https://i.imgur.com/2nDdFsb.png

You need to remove the show first before being able to add it with a different indexer. Or you could use Manage > Change Indexer as well.

medariox avatar May 18 '23 13:05 medariox

did the bulk change tool, and then all my archoved shows were listed as WANTED and it started trying to grab them ALL again

spattersTatt avatar May 18 '23 23:05 spattersTatt