I recently Changed my metadata location from F:\Plex\Metadata to E:\Plex\Metadata. While the Plex Server seems to recognize this change, the Plex Update Service does not.
It is still logging to F:\Plex\MetaData.
How can I Change this ?
I have tried logging out, Restart Plex. Restarting Computer, Restarting service.
Thanks!
Also Tried uninstalling Plex and Reinstalling.
Found it…
Had to modify registry value at
HKEY_USERS.DEFAULT\SOFTWARE\Plex, Inc.\Plex Media Server\
Modify LocalDataPath
Stop Plex Update Service
Start Plex Update Service
Logs are going to the right place now.
@synicasm please could you clarify the sequence in which you made the changes.
Changing the Server setting The path where local application data is stored within Advanced Server Settings / General (See support page https://support.plex.tv/hc/en-us/articles/200289496-General) should have updated the registry entry HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server and created / amended LocalAppDataPath
I would have expected this to work after restarting Plex Media Server and the associated services - or just a reboot
Was there already a Plex, Inc. under HKEY_USERS.DEFAULT\SOFTWARE\
and was there a LocalAppDataPath ?
Just checked one of my servers and I have no Plex entries in the .DEFAULT profile
You meant to say LocalAppDataPath rather than LocalDataPath ?
Big TNX to the O.P. coz I had the exact same problem and Plex (or more particularly the Plex Update Service) kept re-creating the path which I wanted to move and I had already deleted. @synicasm 's solution worked and it seems to be a band-aid patch to a bug in Plex when changing the Server setting “The path where local application data is stored” within Advanced Server Settings / General (See support page https://support.plex.tv/hc/en-us/articles/200289496-General).
To answer @sa2000 :
Was there already a Plex, Inc. under HKEY_USERS.DEFAULT\SOFTWARE\
and was there a LocalAppDataPath ?
– YES and YES.
You meant to say LocalAppDataPath rather than LocalDataPath ?
– LocalAppDataPath.
Thanks for the info - I would expect it to be just the fact that the service was not stopped
Shutting Down Plex Media Server leaves the Plex Update Service running
I will have the issue looked into - but wondering if this would have been adequate:
@sa2000 : Please read O.P.'s original question… he did all that you enumerated. As did I. As did numerous other permutations of start/stops of Plex server and Plex Update service. It’s easy, I think, to recreate the problem. The bug is that the Plex Update Service does not follow the LocalAppDataPath of the server if it is changed. Thanks.
This issue might still exist. I followed https://forums.plex.tv/discussion/comment/851746/#Comment_851746 though between steps 3 & 4 I moved the old metadata out of the way. Is that obviously foolish or is Plex still bugged?
Either way I experienced this problem & https://forums.plex.tv/discussion/comment/1268072/#Comment_1268072 above fixed it. Thanks to @synicasm
@Cauli said:
This issue might still exist. I followed https://forums.plex.tv/discussion/comment/851746/#Comment_851746 though between steps 3 & 4 I moved the old metadata out of the way. Is that obviously foolish or is Plex still bugged?Either way I experienced this problem & https://forums.plex.tv/discussion/comment/1268072/#Comment_1268072 above fixed it. Thanks to @synicasm
Thanks for your post. I don’t believe there has been any change since it was first reported.
Please could you tell me if there is an actual impact to the operation of Plex Media Server or is it just that the Plex Update Service continues to write to logs to the old location?
@Cauli said:
This issue might still exist. I followed https://forums.plex.tv/discussion/comment/851746/#Comment_851746 though between steps 3 & 4 I moved the old metadata out of the way. Is that obviously foolish or is Plex still bugged?
The linked guide explicitly requires in step 2) that the Plex Update Service be stopped, before touching the plex data folder.
@sa2000 said:
Thanks for your post. I don’t believe there has been any change since it was first reported.Please could you tell me if there is an actual impact to the operation of Plex Media Server or is it just that the Plex Update Service continues to write to logs to the old location?
I only ran the system in that state for around 12 hours during which time it had light use. There were no obvious issues outside of the log concerned being written to the old location. Another folder was also created next to Logs however I never saw any other files within.
I did wonder what might have happened if the old location had ceased to be writable but didn’t investigate.
@OttoKerner said:
@Cauli said:
This issue might still exist. I followed https://forums.plex.tv/discussion/comment/851746/#Comment_851746 though between steps 3 & 4 I moved the old metadata out of the way. Is that obviously foolish or is Plex still bugged?The linked guide explicitly requires in step 2) that the Plex Update Service be stopped, before touching the plex data folder.
As I said, I followed the guide with the addition of a step between steps 3 & 4. From this it follows I didn’t do anything, including touching the plex data. prior to step 2, aside from step 1!
Your response is therefore a non sequitur. I can only assume you misunderstood me.
@Cauli said:
@sa2000 said:
Thanks for your post. I don’t believe there has been any change since it was first reported.Please could you tell me if there is an actual impact to the operation of Plex Media Server or is it just that the Plex Update Service continues to write to logs to the old location?
I only ran the system in that state for around 12 hours during which time it had light use. There were no obvious issues outside of the log concerned being written to the old location. Another folder was also created next to Logs however I never saw any other files within.
I did wonder what might have happened if the old location had ceased to be writable but didn’t investigate.
What was the other folder that was created ?
That registry area is under .DEFAULT in HKEY_USERS because that service runs under SYSTEM account and yes that LocalAppDataPath is not being changed - but it is probably of no real impact other than the logging
@sa2000 said:
What was the other folder that was created ?
I was worried you might ask that. I think I saw an empty “Plex Media Server\Plug-in Support\Databases” but I can’t say that was its name with 100% certainty. Sorry; I ought to have made a note given I know my memory & concentration are poor these days.
@Cauli said:
@sa2000 said:
What was the other folder that was created ?I was worried you might ask that. I think I saw an empty “Plex Media Server\Plug-in Support\Databases” but I can’t say that was its name with 100% certainty. Sorry; I ought to have made a note given I know my memory & concentration are poor these days.
I have gone through the steps. Your memory is ok. It was the Databases folder - but empty.
I will try and find out why it creates the databases folder
Problem persists, I also had an empty databases folder show up in the old location, which didn’t exist anymore and was recreated with just the service logs.
Changing the registry value in .USER like you said fixed it. Thanks!
@senorbubbz said:
Problem persists, I also had an empty databases folder show up in the old location, which didn’t exist anymore and was recreated with just the service logs.Changing the registry value in .USER like you said fixed it. Thanks!
I know the issue is still there but as far as I know there is no real impact - it is just the log that for this service that goes to the old location and yes an empty database file is created - no impact to the running of the Plex Media Server.
If you believe there is an impact - please let me know what it is with some evidence and I will communicate that to the development team
I just lived this scenario. I made my second move of the Plex files on the same server after adding more disk space. I THINK what happens is the key may be created on the first move as discussed using the GUI but once the KEY(s) is/are created it never gets updated. I had to go through the registry and correct multiple paths that remained homed on the first move location (which appeared to be successful).
Easy enough for you folks to recreate and test. Create a clean install. Follow your procedure to move the location and include an obscure string in the path like Z:\XXYYZZAABBCC, move the location again and then search the registry for that obscure string ZZYYZZAABBCC.
Probably needs to be cleaned up.
@Smokindog said:
I just lived this scenario. I made my second move of the Plex files on the same server after adding more disk space. I THINK what happens is the key may be created on the first move as discussed using the GUI but once the KEY(s) is/are created it never gets updated. I had to go through the registry and correct multiple paths that remained homed on the first move location (which appeared to be successful).Easy enough for you folks to recreate and test. Create a clean install. Follow your procedure to move the location and include an obscure string in the path like Z:\XXYYZZAABBCC, move the location again and then search the registry for that obscure string ZZYYZZAABBCC.
Probably needs to be cleaned up.
Yes it is not updated. It should not cause a problem unless the old location no longer exists
The registry edit needed is to this item - and it is only needed to be edited if it exists
Computer\HKEY_USERS\.DEFAULT\Software\Plex, Inc.\Plex Media Server\LocalAppDataPath
@sa2000 said:
The registry edit needed is to this item - and it is only needed to be edited if it exists
Computer\HKEY_USERS\.DEFAULT\Software\Plex, Inc.\Plex Media Server\LocalAppDataPath
I suggest you run the test I outlined for you.
As of 2019-12-01 this bug is still present in the latest version of Plex Media Server (running on Windows Server 2012). The update log file was created along with the empty database directory after moving the metadata location. Changing the registry as @Smokindog suggested fixed the issue.
