Sqlite3 error double-quoted string literal - correlated with video buffering/hangs

Plex Media Server
, ,
1

Server Version#: 1.23.1.4571
Player Version#: 8.17.1.25326

I have a recurrent yet frustratingly-random issue where Plex will start buffering a video during local LAN playback to an NVIDIA Shield TV (direct play, plenty of bandwidth headroom). This seems to be correlated with sqlite errors like this,

May 28, 2021 06:16:30.842 [0x7fe2e382eb38] ERROR - SQLITE3:0x80000001, 28, double-quoted string literal: "2019-12-18 14:24:50"

though I don’t see much of anything else of concern in the logs surrounding the event. Sometimes, the buffering is resolved, but other times the entire server seems to bog down indefinitely. This does not occur with the music library (directly play FLAC and transcoding), which is the other library I use extensively. Verbose logging was enabled at the time of the most recent error (attached).
Plex Media Server Logs_2021-05-28_06-23-54.zip (1.2 MB)

Seems similar to another issue on here ([BUG] Photos > SQLITE3:0x80000001, 28, double-quoted string literal: "2021-05-17 19:36:06"), but with a slightly different presentation.

Other details: the server is running off of linuxserver.io’s Docker image on an Intel NUC, and the videos are being pulled off of a Synology NAS on the LAN. The same issue was present when running Plex in a container on the NAS itself (I migrated the NAS Plex database to the NUC recently). I don’t use any other players to play videos so I haven’t yet tested whether the issue is present on other players. The issue has been present for at least the last couple of months (running beta releases most of that time).

2

Thanks for reporting.
I reported to engineering earlier this week and the issue has been solved.
The fix is working its way through QA now.

3

After looking at the logs, and some googling, I found that this is caused by some library called libva and the lack of support for NVIDIA hardware acceleration.

Turning off hardware acceleration fixed these issues for me. Hoping a future patch will fix this and allow me to re-enable hardware encoding.

4

@immortalblade

  1. Double quoted errors in the DB are not related to transcoding.
  2. Nvidia GPUs are supported.
  3. I did find a problem with the Debian configuration which impacts Nvidia GPUs and fixed it earlier today
  4. If you will provide the log files ZIP of it attempting to hardware transcode,
  5. I will review and,
  6. If the same problem exists, I will help you fix it now.
5

i will open a new thread as to not confuse this then. Will do later today.

6

Hi @ChuckPa, any idea when the DB fix will hit the beta channel? I’ve been testing the most recent releases but the issue persists for me as of now.

7

The version in PlexPass now has taken care of most of (if not all) them.

To share what happened:

  1. SQLite deprecated the use of double quotes.
  2. In deprecating it, to prevent breakage, they convert to single quote in the library AND print the warning.
  3. Given those double quotes are embedded in SQL statements –
  4. – AND double quotes are used in regular C++ code
  5. – finding them all by automatic search isn’t realistic.
  6. The only way to find them is read every line of code which uses SQLIte and visually check it. (Pain In The — task)

They think they got them all but it is possible a few slipped through.

Nothing is actually “broken” YET.

Therefore, If anyone sees any of these messages and knows what PMS is doing (reading the logs or know what actions were taken at the GUI) it will help point where to look.

Make sense?