Plex DVR appears to be corrupt (unable to remove)

Server Version#: 1.21.2.3943
Player Version#: 1.27.1.1571-2fface66

Plex DVR seems to have corrupted somehow, and I cannot even remove it to reset it. Setting up Plex from scratch is not an option. Logs available on request.

I’m hoping there’s some way to manually remove the Plex DVR setup manually. I tried removing the DVR references in the DB, but it still is trying to refresh guide of a non-existent Plex DVR and still thinks there is a tuner-less DVR. Help would be much appreciated.

I found this in the log.

Feb 03, 2021 13:36:12.190 [0x80bdab000] ERROR - SQLITE3:0x10, 8, statement aborts at 1: [BEGIN IMMEDIATE] attempt to write a readonly database
Feb 03, 2021 13:36:12.190 [0x80bdab000] ERROR - Failed to begin transaction (…/Library/Tag.cpp:159) (tries=7): Cannot begin transaction. attempt to write a readonly database
Feb 03, 2021 13:36:12.631 [0x80bdab000] ERROR - SQLITE3:0x10, 8, statement aborts at 1: [BEGIN IMMEDIATE] attempt to write a readonly database
Feb 03, 2021 13:36:12.631 [0x80bdab000] ERROR - Failed to begin transaction (…/Library/Tag.cpp:159) (tries=8): Cannot begin transaction. attempt to write a readonly database
Feb 03, 2021 13:36:13.420 [0x80b587c00] DEBUG - HTTP requesting GET https://plex.tv/api/resources.xml?includeHttps=1&includeRelay=1&auth_token=xxxxxxxxxxxxxxxxxxxx
Feb 03, 2021 13:36:13.515 [0x80bdab000] ERROR - SQLITE3:0x10, 8, statement aborts at 1: [BEGIN IMMEDIATE] attempt to write a readonly database
Feb 03, 2021 13:36:13.515 [0x80bdab000] ERROR - Failed to begin transaction (…/Library/Tag.cpp:159) (tries=9): Cannot begin transaction. attempt to write a readonly database
Feb 03, 2021 13:36:13.966 [0x80b587c00] DEBUG - HTTP 200 response from GET https://plex.tv/api/resources.xml?includeHttps=1&includeRelay=1&auth_token=xxxxxxxxxxxxxxxxxxxx
Feb 03, 2021 13:36:13.967 [0x80f3d7900] DEBUG - Connection Tester: Testing the server Dalton-Laptop with 2 URLs.
Feb 03, 2021 13:36:13.967 [0x80f3d6f00] DEBUG - HTTP requesting GET https://174-109-206-38.8907082ec9e34ee989cad62940b870e0.plex.direct:24477
Feb 03, 2021 13:36:13.967 [0x80bd59500] DEBUG - HTTP requesting GET https://10-0-0-28.8907082ec9e34ee989cad62940b870e0.plex.direct:32400
Feb 03, 2021 13:36:14.283 [0x80bdab000] ERROR - SQLITE3:0x10, 8, statement aborts at 1: [BEGIN IMMEDIATE] attempt to write a readonly database
Feb 03, 2021 13:36:14.283 [0x80bdab000] ERROR - Failed to begin transaction (…/Library/Tag.cpp:159) (tries=10): Cannot begin transaction. attempt to write a readonly database
Feb 03, 2021 13:36:14.283 [0x80bdab000] ERROR - Thread: Uncaught exception running async task which was spawned by thread 0x80b587c00: Cannot begin transaction. attempt to write a readonly database

Except that none of the DBs should be read-only. They have write flags on the owner.

Hello??? I really could use some help here.

@Ridley can you help ping a Plex dev that can help with this? I’m not afraid to get technical.

The SQLITE errors are usually not referring to missing write permissions but some database corruption. That would also explain why your attempted changes don’t stick.

Can you check the database for corruption and attempt to repair it?

Thank you for the response, I will get right on that. .

Unfortunately, it didn’t help. The primary DB appears to be intact. It successfully dumped, and imported the dump, and passed all integrity checks. I did not an oddity. I see Plex working on another DB called, tv.plex.providers.epg.cloud-319568ff-dcf9-4816-afba-e3c4cb2611a4-loading.db, which the EPG is precisely what is broken right now. I noticed that it was missing write permissions, so I added the perms and restarted Plex, only for Plex to remove the write flags from the DB and get stuck in the same issue. This appears to be a bug.

See my new report

Ended up expanding the scope of the ticket ever further.

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