Server Version#: 1.15.0.647 and 1.15.0.659
Player Version#: n/a
After upgrading to either Plex Media Server 1.15.0.647 or 1.15.0.659 on Windows 7 Ultimate with SP1, the server starts and then stops after a few seconds. Attempting to manually start the server causes the same behavior: the server starts and after a few seconds stops.
My only remedy has been to uninstall Plex Media Server and then install the downloaded public channel version 1.14.1.5488, which works fine. Subsequently upgrading to either of those beta channel versions again causes the same behavior. I have switched to the public channel until this issue is resolved.
You database looks like it might be corrupt. This could prevent PMS from starting.
Find the database file and rename it. PMS will recreate a new one. See if that gets things running. Then you can look to repairing the database and putting it back.
I will look into this. However, if my database is corrupt why would this same database work fine with Plex Media Server 1.14.1.5488 but not versions 1.15.0.647 or 1.15.0.659? I would expect to have the problem regardless of the PMS version I use if the database were the problem.
I tried moving my db and letting PMS create a new one. Next, I upgraded PMS to version 1.15.0.659. To my surprise, after the upgrade, PMS continues to run and does not stop.
MovieFan.Plex, it seems you were right and I was wrong. My db does indeed seem to be the root of the problem. Thanks for your help.
Looks like I spoke too soon. The problem is not resolved.
I checked my db for corruption using sqlite3 and it reported the db was ok. Nevertheless, I repaired my db using sqlite3’s dump function. This compacted its size from 150MB down to 136MB. I was able to successfully load this repaired db into PMS version 1.14.1.5488. I spot-checked the metadata and all seems well.
Next, I upgraded PMS to version 1.15.0.659 and the server started and then stopped after a few seconds again. Attempting to manually start the server yielded the same results.
So, apparently there is something about my database that PMS version 1.15.0.659 can’t work with. Starting over with a fresh db is an option I don’t want to contemplate since I have spent countless hours over the years customizing the metadata in my libraries.
This alerts me to the precariousness of my metadata. Is there a way to export the metadata from Plex and later import it to a fresh db?
For now it works, I also did a repair of the database even if it had no error. But with the difference that I updated the server in 1.15.0.659 before relaunching it. He has updated the library at startup and everything seems to work for the moment.
Pms will update a database from time to time, so it’s possible one of these updates is not working and stoppping pms. You can try dumping you database then importing it into the blank database that 1.15 created. If that doesn’t work, pm me your database and I’ll see if i can get it fixed for you.
I’m unsure how to import my db into a blank db created by 1.15. Here’s what I did:
Dumped my db into file dump.sql.
Ran “sqlite3 com.plexapp.plugins.library.db < dump.sql” where “com.plexapp.plugins.library.db” is a blank db created by 1.15.
I got all kinds of errors (unique constraint failed, index already exists, trigger already exists, etc.). Plex 1.15 failed to run using the resulting db.
I will pm my db to you to see what you can do. Thanks for your offer to work on it.
Same here, after updating to 1.15.0.659 the server force closes itself after a few minutes or after I try searching for something within the web interface. I’ve restarted it at least 10 times before coming to the forums to see if it’s a known issue which it seems to be.
yep same problem here, after upgrading to 1.15 videos hang at like 10 mins and 15 min intervals for all my users and PlexTranscoders fail, what the hell have they done, they have more like destroyed it.
@dualznz: The problem you’re describing doesn’t sound like the same issue I’m describing. I’m describing a problem that prevents Plex Media Server from running. The source of this problem seems to be PMS 1.15’s inability to work with or update my PMS 1.14 database file.
You might want to post a separate topic with the details of your problem.
@dualznz: Yeah, sounds like your problem is in 1.15 if a rollback fixes it. But your problem is not likely to be related to the database file which as far as I know isn’t involved in handling video playback or transcoding. I still think you should post your problem to a separate topic so the devs can be aware of it and address it before they roll 1.15 out of beta.
I am experiencing a similar problem and opened a thread of my own. In general, I have not had much luck transcoding 4k at all. This latest beta version seems to have taken a step backward in transcoding.
Good to know I am not alone, the version 1.14.1.5488 is working well on my Synology, however, newer versions are malfunction, no matter direct update or rebuild database new.
I even try disable all Online Media Sources(TIDAL ,NEWS and so on), Plex media server still CPU usage over 50% (I guess one core is on full cylinder with my two cores cpu), forbid Remote Access still the same.
So I have to roll back to 1.14.1.5488 version, and hope the team fix the problems in next release version.
welp. skipping 1.15 until the releases mature. I hastily updated to 1.15.0.647 version on my seedbox and things went downhill right after. I can’t afford to repair db since I might not have enough privs to perform a repair.
