Server Version#:plexmediaserver-1.18.8.2468-5d395aa9d.x86_64
Player Version#: 4.26.1 (Plex Web)
Recently installed a fresh version of plex media server and let it rebuild my libraries. For some reason I cannot get search to work - everything else works fine.
Logs produce the following whenever I try to use search:
ERROR - SQLITE3:(nil), 1, statement aborts at 16: [select distinct(tags.id) from metadata_items join taggings on taggings.metadata_item_id=metadata_items.id join tags on tags.id=taggings.tag_id join fts4_tag_titles on fts4_tag_titles.
I’ve tried running through the usual database repair/optimize procedures (drop index, dump to sql, reload from sql, etc) to no avail. Same result. Pragma integrity check comes back fine.
Loading up sqlite3 and running that query above produces an empty result. Is that correct?
Can’t tell anything in abstraction with an excerpt.
It’s impossible to know if that’s come from a failed or interrupted database migration (schema update) during installation.
The biggest cause of such errors occurs if the server is upgraded and immediately called on to start performing tasks before the migrations are complete.
This is why the log files are necessary. They will show the timing relative to when PMS started.
If this occurs before migration is complete, then answer it’s one situation.
If this occurs after the server has been faithfully running, then it’s clearly something else.
Thanks @ChuckPa -
This server was installed in early January 2020, looks like version plexmediaserver-1.18.4.2171. After the libraries completed scanning (metadata, etc), search was found to be not working. I tried several of the database repair routines without success, and just upgraded to version plexmediaserver-1.18.8.2468 today - thinking that might help things. No luck - but I am running an “refresh all metadata” on all libraries to see the result.
Would a collection of logs after a fresh start of the server be helpful?
Here’s the logs collected from the “Download logs” link in the web player. I can also scrub these and provide logs from a fresh start is that’s helpful
This is troublesome to me. Server installed in January. I’m just learning of this issue now?
Thank you for the logs but please put them back to the default logging settings.
DEBUG = ON
VERBOSE = OFF
Verbose generates so much noise I can’t find anything. Secondly, it only captures about 2 minutes of elapsed time. VERBOSE is to be used ONLY when expressly requested (which is why it’s off by default.
I haven’t seen any other related posts, so I am inclined to believe this is an isolated incident. I’ve been troubleshooting it for a while as time permits as it’s not fatal, just an annoyance, but I’m here now posting as I’ve run out of ideas Obviously my end game is just to see if there’s a way to repair this without having to completely start from scratch. Library rebuild takes a while.Plex Media Server Logs_2020-03-07_20-28-13.zip (2.0 MB)
I had verbose logging on for support of another tool - sorry about that.
Restarted on debug only, clean logs attached, with a search for at around “Mar 07, 2020 20:25:41.143” in the logs. The error appears there.
Obviously my end game is just to see if there’s a way to repair this without having to completely start from scratch. Library rebuild takes a while.