I feel like ever since I signed up for Discover Beta…my windows Plex Server has shown PlexScriptHost process eating up my CPU. It started with multiple processes stacking up over time causing 100% CPU…now I get a single process that runs as soon as I startup Plex/reboot windows and it never goes away and never drops below 25% CPU usage. What is running constantly and how do I figure out how to resolve? I have disabled Discover and everything else I can think of but I can’t seem to figure out why that process is running.
Verify that your boot drive + the volume where the Plex data folder is located (they are the same by default) have plenty of free space on them.
Have you tried a clean installation?
i.e.
Stop/quit/end Plex Server with the tray icon
deinstall Plex Server with the regular ‘Apps’ control panel of Windows
(do not use 3rd party ‘Uninstaller’ software like Revo etc.
do not use “Registry Cleaner/optimizer” software like CCleaner et al)
for safety, reboot Windows
download a fresh installation exe of the current version and install it (go preferably with the 64 bit version)
I tried the db cleanup tasks but that resulted in corrrupted db file so copied back the original and plex came back. During this process of stopping and restarting plex I no longer see the process start up immediately like before. I will keep an eye on this but possibly after disabling “Discover” beta from my account I never restarted this server process. Discover is when i first noticed these processes hitting the server hard…maybe the disabling and then restart of the server finally cleared it out. Will post again after a few days to confirm this was the fix.
Do you mean the ones in the Scheduled Tasks menu?
If they produce a corrupt database, it is on the brink of data loss. You need to act now and perform the steps of the “low-level recovery” urgently. If they don’t work on the current db file, perform them on one of the backups.
sorry I meant I followed steps on low level recovery. All the checks came back clean on that but I ran through all the steps and in the end I must have done something wrong since it corrupted the end file. Luckily teh “original” file in step 1 let me easily recover what was originally there. All working fine at the moment so assume even with all my restarts I must not have restarted the services after I finally disabled “Discover” options under Settings | Online Media Sources. Maybe that was still holding on until reboot? Is Discover part of the plexscripthost process and considered a plugin?
Discovery has nothing to do with a damaged database.
Try performing the repair again.
This time make sure that Plex server is not running during the procedure.
Sorry seems you are confused in what I am saying…here is recap of what happened and what seems to have finally fixed it:
Signed up for Discover Beta
My Windows Plex server started seeing hung/numerous PlexScriptHost.exe processes, frequently had to kill them (100% CPU)
Stopped using Discover Beta (didn’t work well, didn’t keep track of where I left off in series so what’s the point)
Less PlexScriptHost.exe processes but whenever I startup Plex at least one would come up at 25% CPU usage and never stop
Noticed I hadn’t disabled Discover under the Settings | Online Media Sources. I disabled all options under Discover
That process still was at 25% so I posted this thread
Upon Plex server process restart the process no longer comes back. Most likely I hadn’t restarted plex server process after disabling Discovery options.
No db corruption, no other issues. I corrupted a copy of my db file following those recovery steps but that was probably an error I made in the instructions. No harm no foul since I had made a copy of my original and recovered that and was back online.
At this point over muliple days my plex server is running with low CPU in normal mode which it hadn’t done in months so I am happy.
