#PMM Keeps recreating already existing collections

1 messages Β· Page 1 of 1 (latest)

austere ridge
#

As per the title. Here is a screenshot of the duplicate collections it has made,

willow brambleBOT
#

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.

dull joltBOT
#

Find meta.log in config/logs/

Drag it in the Discord thread - the whole thing, DO NOT EDIT IT

Log file too big? USE PASTEBIN or ZIP THE FILE

Still confused? Β―\(ツ)/Β―

austere ridge
pearl granite
#

So this is most likely a corrupt database issue as plex should not allow multiple collections with the same to even be created

dull joltBOT
austere ridge
#

Ah was hoping that wasn't the answer lol. Rebuild time

austere ridge
#

is that the same as this error when trying to apply overlays to some tv shows?

cloud sparrow
#

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'"

austere ridge
#

Hmm I wonder if it’s because it got scanned in to plex after it had already cached the episodes?

cloud sparrow
#

Could be anything. It's a "well nobody saw that coming" error.

balmy basin
#

I'll close this as the issues are out of our control

willow brambleBOT
#

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.

balmy basin
#

sorry, testing went haywire

faint hemlock
#

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.

pearl granite
faint hemlock
#

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.

pearl granite
#

I run streaming collections just fine

faint hemlock
#

I actually created an issue here a few weeks back, but it was closed as being corrupt database, same as this one.

pearl granite
#

No duplicates at all. On latest nightly

faint hemlock
viscid tinsel
#

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...

faint hemlock
#

I'll roll back and try it again, and report back here.

viscid tinsel
#

to master?

pearl granite
#

@oak osprey any thoughts on this?

pearl granite
faint hemlock
faint hemlock
balmy basin
#

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

faint hemlock
#

What version of PMM is 1.19? Is that develop or master?

viscid tinsel
#

are u using containers?

dull joltBOT
#

NOTE: This is addressing changing from, for instance, latest to nightly.

The method depends on how you installed it.

**I'M USING DOCKER:**
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

**I'M USING DOCKER ON UNRAID**

: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.

**I'M USING DOCKER ON A SYSTEM WITHOUT COMMAND PROMPT (SUCH AS NAS):**

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.

**I'M RUNNING LOCALLY VIA GIT:**
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.

faint hemlock
#

Yes, Docker.

viscid tinsel
#

change tag to latest

faint hemlock
#

I was trying to go back to before the most recent update, to see if it would resolve the issue.

balmy basin
#

All three are on 1.19

viscid tinsel
#

if you are on develop, then moving to latest would be the "oldest"

balmy basin
#

Nightly just has some more commits above it

#

Develop and Master are in sync at present

viscid tinsel
#

and develop is somewhere in between

faint hemlock
#

Is there a way to go back to 1.18? Just for a test?

balmy basin
#

yes

viscid tinsel
#

with containers?

balmy basin
#

add :v1.18 I think it is

viscid tinsel
#

i did not think it was still there

balmy basin
#

you can't go to a specific commit

#

But you can go do a release

#

v1.18.0 I think actually

viscid tinsel
#

docker pull meisnate12/plex-meta-manager:v1.18.3

faint hemlock
#

That worked ... running a test now with 1.18.

balmy basin
#

Ah yeah I forgot 1.18.3 haha

faint hemlock
#

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.

pearl granite
#

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.

faint hemlock
#

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

pearl granite
#

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

faint hemlock
#

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.

balmy basin
#

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 🀣

pearl granite
#

i dont think it did

#

but i just double checked every library and i have no dupes. I just finished a run as well

faint hemlock
#

plex_meta_manager.py: error: unrecognized arguments: --log-requests in 1.18.3. Guess it didn't exist

balmy basin
#

just do -tr then

#

but do --log-requests for 1.19

faint hemlock
#

I'll be damned... now it stopped happening in 1.19.

pearl granite
#

thats what i was saying about the db repair you did

faint hemlock
#

Bizarre, because I did the db repair long before the issue stopped happening.

#

Might be because I deleted the old collections

pearl granite
#

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

faint hemlock
#

Yeah, possibly

pearl granite
#

i have no idea though. its all theories at this point

#

glad its fixed though

faint hemlock
#

Thanks all!

balmy basin
#

So can this be closed or?

faint hemlock
#

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.

balmy basin
#

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

faint hemlock
#

Ok cool, will do.

balmy basin
#

Just so we can double confirm it's nothing on PMM's side πŸ‘

#

(which it's not, I'm telling ya!!! :P)

willow brambleBOT
#

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.

viscid tinsel
#

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.

balmy basin
#

I mean it's not really a PMM issue πŸ˜„

#

But sure

balmy basin
#

@austere ridge can this be closed?

austere ridge
#

Yea Seems to have fixed it