#PMM Keeps recreating already existing collections
1 messages Β· Page 1 of 1 (latest)
Welcome!
Someone from <@&938443185347244033> will assist when they're available.
Including the meta.log from the beginning is a huge help, type !logs for more information.
You can press the "Close Post" button above or type !close at any time to close this post.
So this is most likely a corrupt database issue as plex should not allow multiple collections with the same to even be created
Having trouble with PLEX? Here are some links that may help you.
Repair Corrupt DB: https://support.plex.tv/articles/repair-a-corrupted-database/
Restore PLEX DB: https://support.plex.tv/articles/202485658-restore-a-database-backed-up-via-scheduled-tasks/
Ah was hoping that wasn't the answer lol. Rebuild time
is that the same as this error when trying to apply overlays to some tv shows?
a 500 is Plex saying "Something went wrong inside, but no developer foresaw it to add error handling and no tester ran into it to make error handling get added, so all I can say is 'the bad thing happened'"
Hmm I wonder if itβs because it got scanned in to plex after it had already cached the episodes?
Could be anything. It's a "well nobody saw that coming" error.
I'll close this as the issues are out of our control
This post has been marked as Resolved and will be closed in one hour unless you send another message.
Once closed, you cannot reopen this thread - you must create a new one or ask a member of staff to reopen it in #general-chat.
Thanks for using Plex Meta Manager.
sorry, testing went haywire
FWIW, I am seeing the same exact thing (and only on the streaming collections). Very odd that we are both seeing the same issue, and makes me wonder if maybe it's something other than a corrupt database. I have repaired my database (not a complete rebuild) but I'm still seeing this issue.
The exact same name though? There was a pmm issue before where collections duplicated but the names were different, one set had Movies or Shows at the end of the name
Yep, the same name. And if I run PMM again, I get another copy. I've had to stop running the Streaming collections because every time I run it, I get a new copy of each. And they also don't have the posters, it shows the generic posters like in his screenshot.
I run streaming collections just fine
I actually created an issue here a few weeks back, but it was closed as being corrupt database, same as this one.
No duplicates at all. On latest nightly
I used to, as well. This only started happening recently. In fact I might try rolling back PMM to the previous version, to see if that changes things for me.
I was running all the collections without duplication, however, my library is pretty small...
I am working on another problem that I have so I cannot test this phenomenon until later this week... likely...
I'll roll back and try it again, and report back here.
to master?
@oak osprey any thoughts on this?
When you repaired, did you delete the collections as well?
Only the ones that are affected. Maybe I should delete all collections?
That's what I was thinking. I'm currently on develop.
Im not convinced this is a PMM issue
Plex doesn't let you name two collections the same
It should actively deny it
I've been running Streaming for months on end with no issue
I was too. Until this suddenly started appearing.
What version of PMM is 1.19? Is that develop or master?
are u using containers?
NOTE: This is addressing changing from, for instance, latest to nightly.
The method depends on how you installed it.
docker pull meisnate12/plex-meta-manager:TAG_HERE
replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.
Then recreate your container via whatever means you used to create it [docker run, docker-compose, etc.], setting the image as meisnate12/plex-meta-manager:TAG_HERE
:one: Click on DOCKER tab and then on Plex-Meta-Manager
:two: Edit Repository: setting to switch branches:
meisnate12/plex-meta-manager:TAG_HERE
replace TAG_HERE with latest, develop, or nightly; whichever you want to switch to.
The same concepts as above will apply:
:one: pull new image
:two: recreate container using that image instead of the current one.
Whatever the system, there will be a way to accomplish these two things.
cd DIRECTORY_WHERE_YOU_PUT_PMM
git checkout BRANCH_NAME
git stash
git stash clear
git pull
For BRANCH_NAME, substitute master, develop, or nightly
Those stash commands are going to discard any changes you may have made to PMM's own files. If that's a concern, you are probably familiar enough with git to know what you need to do instead.
Yes, Docker.
change tag to latest
I was trying to go back to before the most recent update, to see if it would resolve the issue.
All three are on 1.19
if you are on develop, then moving to latest would be the "oldest"
Nightly just has some more commits above it
Develop and Master are in sync at present
and develop is somewhere in between
Is there a way to go back to 1.18? Just for a test?
yes
with containers?
add :v1.18 I think it is
i did not think it was still there
you can't go to a specific commit
But you can go do a release
v1.18.0 I think actually
That worked ... running a test now with 1.18.
Ah yeah I forgot 1.18.3 haha
You're not gonna believe this but 1.18.3 is working fine. At least so far, it's creating the collections with the correct posters. Still have to get through this first run so I can run it again and make sure it doesn't duplicate the collections... but so far it's looking good.
Just completed a third run with 1.18.3. No duplicates, and all posters are showing up as expected.
Idk I've been running 1.19 long before it was on latest. I've been on 1.19 since it first hit nightly which was like what 6 or 7 months ago. Just seems weird only 2 people out of everyone who's on 1.19 has this issue.
I know, but I also know that it happens on 1.19, doesn't happen on 1.18.3.
Guess I could just stay on 1.18.3, but my FOMO will be out of control
You could try going back to 1.19 now and see what happens. Maybe the db repair fixed something that could of been an issue of going from 1.18.3 to 1.19 but isn't an issue now π€·ββοΈ
I have no idea. It's difficult to troubleshoot stuff like this
It wasn't the db repair. I didn't do a db repair in between switching from 1.19 to 1.18.3. But it still stopped doing it when I switched.
But you're right, these things are damn near impossible to troubleshoot.
so run this test for me
3 runs on 1.18.3 - do they duplicate
3 runs on 1.19.0 - do they duplicate
on one of the three runs on both versions, can you do --log-requests in the run command
idk if log requests existed in 1.18.3, we'll find out π€£
i dont think it did
but i just double checked every library and i have no dupes. I just finished a run as well
Doing this now
plex_meta_manager.py: error: unrecognized arguments: --log-requests in 1.18.3. Guess it didn't exist
I'll be damned... now it stopped happening in 1.19.
thats what i was saying about the db repair you did
Bizarre, because I did the db repair long before the issue stopped happening.
Might be because I deleted the old collections
maybe something happened with the upgrade from 1.18 to 1.19 for you, the db repair didnt fix the dupe issue but it could have fixed an issue that happened from 1.18 to 1.19
Yeah, possibly
Thanks all!
So can this be closed or?
I think so, I'm trying other libraries since I only did my smallest one. But I believe if it comes back, I can fix it by switching to 1.18.3 again.
Well no
I would never suggest downgrading major versions as a solution π
If it happens again then raise a thread with some logs and we can double check it
Ok cool, will do.
Just so we can double confirm it's nothing on PMM's side π
(which it's not, I'm telling ya!!! :P)
This post has been marked as Resolved and will be closed in one hour unless you send another message.
Once closed, you cannot reopen this thread - you must create a new one or ask a member of staff to reopen it in #general-chat.
Thanks for using Plex Meta Manager.
Ummm... we closed this because Departed has their issue fixed... however, no idea if @austere ridge is able to do the same and fix it....
And his is the OP.
@austere ridge can this be closed?
Yea Seems to have fixed it