[Bug] 1.23.6.4863 PMS (beta) - SQLite3 DB Locked

Plex Media Server NAS & Devices
1

Server Version#: v1.23.6.4863-6b3792414
Player Version#: app.plex.tv (hosted)

I just installed the latest PMS and there seams to be a problem with access to the DB. The PMS logs only contains the following:

Jul 26, 2021 17:59:23.434 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:25.676 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:27.908 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:30.134 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:32.358 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:34.595 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:36.825 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:39.053 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:41.278 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:43.504 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:45.730 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:47.956 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:50.182 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:52.409 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:54.638 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:56.865 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 17:59:59.092 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 18:00:01.322 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 18:00:03.552 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 18:00:05.789 [0x7f0b1ea3cb50] WARN - Waited one whole second for a busy database.
Jul 26, 2021 18:00:07.001 [0x7f0b1ea3cb50] ERROR - Database corruption: sqlite3_statement_backend::loadOne: database is locked
2

Looks like the SQLite3 process hangs (i guess). I did not previously have a problem with locked DB.

I tried to rollback a couple of versions. Rebooted - and it worked again. Updated to the latest (beta) version and it works. Looks like the latest fix doesn’t solve it completely (reboot required).

3

Can I convince you to try one more time so the full ZIP logs can be uploaded here and the issue investigated? A filtered excerpt is not enough to go on.

It can’t be addressed without more info.

4

I would try again, but I think it will be hard to reproduce. Since I restarted the NAS and it works now. I did notice the previous release also had a fix for locked DB. This is the first time it has happened to me (no beta QNAP fw - just current stable rel)

The logs posted previously was actually the only log file that existed in the logs folder. Only missing the HW info.

Could you recommend some specific steps? I would gladly give it a try.

5

what firmware did you have when you upgraded PMS and what was the sequence?

If you can replicate the sequence – as close as you remember – that would be great.

Was PMS streaming at the time or running media scanning ?

6

I’ll give it another try. I have “all” PMS versions available locally.

QNAP FW: 4.5.4.1723 (latest official stable)
PMS: Had no active streams/users. DVR idle.

Downloaded the latest PMS beta.
Updated it manually by QNAP “App Center” (did not stop Plex service before update)
Update completed without any problems.

I noticed in PlexWeb (hosted - google devtools), that it couldn’t connect to websockets (it tried 3 different - and one strange websocket host: 253.253.253.253). I could browse some sections - but clicking the latest movie I had added 5 min before - made everything hang.

7

I think I ran a Optimize database at the same time i clicked the recent added movie.

8

This was the PMS log. No other logs existed in the logs folder, when this happened. I always clear the logs folder, when something strange happens. This time i forgot to make a backup, before delete though.

Plex Media Server.5.log (2.5 KB)

9

I restored DB and PMS to the state of yesterday:

  1. Stopped PMS.
  2. Cleared logs folder.
  3. Restored backup of “com.plexapp.plugins.library.db” from yesterday.
  4. Rolled back to PlexMediaServer-1.23.6.4810-15ce0e21a.
  5. Opened PlexWeb
  6. Waited for PMS to add the 2 new movies and update DVR EPG.
  7. Empty trash (one movie deleted from FS)
  8. Installed PlexMediaServer-1.23.6.4863-6b3792414 in QNAP “App Center” (did not stop PMS before update)

It still works (like before). Sadly it is kinda hard to reproduce, when the server has been rebooted I guess.

@ChuckPa would you still like a copy of the logs?

10

Next time it burps - then grab the logs so I can see what’s happening.

Please keep your eyes open for a PMS update (PlexPass).

Engineering was aware of the “database is locked” condition and fixed at least one.

1 Like
11

Known issue:

1 Like
12

2 posts were split to a new topic: PMS 1.24.3.5033 database locked

13

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