Not deleting certain collections when running - creating a ton of duplicates

[tulip cipher]

📝 If you want to review this again, joed1986:
:one: Right-click (or long press with phone) on the message that contains the log
:two: Select: Copy Message Link
:three: Use the command: /logscan <message_link> or !logscan <message_link> and paste the value copied from the previous step where you see <message_link> 📝

Welcome @keen pagoda!

Thanks for being a Kometa Sponsor, we greatly appreciate it! Your ticket will now be diverted to <@&1097919568334311495> and <@&938443185347244033>.

Including meta.log from the beginning is a huge help. Type !logs for more information.

After attaching your log, do not forget to hit the green check boxes when prompted by our bot.

You can press the "Close Post" button above or type /close at any time to close this post.

[tulip cipher]

I run on this program on both macs and PCs. The PC versions run without issues, but on the mac certain collections will create multiple copies over time (it seems like when it goes to run again it creates a new collection in some cases and does not delete the older one). I have not been able to figure out why this happens on mac as it does not happen on PC, it also only happens on certain mac collections and not others. Including here the config file - the file thats creating many duplicate collections - the log

[digital escarp]

Plex should't allow duplicates, if it is then that's a sign of DB corruption

what collections is kometa "not deleting" that it should be?

[keen pagoda]

all of the collections within the Best_of2 get duplicated everytime kometa runs

this has happened consistently for a long time - i usually then go in and just select all those duplicates and delete them

it doesnt happen with the other collections that kometa is making - it only happens with those collections

[young sparrow]

Regardless of when it's happening that's entirely inside Plex; Plex should not allow multiple collections with the same name regardless of who creates them.

And there's no way for an api client to tell or force it to do so.

[young sparrow]

That log above contains only three failed Plex connection attempts.

Kometa attempts to connect to Plex for each library, and receives:

| ConnectionRefusedError: [Errno 61] Connection refused

each time

[keen pagoda]

ok ive gone and reinstalled kometa - also deleted the collections and testing out - seems to work so far but will see how this goes. Perhaps an old hard drive which had been causing issues in the past was creating a fault and causing the database to screw up on that particular action

[digital escarp]

Whatever the case, it isn’t caused by Kometa

[low jungle]

antwanchild used !aenh

@keen pagoda, anything else needed here? If not, please type /close and hit enter. Please respond within 24 hours of this message or it will be archived.

[young sparrow]

What should happen:

Script: Hey Plex I want to create a collection named "foo".
Plex: I have one with that name right here, let's modify this one.

What apparently happens:

Script: Hey Plex I want to create a collection named "foo".
Plex: Even though I have one with that name already, let's create a new one because whatever.

This isn't platform-dependent [Kometa running on Windows interacts with Plex in exactly the same way as Kometa on Mac].