Look here. This was just posted
@ChuckPA said:
Look here. This was just postedhttps://forums.plex.tv/discussion/comment/1479621#Comment_1479621
Thanks ChuckPA! This does seem to be the exact issue as I see some of the same SQLite errors from that post as I do on mine. This mostly likely means if you only RDP into your server for management, you will have issues if you cleanup temp folders/perform a disk cleanup.
I’m curious what Plex is saving in the %localappdata% temp folders… if these files/folders c an be redirected that will alleviate this kind of issue.
Run Plex server as a system service and this will be a non-issue.
Sqlite3 appears to be using temp files - for some reason only sqlite3,s affected. Zipping the logs also uses temp and I do not believe is failing
If certain channels won’t work while running as a service, this is a no go for me. I use channels all the time. A refresh of the page on the web, or reload of PMP usually restores the dashboard. An annoyance is far easier to deal with.
Don’t think running as a service is a factor
It is to do with the windows policy discussed here
It is still not known as to why this has become an issue now and whether there has been any windows updates or if it is within plex
Running as a service was my next choice to start testing so thanks for the link Otto.
While yes the creation of the temp folders per terminal services session are created, even when I don’t logout of the session that running PMS, somehow that “2” folders get cleaned up during some Plex transaction causing the dashboard again to fail.
I don’t have any scheduled task that do cleanup or anything so I am assuming the terminal session is somehow doing it or it is plex.
Are there any downfalls to running as a service? Any reason why not too?
@EricnM said:
Are there any downfalls to running as a service? Any reason why not too?
Most of the con’s are mitigated by the service wrapper.
I understand, even the update process is somehow cared for.
(Normally, installing a new version of PMS will create an entry in the Autorun branch of the Registry. Without the service wrapper, you’d have to remove it yourself so that plex is not attempting to start [a second time] as soon as you log into your Windows account.)
Using the hardware transcoding abilities is also not possible, currently (but that is only possible with a special preview version of PMS anyway.)
Main advantage (besides the ‘running while no user is logged on’) is that you can create a special Windows user account just for Plex. Then you can tailor its privileges to minimize attack surface and also to protect against malfunction.
For instances I only allow Plex to write into a few media folders (for DVR and ‘optmized versions’).
Most folders are ‘read-only’ for Plex on my server.
The same can be done with PlexPy, btw. with a bit of tinkering.
@EricnM said:
While yes the creation of the temp folders per terminal services session are created, even when I don’t logout of the session that running PMS, somehow that “2” folders get cleaned up during some Plex transaction causing the dashboard again to fail.
I don’t have any scheduled task that do cleanup or anything so I am assuming the terminal session is somehow doing it or it is plex.
If this is easily reproducible after a relaunch of plex media server, I would love to have a look at a procmon capture covering period from launch up to time when the temp
\ folder disappears and the hubs fail to load
So if possible please download Microsoft SysInternals Process Monitor and unzip it and prepare it to use to get a PML file
Enable verbose logging together with debug logging in plex media server
Shutdown plex media server
Launch procmon.exe and run as adminstrator capturing all events
Launch plex media server
As soon as the hubs issue arises, stop the procmon capture
Save all events to a PML file and exit
Zip the PML file
Disable verbose logging leaving only debug logging in the plex media server settings
Get the plex media server logs zip
Post here and upload the zipped PML on Dropbox or similar service and send me link by private message