Open mitch71h opened 1 year ago
Same here, multiple times last few nights. As i am still on 1.0.14, because 1.0.15 has a UMASK error
I'm seeing this as well. Latest docker version.
I've enabled debug logs and will report back when I see this again.
What I've already tried:
Observations
Behaviour looks a bit similar to this bug: https://github.com/pymedusa/Medusa/issues/10560
The problem is with the TVDB indexer. You should switch to a different indexer ASAP.
The problem is with the TVDB indexer. You should switch to a different indexer ASAP.
I see. How do I do that? Remove show and re-add with different indexer?
I've been having this issue on & off for about a week; I thought it was me at first, but I manually set a ton of shows to archived, and overnight many hundreds of archived shows have downloaded, and wasted many 100's of GB of data. I was remiss and did not set logging to debug, but will now for when it happens again. For now, I may have to set my downloader to paused and manually release the downloads - not ideal, but c'est la vie!
EDIT: version 1.0.15, commit d45f98c9356f9cc6b819028c2fb52fae709c21dd
Same here, multiple times last few nights. As i am still on 1.0.14, because 1.0.15 has a UMASK error
What is the UMASK error that prevents use of 1.0.15?
I'm on 1.0.13 with hot patches for the recent 'thetvdb' API fixes, so I would like to know what else is at issue in subsequent release that might make moving to them problematic.
thanks in advance
Observations
- Happens with shows that have keyword requirements, and shows without keyword requirements
- Happens to long running (>40 seasons) shows and shows that are more recent
Behaviour looks a bit similar to this bug: #10560
Which indexer(s) are you using? General advice is to migrate away from thetvdb to tvmaze, which I'm slowly doing over time. Slowly, cuz 600 shows take a long time to "Change Indexer" and manually follow up -- it sets all shows to Downloaded, not Archived. See https://github.com/pymedusa/Medusa/issues/11277.
Same here, multiple times last few nights. As i am still on 1.0.14, because 1.0.15 has a UMASK error
What is the UMASK error that prevents use of 1.0.15?
I'm on 1.0.13 with hot patches for the recent 'thetvdb' API fixes, so I would like to know what else is at issue in subsequent release that might make moving to them problematic.
thanks in advance
the UMASK error means i am not able to move the downloads to the tv dir Getting a Permission Denied error. Reverting back to 1.0.14 doesn’t give that error anymore I use UMASK 002 wich should give root accesss, and even then i can’t move Conclusiion is that UMASK doesn’t work on 1.0.15
I suspect the 1.0.14-->1.0.15 changes can't be related to the umask
problem you're experiencing, as the only source code change (shown by https://github.com/pymedusa/Medusa/compare/v1.0.14...v1.0.15) is that one line of code was made dependant on a NULL check in medusa/indexers/tvdbv2/api.py:
before:
last = paged_episodes.links.last
after:
if paged_episodes.links:
last = paged_episodes.links.last
This occurs in two places in that file.
Back on topic: I've changed all my indexers to TVMaze (by removing and re-adding each show with a new indexer), I'll see if the issue pops up again.
Last night i have had no problems, seems stable now
I'm changing my shows over (thetvdb->tvmaze) as well. A bit manual because https://github.com/pymedusa/Medusa/issues/11277 is still a problem, meaning one has to follow up with each show and set episodes that were previously Archived (and get set to Downloaded) back to Archived to avoid re-downloads if the quality settings have changed since initial download.
Also a good opportunity to delete "Ended" shows, so my list is down from 600 to 450 shows so far with more deletions to finish off.
I am getting this issue as well, and it is rather annoying. I can trigger the event, by forcing a show to update the details from the indexer, and then most of the old seasons, which are set to archived already, are changed to wanted again and start downloading/error etc.
with over 200 hundred shows in the list, its rather painful having to track all through Episode status management to see which shows/seasons I have to revert to archived.
This morning again problems. Is this tvdb related or is it medusa related?
I'm also having this issue. Downgrading to 1.0.14 didn't help.
Triggering of new indexer also causes the same issue of the backlog searches and previous shows being archived. Dont want to go through and delete everything, and re-add as thats also painful as there is no mass way to actually set things back to archived, only ignored or skipped
Triggering of new indexer also causes the same issue of the backlog searches and previous shows being archived. Dont want to go through and delete everything, and re-add as thats also painful as there is no mass way to actually set things back to archived, only ignored or skipped
Manage -> Change Indexer - Allows you to change indexers in mass without deleting and re-adding shows. Manage -> Episode Status Management - Allows you to change episode status in mass without going to each individual show.
Using this process I was able to migrate away from TVDB and then set old season back to archived, The only manual/per show editing I had to do was setting back up Scene Exceptions for shows with apostrophes and colons in their names, and adding DV to Ignored Words for shows with 4K quality.
I have now gone three days without any more occurrences of mass downloading of old seasons of shows. Thank you to everyone who offered help and advice. The TVDB was definitely the culprit.
Manage -> Change Indexer - Allows you to change indexers in mass without deleting and re-adding shows. Manage -> Episode Status Management - Allows you to change episode status in mass without going to each individual show.
I wish Manage->Change Indexer would leave the Archived state set for episodes that already have this. It sets them to Downloaded if files exist. If quality settings have changed everything will be downloaded.
Interesting note about using Ep Stat Mgmt to set a whole pile to Archived after changing indexers. Thanks; that will be very useful.
That said, it would be nice if Change Indexer could honor existing state. If you have a mixed set of states (some Archived, some not), you don't want to set EVERYTHING to Archived.
See also https://github.com/pymedusa/Medusa/issues/11277 where I describe this behavior and request a fix.
1.0.16 did NOT solve this
made it even worse ….
1.0.16 did NOT solve this
made it even worse ….
That's unlikely. 1.0.16 will stop the update process for a show that has malformed data, which should avoid erroneously setting episodes as missing in the first place.
I had to correct like 15 shows, which were on archived before. Needed to remove more than 200 episodes which were put on wanted all of the sudden.
it would have helped if you could put all wanted episodes to archived But “episode status management” only let you put them on skipped
i use tvdb as indexer mostly , and did a “mass update” “update” on all shows
i use tvdb as indexer mostly , and did a “mass update” “update” on all shows
I've seen this too after doing a mass update on all shows; the shows involved were on tvdb at the time.
I've been seeing this for a while. All on tvdb. Just saw it recently with "The Walking Dead". Does migration to tvmaze fix it?
I've been seeing this for a while. All on tvdb. Just saw it recently with "The Walking Dead". Does migration to tvmaze fix it?
It seems to have fixed the issue for me. See above for mass migration instructions.
Tvdb is too unstable, i migrated to tvmaze. Took some time, but less time as correcting every day
Second day without errors, switching to tvmaze fixed everything.
Full week without any errors. Switching to tvmaze fixes everything
Well, switching to tvmaze can't be a magic fix for this specially for anime since it doesn't have recent series.
Also if I remember correctly thexem only mapped the numbering for tvdb and not tvmaze, so we could only choose "Anime" option on tvdb indexed series, did this change in the meanwhile?
Full week without any errors. Switching to tvmaze fixes everything
Except it doesn't.....I changed indexer and lost a complete show
2023-06-22 23:07:44 INFO SHOWQUEUE-REMOVE-SHOW :: [e98773f] 52458: Removing 2023-06-22 23:07:42 INFO SHOWQUEUE-CHANGE-INDEXER :: [e98773f] Running full backlog search on missed episodes for selected shows 2023-06-22 23:07:42 WARNING SHOWQUEUE-CHANGE-INDEXER :: [e98773f] Unable to add series: SaveSeriesException("Unable to load series from indexer: IndexerShowNotFound('Show search failed in getting a result with reason: Maze id 52458 not found')") Traceback (most recent call last):
It should not REMOVE the show, but keep it with the old indexer when it fails to set a new one
So I'd had this problem before, and have switched everything from tvdb to other indexers and haven't had any issues. Just now, however, I was copying a show I'd downloaded 3 seasons to my Plex server, and in the middle of copying pyMedusa deleted everything that hadn't copied and is now re-downloading these files. This is pretty maddening.
Describe the bug Several times over the last week, Medusa has redownloaded entire old seasons of multiple shows that were previously labeled "Archived". When I go to the show page I find entire old seasons marked as "Wanted". This has filled up my seedbox with unnecessary downloads,
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots If applicable, add screenshots to help explain your problem.
Medusa (please complete the following information):
Debug logs (at least 50 lines): General > Advanced Settings > Enable debug
Additional context Add any other context about the problem here.