Two "Album Collections" are indentical twins and won't die

I created two album collections with the same name. They were meant to be something like Vinyl 2023 and Vinyl 2022 (but in fact I used the same year by accident).

As I started populating one of these collections, I eventually noticed that both collections were being populated the same way. For example, if I add an album to one collection, it is added to the second collection as well.

I tried to rename one of the collections. However, they still were synched the same was as described above. So I eventually deleted both collections.

Then I started two new collections, named again Vinyl 2023 and Vinyl 2022. I was so confident I had fixed the issue, I took the next hour to repopulate it without checking.

Then, I noticed that both are populated the same way again.

Ugh. So how and I supposed to fix this cursed twin collection? I didn’t think I’d have to add the logs for this issue since it’s probably more of a obvious thing from the back end. Let me know what I need to do! THanks in advance.

Anyone, please?

What does the collection Tag look like in the albums?

I created a test collection. So the collections tag is usually locked, and if you have more than one tag in there the album will show up in both collections.

My best guess is check the tags and see what you have there. You might need to update the tags?

Edit: also check to see if the collections are locked or not.

Just a guess.

Thanks for replying. There are no tags/label on these collection. On my version of plex it’s called ‘Label’ in stead of ‘Tag’.

I just tried adding an album to a collection and it added it to the two collections again. Then I tried adding another album from the same artist and it looked the same album was added to the both collections (which is just adding to the confusion). I removed the duplicate and re-added it, and it happened again. Hmmm! Very weird.

lol, so then I tried adding again from Plex (instead of Plexamp). I’m getting so very interesting stuff happening. I wonder if there is actually something wrong with my software and/or database. I looked at logs and saw my public IP on the Plex Media Server.log but all the logs from today seem okay:

Jan 15, 2025 11:41:31.847 [548160467168] INFO - Request: [192.168.86.35:49534 (Allowed Network (Subnet))] OPTIONS /:/prefs (5 live) #f7576 TLS GZIP Signed-in Token ()
Jan 15, 2025 11:41:31.847 [548274307296] INFO - Completed: [192.168.86.35:49534] 200 OPTIONS /:/prefs (5 live) #f7576 TLS GZIP 0ms 376 bytes (pipelined: 3)
Jan 15, 2025 11:41:32.183 [548105871584] INFO - [Req#f7582] AutoUpdate: no updates available
Jan 15, 2025 11:41:35.114 [548192895200] INFO - [Req#f759a] AutoUpdate: no updates available
Jan 15, 2025 11:41:36.467 [548192895200] ERROR - [Req#f75ae] Unknown metadata type: folder
Jan 15, 2025 11:41:36.467 [548055322848] ERROR - [Req#f75ad] Unknown metadata type: folder
Jan 15, 2025 11:41:36.471 [548192895200] WARN - [Req#f75ae] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:36.471 [548055322848] WARN - [Req#f75ad] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:36.471 [548192895200] WARN - [Req#f75ae] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:36.471 [548055322848] WARN - [Req#f75ad] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:36.733 [548192895200] ERROR - [Req#f75d9] Unknown metadata type: folder
Jan 15, 2025 11:41:36.734 [548192895200] WARN - [Req#f75d9] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:36.734 [548192895200] WARN - [Req#f75d9] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:37.167 [548053213408] ERROR - [Req#f75e1] Unknown metadata type: folder
Jan 15, 2025 11:41:37.168 [548053213408] WARN - [Req#f75e1] QueryParser: Invalid field ‘contentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:37.168 [548053213408] WARN - [Req#f75e1] QueryParser: Invalid field ‘pinnedContentDirectoryID’ found, ignoring.
Jan 15, 2025 11:41:37.826 [548053213408] WARN - [Req#f75e1] SLOW QUERY: It took 910.000000 ms to retrieve 57 items.
Jan 15, 2025 11:41:48.305 [548192895200] WARN - [Req#f761a/PhotoTranscoder/Req#f7621] SLOW QUERY: It took 250.000000 ms to retrieve 32 items.
Jan 15, 2025 11:41:51.632 [548160467168] WARN - [Req#f763f] SLOW QUERY: It took 210.000000 ms to retrieve 20 items.
Jan 15, 2025 11:41:51.961 [548051103968] WARN - [Req#f7653] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 11:41:52.449 [548048994528] WARN - [Req#f7646/PhotoTranscoder/Req#f7652] SLOW QUERY: It took 370.000000 ms to retrieve 22 items.
Jan 15, 2025 11:41:52.843 [548051103968] WARN - [Req#f7653] SLOW QUERY: It took 840.000000 ms to retrieve 79 items.
Jan 15, 2025 11:41:53.230 [548068995296] WARN - [Req#f7647/PhotoTranscoder/Req#f765a] SLOW QUERY: It took 290.000000 ms to retrieve 46 items.
Jan 15, 2025 11:41:57.233 [548192895200] WARN - [Req#f76b2/PhotoTranscoder/Req#f76b6] SLOW QUERY: It took 330.000000 ms to retrieve 6 items.
Jan 15, 2025 11:42:02.493 [548053213408] WARN - [Req#f76e3/PhotoTranscoder/Req#f76e7] SLOW QUERY: It took 540.000000 ms to retrieve 21 items.
Jan 15, 2025 11:42:02.815 [548048994528] WARN - [Req#f76ee/PhotoTranscoder/Req#f76ef] SLOW QUERY: It took 220.000000 ms to retrieve 6 items.
Jan 15, 2025 11:42:04.025 [548055322848] WARN - [Req#f76f9/PhotoTranscoder/Req#f76fc] SLOW QUERY: It took 260.000000 ms to retrieve 7 items.
Jan 15, 2025 11:42:06.608 [548068995296] WARN - [Req#f771f] Missing X-Plex-Container-Size header. This will fail with status code 400 in the future.
Jan 15, 2025 11:42:07.856 [548053213408] WARN - [Req#f7723/PhotoTranscoder/Req#f7726] SLOW QUERY: It took 390.000000 ms to retrieve 29 items.
Jan 15, 2025 11:42:10.175 [548068995296] WARN - [Req#f771f] SLOW QUERY: It took 960.000000 ms to retrieve 99 items.
Jan 15, 2025 11:46:45.540 [548084539616] WARN - [Req#f77f7] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 11:46:46.307 [548084539616] WARN - [Req#f77f7] SLOW QUERY: It took 1530.000000 ms to retrieve 79 items.
Jan 15, 2025 11:46:58.209 [548068995296] WARN - [Req#f780a] SLOW QUERY: It took 260.000000 ms to retrieve 11 items.
Jan 15, 2025 11:47:11.524 [548062679264] WARN - [Req#f7865] Missing X-Plex-Container-Size header. This will fail with status code 400 in the future.
Jan 15, 2025 11:47:11.714 [548160467168] WARN - [Req#f7855/PhotoTranscoder/Req#f7866] SLOW QUERY: It took 270.000000 ms to retrieve 49 items.
Jan 15, 2025 11:47:12.085 [548073357536] WARN - [Req#f785f/PhotoTranscoder/Req#f7870] SLOW QUERY: It took 410.000000 ms to retrieve 47 items.
Jan 15, 2025 11:47:12.086 [548068995296] WARN - [Req#f7859/PhotoTranscoder/Req#f786e] SLOW QUERY: It took 550.000000 ms to retrieve 50 items.
Jan 15, 2025 11:47:21.733 [548024123616] WARN - [Req#f7871] Missing X-Plex-Container-Size header. This will fail with status code 400 in the future.
Jan 15, 2025 11:47:21.734 [548024123616] WARN - [Req#f7871] QueryParser: Invalid field ‘subtype’ found, ignoring.
Jan 15, 2025 11:47:21.734 [548024123616] WARN - [Req#f7871] QueryParser: Invalid field ‘smart’ found, ignoring.
Jan 15, 2025 11:47:47.234 [548073357536] WARN - [Req#f7930] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 11:48:11.483 [548160467168] WARN - [Req#f79f5] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 11:48:19.198 [548073357536] WARN - [Req#f7a01] Missing X-Plex-Container-Size header. This will fail with status code 400 in the future.
Jan 15, 2025 11:48:25.312 [548073357536] WARN - [Req#f7a04] Missing X-Plex-Container-Size header. This will fail with status code 400 in the future.
Jan 15, 2025 11:48:25.313 [548073357536] WARN - [Req#f7a04] QueryParser: Invalid field ‘subtype’ found, ignoring.
Jan 15, 2025 11:48:25.313 [548073357536] WARN - [Req#f7a04] QueryParser: Invalid field ‘smart’ found, ignoring.
Jan 15, 2025 11:48:54.161 [548050211040] WARN - [Req#f7ab3] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 11:49:12.751 [548050211040] WARN - [Req#f7ad4] SLOW QUERY: It took 210.000000 ms to retrieve 20 items.
Jan 15, 2025 11:49:13.146 [548105871584] WARN - [Req#f7b2c] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 11:49:41.952 [548050211040] INFO - Request: [192.168.86.35:49694 (Allowed Network (Subnet))] DELETE /library/collections/98850/children/92294?excludeAllLeaves=1 (6 live) #f7b3a TLS GZIP Signed-in Token (denis.128) (Chrome)
Jan 15, 2025 11:49:45.167 [548272197856] INFO - Completed: [192.168.86.35:49694] 200 DELETE /library/collections/98850/children/92294?excludeAllLeaves=1 (6 live) #f7b3a TLS GZIP 3215ms 736 bytes (pipelined: 2)
Jan 15, 2025 11:50:52.638 [548068995296] WARN - [Req#f7beb] Missing X-Plex-Container-Size header. This will fail with status code 400 in the future.
Jan 15, 2025 11:54:12.825 [548084539616] WARN - [Req#f7d29] QueryParser: Invalid field ‘subtype’ found, ignoring.
Jan 15, 2025 11:54:12.825 [548084539616] WARN - [Req#f7d29] QueryParser: Invalid field ‘smart’ found, ignoring.
Jan 15, 2025 11:54:13.316 [548073357536] INFO - Request: [192.168.86.35:49746 (Allowed Network (Subnet))] DELETE /library/collections/98847/children/92294?excludeAllLeaves=1 (7 live) #f7d33 TLS GZIP Signed-in Token (denis.128) (Chrome)
Jan 15, 2025 11:54:16.516 [548274307296] INFO - Completed: [192.168.86.35:49746] 200 DELETE /library/collections/98847/children/92294?excludeAllLeaves=1 (7 live) #f7d33 TLS GZIP 3200ms 761 bytes (pipelined: 2)
Jan 15, 2025 11:54:43.115 [548105871584] WARN - [Req#f7dfb] QueryParser: Invalid field ‘subtype’ found, ignoring.
Jan 15, 2025 11:54:43.115 [548105871584] WARN - [Req#f7dfb] QueryParser: Invalid field ‘smart’ found, ignoring.
Jan 15, 2025 11:55:37.210 [548068995296] WARN - [Req#f7f92] X-Plex-Container-Size header exceeds limit 120. This will fail with status code 400 in the future.
Jan 15, 2025 12:02:46.109 [548272197856] WARN - Deleted file “/home/plex/tmp_transcoding/logs.zipb92e7961-9770-4b7e-b6f7-21c5c56a9360” after connection reset

Jan 13, 2025 20:20:29.231 [548286845152] INFO - Plex Media Server v1.41.3.9314-a0bfb8370 - TerraMaster F2210 aarch64 - build: linux-aarch64 terramaster - GMT -05:00
Jan 13, 2025 20:20:29.232 [548286845152] INFO - Linux version: TOS 4.2.41, language: en-US
Jan 13, 2025 20:20:29.232 [548286845152] INFO - Processor: 4-core ARM Cortex-A53
Jan 13, 2025 20:20:29.232 [548286845152] INFO - Compiler is - Clang 11.0.1 (https://plex.tv 9b997da8e5b47bdb4a9425b3a3b290be393b4b1f)
Jan 13, 2025 20:20:29.232 [548286845152] INFO - /usr/local/plexmediaserver/Plex Media Server
Jan 13, 2025 20:20:29.518 [548289368096] INFO - SQLITE3:0x555b7a7850, 283, recovered 284 frames from WAL file /home/plex/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal

Should I stop using static album collections?

Try repairing your database, using this script: GitHub - ChuckPa/PlexDBRepair: Database repair utility for Plex Media Server databases

How many items are currently in these collections?
How many collections do you have in total on your server?

Thanks, I will look over the doc and plan to run some of the recommended maintenance tasks.

There are 101 items in this ‘dual’ collection. 14 album collections total.

The DBRepair script doesn’t know my NAS configuration, the terramaster. I can give it the manual information for databases and Plex SQLite directory, but I can’t find the SQLite directory on this installation. Would you be able to provide it?

x@TNAS-51B2:~/PlexDBRepair-1.10.02$ ./DBRepair.sh
Error: Unknown host. Current supported hosts are: QNAP, Syno, Netgear, Mac, ASUSTOR, WD (OS5), Linux wkstn/svr, SNAP
Current supported container images: Plexinc, LinuxServer, HotIO, & BINHEX
Manual host configuration is available in most use cases.

x@TNAS-51B2:~/PlexDBRepair-1.10.02$ ./DBRepair.sh --databases /home/plex/Library/“Application Support”/“Plex Media Server”/“Plug-in Support”/Databases --sqlite /home/plex/Library/“Application Support”/“Plex Media Server”/
Given ‘Plex SQLite’ directory/path (‘/home/plex/Library/Application Support/Plex Media Server/’) is invalid. Aborting.

Unfortunately I have no knowledge of this platform.
In general, the necessary sqlite binaries are included in the same folder where the Plex executables are stored. You’d need to find out this information somehow on your NAS. Perhaps from some startup script which is starting up the various software on that device.

Here is an older thread, which unfortunately doesn’t include an exact description of the method that helped the user in the end. But maybe you can gleam enough from it: Server unavailable after updating to version 1.40.3

PlexSQLite = ‘/usr/lib/plexmediaserver/Plex SQLite’

  Plex Media Server Database Repair Utility (User Defined)
                   Version v1.10.02

Okay, it worked!!! Thank you
 Hoping this clears a few other quirks I’ve noticed. Good thing to remember, and thank you!

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.