Don't know, if Crash Uploading is working or not. How to find out? Too many requests?

Plex Media Server NAS & Devices
1

Server Version#: 1.18.2.2015-5a99a9a46

Old and/or not answered/helping Posts:

https://forums.plex.tv/t/crashdump-uploader-not-working/188007

Hi,
I’m not sure, if the Crash Uploader is working here:

I’m seeing this in Plex Crash Uploader.*.log:

Nov 11, 2019 18:25:55.543 [0x7f2825db9700] INFO - Crash Uploader - Platform: Linux ServerUUID: myserverUUID UserId: mymail@mytld.net Version: 1.18.2.2015-5a99a9a46
Nov 11, 2019 18:25:56.717 [0x7f282bcb3740] ERROR - Failed to upload crashdump 6596a5d4-ec6a-7cfb-486614a8-591a170e: 429
Nov 11, 2019 18:25:59.115 [0x7f282bcb3740] ERROR - Failed to upload crashdump 7bb12753-5b36-2598-42fe84d3-26bd6738: 429
Nov 11, 2019 18:26:01.262 [0x7f282bcb3740] ERROR - Failed to upload crashdump 5a9e65bb-662a-ef9c-6585054e-4e27259a: 429
Nov 11, 2019 18:26:02.370 [0x7f282bcb3740] ERROR - Failed to upload crashdump 5506ea97-ee24-f3ee-50f4c351-210576b0: 429
Nov 11, 2019 18:26:03.525 [0x7f282bcb3740] ERROR - Failed to upload crashdump 79c9a312-af0d-785b-2af120bf-0f975cbe: 429
Nov 11, 2019 18:26:08.540 [0x7f282bcb3740] ERROR - Failed to upload crashdump 1901aeb1-a3d3-f025-4516b9ca-33bfdc6d: 429

as well as this:

Nov 13, 2019 09:30:52.953 [0x7fbef7c68700] INFO - Crash Uploader - Platform: Linux ServerUUID: myserverUUID UserId: NOUSERID Version: 1.18.2.2015-5a99a9a46
Nov 13, 2019 09:30:53.056 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:54.312 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:54.313 [0x7fbefdb62740] ERROR - Failed to upload crashdump 64748d33-ca00-7b17-4457439e-2201de3f: 429
Nov 13, 2019 09:30:54.350 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:55.388 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:55.388 [0x7fbefdb62740] ERROR - Failed to upload crashdump 6596a5d4-ec6a-7cfb-486614a8-591a170e: 429
Nov 13, 2019 09:30:55.487 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:56.512 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:56.512 [0x7fbefdb62740] ERROR - Failed to upload crashdump 7bb12753-5b36-2598-42fe84d3-26bd6738: 429
Nov 13, 2019 09:30:56.535 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:57.603 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:57.603 [0x7fbefdb62740] ERROR - Failed to upload crashdump 5a9e65bb-662a-ef9c-6585054e-4e27259a: 429
Nov 13, 2019 09:30:57.604 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:58.627 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:30:58.627 [0x7fbefdb62740] ERROR - Failed to upload crashdump 3d0f4d0c-86cd-4adb-511c377b-0bb33ec7: 429
Nov 13, 2019 09:30:58.627 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:01.293 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:01.293 [0x7fbefdb62740] ERROR - Failed to upload crashdump 35e2378b-9f24-8189-36647ea8-2581c537: 429
Nov 13, 2019 09:31:01.313 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:03.134 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:03.134 [0x7fbefdb62740] ERROR - Failed to upload crashdump 5506ea97-ee24-f3ee-50f4c351-210576b0: 429
Nov 13, 2019 09:31:03.162 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:04.615 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:04.615 [0x7fbefdb62740] ERROR - Failed to upload crashdump 79c9a312-af0d-785b-2af120bf-0f975cbe: 429
Nov 13, 2019 09:31:04.616 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:05.961 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:05.961 [0x7fbefdb62740] ERROR - Failed to upload crashdump 39aa7dbf-387b-494d-7ef8b40c-5afcbcf8: 429
Nov 13, 2019 09:31:05.978 [0x7fbefdb62740] DEBUG - HTTP requesting POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:07.257 [0x7fbefdb62740] DEBUG - HTTP 429 response from POST https://sentry.io/api/1233455/minidump?sentry_key=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Nov 13, 2019 09:31:07.258 [0x7fbefdb62740] ERROR - Failed to upload crashdump 1901aeb1-a3d3-f025-4516b9ca-33bfdc6d: 429

Its not clear to me, wether the logs are sent (which they should) or not.

Simply trying to PING sentry.io gives this:

:> ping sentry.io
PING sentry.io (35.188.42.15) 56(84) bytes of data.
64 bytes from 15.42.188.35.bc.googleusercontent.com (35.188.42.15): icmp_seq=1 ttl=40 time=122 ms
64 bytes from 15.42.188.35.bc.googleusercontent.com (35.188.42.15): icmp_seq=2 ttl=40 time=121 ms
64 bytes from 15.42.188.35.bc.googleusercontent.com (35.188.42.15): icmp_seq=3 ttl=40 time=122 ms

Also a simple WGET seems to resolve the address.

:> wget https://sentry.io/api/1233455/minidump
--2019-11-13 10:20:32--  https://sentry.io/api/1233455/minidump
Resolving sentry.io... 35.188.42.15
Connecting to sentry.io|35.188.42.15|:443... connected.
HTTP request sent, awaiting response... 405 METHOD NOT ALLOWED
2019-11-13 10:20:32 ERROR 405: METHOD NOT ALLOWED.

So the network is up and running, what could be the cause?

Can someone of the Plexteam tell me, if the (hopefully useful) reports are succsessfully sent, or what may be the problem with the Crash Uploader?

2

Same with me. My server is crashing ALOT lately and I don’t think plex is getting the reports. :frowning:

3

Also having this problem.

4

i’m having the same problem.
ever since updating PMS to 1.18.2.2058 on my synology, it has been crashing at least twice a week.
i see an “ERROR - Failed to upload crashdump xx-xx-xx-xx-xx: 429” in Plex Crash Uploader.log, then nothing. i restart the service and i have no idea why it even crashed in the first place

5

May I see the full (manually created in File Station) ZIP of the Logs directory?

6

sure, i can even provide you said Crash Report .dmp file, but how do i share this with only you, and not this entire forum? (because these logs contain email addresses, user ID’s and ip addresses…)

7

Check your DM please

8

A small “Too many crashdumps detected!” update. (From Plex Crash Uploader.log)

Dec 22, 2019 11:44:08.828 [294688] INFO - Crash Uploader - Platform: Windows ServerUUID: 7aa032c294d0294d5205c5a830d869c1c0bd35c7 UserId: my@mail.de Version: 1.18.4.2171-ac2afe5f8
Dec 22, 2019 11:44:11.189 [295460] ERROR - Failed to upload crashdump 0692862d-b312-4066-9eb1-b2b011573fad: 429
Dec 22, 2019 11:44:12.331 [295460] ERROR - Failed to upload crashdump 14295da3-4f53-43f3-b5e8-b43ee695d04c: 429
Dec 22, 2019 11:44:13.445 [295460] ERROR - Failed to upload crashdump 153dc8a6-7b3a-4447-b94d-ce8f754bca12: 429
Dec 22, 2019 11:44:14.520 [295460] ERROR - Failed to upload crashdump 20a1b951-6528-4ce7-8c15-7a1302eeaabe: 429
Dec 22, 2019 11:44:15.718 [295460] ERROR - Failed to upload crashdump 3fbc2261-2581-4c5c-825e-804102c2e982: 429
Dec 22, 2019 11:44:17.729 [295460] ERROR - Failed to upload crashdump 47f211a1-9c5b-4137-afbe-87380704c505: 429
Dec 22, 2019 11:44:18.812 [295460] ERROR - Failed to upload crashdump 9bca66cc-455d-4bbb-83ed-4165a9f5e109: 429
Dec 22, 2019 11:44:20.071 [295460] ERROR - Failed to upload crashdump a75decc6-706c-4d29-9c61-201194840f19: 429
Dec 22, 2019 11:44:21.221 [295460] ERROR - Failed to upload crashdump b49ce6f7-07dc-408a-af07-4e3210bd98fb: 429
Dec 22, 2019 11:44:22.389 [295460] ERROR - Failed to upload crashdump be4a1da2-4ae9-40f3-9913-ea2af76790ab: 429
Dec 22, 2019 11:44:23.571 [295460] ERROR - Failed to upload crashdump e4d2a070-0538-423d-bee1-46347c236c9a: 429
Dec 22, 2019 11:44:23.572 [295460] ERROR - Too many crashdumps detected!
Dec 22, 2019 11:44:23.572 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\0692862d-b312-4066-9eb1-b2b011573fad.dmp
Dec 22, 2019 11:44:23.573 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\14295da3-4f53-43f3-b5e8-b43ee695d04c.dmp
Dec 22, 2019 11:44:23.573 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\153dc8a6-7b3a-4447-b94d-ce8f754bca12.dmp
Dec 22, 2019 11:44:23.573 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\20a1b951-6528-4ce7-8c15-7a1302eeaabe.dmp
Dec 22, 2019 11:44:23.573 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\3fbc2261-2581-4c5c-825e-804102c2e982.dmp
Dec 22, 2019 11:44:23.574 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\47f211a1-9c5b-4137-afbe-87380704c505.dmp
Dec 22, 2019 11:44:23.574 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\9bca66cc-455d-4bbb-83ed-4165a9f5e109.dmp
Dec 22, 2019 11:44:23.574 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\a75decc6-706c-4d29-9c61-201194840f19.dmp
Dec 22, 2019 11:44:23.575 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\b49ce6f7-07dc-408a-af07-4e3210bd98fb.dmp
Dec 22, 2019 11:44:23.575 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\be4a1da2-4ae9-40f3-9913-ea2af76790ab.dmp
Dec 22, 2019 11:44:23.575 [295460] ERROR -   Removing E:\settings\Plex\Plex Media Server\Crash Reports\1.18.4.2171-ac2afe5f8\PLEX MEDIA SCANNER\e4d2a070-0538-423d-bee1-46347c236c9a.dmp

and a little bit later, it seems that the crashes are flodding the (smallish in size) logs:

Dec 22, 2019 11:59:15.727 [288720] INFO - Crash Uploader - Platform: Windows ServerUUID: 7aa032c294d0294d5205c5a830d869c1c0bd35c7 UserId: my@mail.de Version: 1.18.4.2171-ac2afe5f8
Dec 22, 2019 11:59:17.451 [295204] ERROR - Failed to upload crashdump 24239dc7-9b0a-4415-86c8-7c68ba224787: 429
Dec 22, 2019 11:59:19.503 [295204] ERROR - Failed to upload crashdump 41da8050-bc1a-4ce9-a46c-dafff4c13ef5: 429
Dec 22, 2019 11:59:21.604 [295204] ERROR - Failed to upload crashdump 5a1cab1a-5d6b-4c6d-a952-e2eb27aabd86: 429
Dec 22, 2019 11:59:24.820 [295204] ERROR - Failed to upload crashdump 702e275b-e961-4437-baad-41243e8a6317: 429
Dec 22, 2019 11:59:25.934 [295204] ERROR - Failed to upload crashdump 8801c6ff-e2d2-475a-8c81-1a8cf36e1db4: 429
Dec 22, 2019 11:59:27.189 [295204] ERROR - Failed to upload crashdump 95669fef-ef8f-4468-8f0a-5a109c900977: 429
Dec 22, 2019 11:59:28.350 [295204] ERROR - Failed to upload crashdump a59e7769-f7de-4f44-be83-55314cf98450: 429
Dec 22, 2019 11:59:30.511 [295204] ERROR - Failed to upload crashdump b75c4ba0-a560-46cd-bbcd-eac5b44d144e: 429
Dec 22, 2019 11:59:31.636 [295204] ERROR - Failed to upload crashdump e0003407-2829-4c35-a470-76cd754fe3fa: 429
Dec 22, 2019 11:59:37.877 [295204] ERROR - Failed to upload crashdump ee26b000-b393-47fc-b5ca-24c3b8b90fec: 429
9

Stop Plex
Delete the entire contents of the “Crash Reports” directory.
Start Plex

What’s happened is you’ve had so many crashes, you’re now being throttled.
Time to wipe it all out and start frsh.

When it does crash again, please start a fresh thread with server-windows tag
This is Synology (Linux)

10

Just adding here:
After deleting all the Subfolders in “Crash Reports” folder and updating to 1.18.3.2156 6 days ago, PMS hasn’t crashed for me yet. Let’s hope it stays that way :partying_face:

11

Thanks, deleting the crashlog folder takes me back to my initial posting, which is about “the crashlog seems not to be uploaded”.

My PMS’s are on Windows and Linux, so maybe its a global blocking thingy, but I don’t have a firewall, only pi-hole, which is not blocking relevant domains, IMHO.

No place, where I could block the domain sentry.io. beside pihole, but that domain is not blocked.

What domains does the crashuploader tries to upload?

Any ideas?

12

Crashes are uploaded to sentry.io

13

well. my PMS stopped working again.
same as before. nothing logged in Plex Media Server.log except for “running CrashUploader” (which is the last entry)
then in Plex Crash Uploader.log the only thing i get is “ERROR - Failed to upload crashdump : 429”
so it seems the crashdump itself is failing, even though there’s only 1 folder in the “Crash Reports” directory.
even so. why is it calling crashuploader in the first place? i see no indication what went wrong to invoke the crash uploading. and THEN the crash uploading also fails.

@ChuckPa can i send you my dumps and logs again?

edit:
FYI: the remote user reported having issues during selecting subtitles when it crashed.
so i checked the pms plugin logs. and the last thing i see is INFO (pipeinterface:87) - Stopping plug-in in com.plexapp.system.log which is 3 seconds after the “failed to upload”

14

PM sent.

It calls the uploader if a .dmp file exists.

15

Ok, then it must be something else, which causes the problem with the upload. sentry.io is fully accessible from here.

Unfortunately, also with DEBUG + VERBOSE logging activated, nothing interesting is shown in Plex Crash Uploader.log

So it seems we will never find out, WHY the Crash Upload is not uploading, which is very sad, because I have trillions of crashes (from media scanner tasks) a day, which I hoped to be helpful for the developers.

What can I do to supply more infos?

16

Let’s take a breath please?

  1. Crash upload being throttled by Sentry means it’s retrying at too fast a rate.
  2. You state ‘trillions’. It’s clearly not that many but I do understand your frustration and it feels that way.

I would like to invoke the scanner manually with you so we can find out exactly what’s happening. There is console output which will prove very useful if it’s crashing that easily.

This having been said, and not a widespread issue, we need to find out what is going on with your DSM installation.

I will prepare a script for you which we can run on Synology and post back here when I have it ready.

17

I have put together a few commands to perform basic validation of the installation.

  1. SSH into the Synology and obtain the terminal prompt
  2. sudo -su root (elevate to root privilege)
  3. See the scanner command line options
su plex -s /bin/sh -c '/var/packages/Plex\ Media\ Server/target/Plex\ Media\ Scanner'
  1. Get the list of currently defined sections
su plex -s /bin/sh -c '/var/packages/Plex\ Media\ Server/target/Plex\ Media\ Scanner -l'
  1. Trial scan for new media. This will exercise major components and the database. You will see it walk through your media looking for new files. “GUI” messages are it sending progress activity reports to Plex/Web. (This may take time if you have a lot of media so please be prepared)
su plex -s /bin/sh -c '/var/packages/Plex\ Media\ Server/target/Plex\ Media\ Scanner -s'

Let me know how this ends.

1 Like
18

Thanks.

I followd Steps 1-3.

> whoami
root

Step 3 shows me the list of command line options.

Step 4 crashes the Plex Media Scanner:

> su plex -s /bin/sh -c '/var/packages/Plex\ Media\ Server/target/Plex\ Media\ Scanner -l'
terminate called after throwing an instance of 'soci::soci_error'
  what():  sqlite3_statement_backend::prepare: no such column: library_sections.content_changed_at for SQL: select library_sections.id as 'library_sections_id', library_sections.library_id as 'library_sections_library_id', library_sections.name as 'library_sections_name', library_sections.name_sort as 'library_sections_name_sort', library_sections.section_type as 'library_sections_section_type', library_sections.language as 'library_sections_language', library_sections.agent as 'library_sections_agent', library_sections.scanner as 'library_sections_scanner', library_sections.user_thumb_url as 'library_sections_user_thumb_url', library_sections.user_art_url as 'library_sections_user_art_url', library_sections.user_theme_music_url as 'library_sections_user_theme_music_url', library_sections.created_at as 'library_sections_created_at', library_sections.updated_at as 'library_sections_updated_at', library_sections.scanned_at as 'library_sections_scanned_at', library_sections.user_fields as 'library_sections_user_fields', library_sections.query_xml as 'library_sections_query_xml', library_sections.query_type as 'library_sections_query_type', library_sections.uuid as 'library_sections_uuid', library_sections.changed_at as 'library_sections_changed_at', library_sections.content_changed_at as 'library_sections_content_changed_at' from library_sections
****** PLEX MEDIA SCANNER CRASHED, CRASH REPORT WRITTEN: /var/services/homes/plex/Library/Application Support/Plex Media Server/Crash Reports/1.18.4.2171-ac2afe5f8/PLEX MEDIA SCANNER/38e589e6-1dec-071b-62127715-23e82bcd.dmp
Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign
Crash Uploader options (all are required):
  --directory arg       Directory to scan for crash reports
  --serverUuid arg      UUID of the server that crashed
  --userId arg          User that owns this product
  --platform arg        Platform string
  --platformVersion arg Platform version string
  --vendor arg          Vendor string
  --device arg          Device string
  --model arg           Device model string
  --sentryUrl arg       Sentry URL to upload to
  --sentryKey arg       Sentry Key for the project
  --version arg         Version of the product
Aborted (core dumped)

This error seems odd to me, because the command line I copied from your post and pasted to the console did not included '--serverUuid'.

Error in command line:the argument for option '--serverUuid' should follow immediately after the equal sign

Step 5 does nothing here.

Would you like to have the mentioned DMP file via PM?

19

Your database is all out of whack (“Highly” technical term :rofl: )
While it isn’t fully corrupt, it’s corrupt enough the scanner can’t work with it.

Please open File Station.
Navigate into the Plex share.
Library / Application Support / Plex Media Server / Plug-in Support / Databases.

Do you see com.plexapp.plugins.library.db-DATE_VALUE_HERE files ?

20

Thats nothing new… but I wonder, why Plex is whacking it…(or, in other objective words, what is whacking it)

No, because I don’t let Plex backup my databases.

For me, it does not have any sense to backup, since also starting from scratch* will not protect me for plex is corrupting the database itself. Also, I don’t know, which backup would contain a working copy, so starting from scratch is the only safe way.

I started from scratch a lot of times:
completely removed syno package, deleted all plex folders, reinstalled, etc.
I also followed the restart-plex-media-server-setup-from-scratch guide,
and updated to the latest PMS/PMP versions as soon as they are available, but its always the same result.

Plex is messing up its own database without my help :->

I really like to help to fix that.