Server Version#: v1.18.0.1846-f62172e99 -> v1.17.0.1841-d42cfa161 -> v1.18.0.1913-e5cc93306
Player Version#: N/A
I recently updated my pms-docker installation to v1.18.0.1846-f62172e99 with a simple restart of the container as I’ve been doing for the past few years. I was excited to see the new music library features so the first thing I did was to manually refresh the all of the metadata in my music library. And there were no problems! I saw plenty of complaints online, but I had no problems.
Everything was going fine for a couple days and then I saw a notification on my PMS homepage that there was a new release of v1.18.???. So I restarted my container as I always do and while the container came back up and appeared healthy, my PMS is shown as unreachable on all previously connected clients. I checked the logs and saw that it had attempted a downgrade to v1.17.0.1841-d42cfa161.
I see several of these lines in the Plex Media Server.log while running down migrations:
Oct 08, 2019 23:40:42.182 [0x7f004d126740] INFO - SQLITE3:(nil), 17, statement aborts at 57: [select * from metadata_items limit 1] database schema has changed
I checked pms-docker tags in the Docker registry and saw that the v1.18.0.1846-f62172e99 had been removed. Now today, there is a new release tagged v1.18.0.1913-e5cc93306 which I have pulled and installed (by restarting the container again). It ran forward migrations and there were several of the SQLITE3 info level messages again, but otherwise the logs look normal.
I’m able to access Plex Web at http://127.0.0.1:32400/web/index.html but it shows the Plex server as unreachable.
Is this a DB problem? Any ideas how to recover from this?
Plex Media Server.v1.18.0.1913-e5cc93306.log (484.1 KB)
