seems to be back up and running with 1.23.5.4862 … i just dont understand how other one made it through to be published? any testing would have shown this to be fail. 
anyway… thanks for fixing this.
I am.
FYI, when I moved from 1.23.5 fix to this, I got stuck on updating library issue, left it a while but just seems stuck. Uninstall and back to 1.23.5 works fine again
Running
Server Version#: QNAP TVS-1282T3, running QNAP firmware 4.5.4.1723
Installed PlexMediaServer-1.23.6.4810-15ce0e21a-x86_64.qpkg this morning.
The package sits in “Uploading and processing” state for 5 minutes, then I get a failed import error.
Plex then becomes completely unresponsive. QNAP indicates the service is running, but none of my media is accessible (via app.plex.tv in web browser).
Subsequent reboots of the NAS haven’t fixed anything.
I backed up everything in the PlexData folder. Do I need to remove Plex altogether and then do a fresh package install or will there be a new package that ships that will actually complete the “Uploading and Processing” process?
Thanks!
So for the people who didn’t have a problem with 1.23.6.4810 (me) should we still downgrade?
1 Like
Was so confused by 1.23.6 being pulled off downloads after seeing 1.23.5 released as a fix… have same question… will wait for answer now.
I’m 99% sure it’s not necessary.
But you could upgrade to the 1.23.6.x version he posted a few messages up in this thread.
1 Like
Thanks… with all the 1.23.6 statements but NOT including the last decimal to indicate it was a different 1.23.6 version than the one posted\pulled, my scan of the thread missed it. 
I’m not impacted, luckily, but was thrown by the situation when I saw “new version” and the beta was an older version now.
Yea I see there’s another higher 1.23.6 version specifically 1.23.6.4860 that’s posted above which should be pushed out through official channels later tonight.
1 Like
worked fine on 1.23.6.4810-15ce0e21a until i restartet the win10 machine and im now stuck with a locked db.
going to downgrade now
Can we get a fix for NVIDIA Shield? You guys never pushed 1.23.6.4810 to the Shield on Beta Channel. I’m on 1.23.5.4841 and my server now crashes a few minutes after restarting with the same log messages. Help!
Need NVIDIA Shield Please!
It appears my database is locked, again. 
Plex Media Server Logs_2021-07-23_23-59-12.zip (3.8 MB)
It isn’t crashing now, but I can’t play anything. Worked fine all night up till a half hour ago.
EDIT: I lied. I’m back to square one. Full crash.
Same issue here. I’ve applied the 1.23.6.4860 patch but still crashing within a few seconds after starting the server.
EDIT: downgraded to 1.23.5.4862 and seems to be working ok now. Had to delete DVR and set up again.
1.23.6.4860 logs
Jul 24, 2021 07:15:08.759 [0x7fd9e002ab38] INFO - Plex Media Server v1.23.6.4860-1715b7caf - Ubuntu PC x86_64 - build: linux-x86_64 debian - GMT 01:00
Jul 24, 2021 07:15:08.760 [0x7fd9e002ab38] INFO - Linux version: 20.04.2 LTS (Focal Fossa), language: en-US
Jul 24, 2021 07:15:08.760 [0x7fd9e002ab38] INFO - Processor AMD Phenom(tm) II X4 965 Processor
Jul 24, 2021 07:15:08.760 [0x7fd9e002ab38] INFO - Compiler is - Clang 11.0.1 (https://plex.tv e0c29d5827bc4eaaa2ceb882cbeed224b0960173)
Jul 24, 2021 07:15:08.760 [0x7fd9e002ab38] INFO - /usr/lib/plexmediaserver/Plex Media Server
Jul 24, 2021 07:15:08.762 [0x7fd9e2eb5b50] DEBUG - BPQ: [Idle] -> [Starting]
Jul 24, 2021 07:15:08.764 [0x7fd9e2eb5b50] DEBUG - FeatureManager: Using cached data for features list
Jul 24, 2021 07:15:08.767 [0x7fd9e2eb5b50] DEBUG - Opening 20 database sessions to library (com.plexapp.plugins.library), SQLite 3.35.5, threadsafe=1
Jul 24, 2021 07:15:08.769 [0x7fd9e2eb5b50] INFO - SQLITE3:0x80000001, 283, recovered 125 frames from WAL file /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-in Support/Databases/com.plexapp.plugins.library.db-wal
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Running migrations. (EPG 0)
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Running forward migration 20210720150000.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 0.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 1.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 2.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 3.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 4.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 5.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 6.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 7.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 8.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 9.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 10.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 11.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 12.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 13.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 14.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 15.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 16.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 17.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 18.
Jul 24, 2021 07:15:08.823 [0x7fd9e2eb5b50] DEBUG - Captured session 19.
Jul 24, 2021 07:15:10.756 [0x7fd9dd76db38] DEBUG - [JobRunner] Job running: '/usr/lib/plexmediaserver/CrashUploader' '--directory=/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Crash Reports/1.23.6.4860-1715b7caf' '--version=1.23.6.4860-1715b7caf' '--platform=Linux' '--platformVersion=20.04.2 LTS (Focal Fossa)' '--serverUuid=e661ae1d8a0b3ea9d656075f59aa22bb324f3a17' '--userId=pod@podonthenet.co.uk' '--sentryUrl=https://sentry.io/api/1233455/minidump' '--sentryKey=xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx' '--vendor=Ubuntu' '--model=x86_64' '--device=PC' '--allowRetries=0'
Jul 24, 2021 07:15:10.756 [0x7fd9dd76db38] DEBUG - [JobRunner] Jobs: Starting child process with pid 27954
Jul 24, 2021 07:15:10.791 [0x7fd9dffebb38] DEBUG - Jobs: '/usr/lib/plexmediaserver/CrashUploader' exit code for process 27954 is 0 (success)
For me the 1.23.5.4862 update has been working fine for going on 8 hours now.
- Host OS: ubuntu 18.04
- Plex running in docker container
I still see a few of these roll through the logs now and then, but that’s a normal occurrence no matter the version (for me at least)
DEBUG - It took 140.000000 ms to retrieve 1 items.
WARN - SLOW QUERY: It took 240.000000 ms to retrieve 1 items.
DEBUG - It took 140.000000 ms to retrieve 1 items.
So, I was admittedly a bit sotted last night, and didn’t have the mental processing power to begin making proper diagnosis. My server had auto-updated to Version 1.23.6.4810 which I had assumed is the semi-official rollout for the fix because there was a new post in the server update thread. Nope, it had reverted back to the broken one.
I reapplied the version listed in this post (1.23.5.4862-0f739d462) and will disable updates until I’m told it’s safe to roll forward. Currently waiting for “Updating Library” which went pretty quick last time.
Will update as this unfolds.
EDIT: Corrupt Database error… lovely. I’ll have to investigate how to fix that without a proper backup.
Hello, I was having the same issue after upgrading to the most recent beta on Windows. I rolled back to 1.23.5 as was advised above and I believe that has fixed the issue. Thank you all for posting. I’m sure you know the panic feeling when Plex just keeps crashing. Now I can go back to enjoying my Saturday=D
I’m still dead, no update for the NVIDIA Shield was given. Please update the NVIDIA Shield version with the fix!
1 Like
So sorry to see you’re still dealing with this. Knock on wood, mine continues to work after seeming to resolve itself later in the day on Thursday. I still haven’t been able to figure out how that happened, especially because I ended up back with the current build and most people in this thread seem to have relied on rolling back, but if I’m able to identify what did the trick, I’ll sprint back here to share. I hope you get to the bottom of this today.
1 Like
Does MariaDB have this sort of issue? I know a lot of people (myself included) have been asking for a migration from SQLite for a long time.
