Hello
When there is no space left on device, Plex erase/corrupt the Preferences.xml file by a new one (empty), when we restart the server, the server becomes unreachable with the error “No Soup for you”.
The new generated file looks like this one:
<?xml version="1.0" encoding="utf-8"?>
<Preferences OldestPreviousVersion="1.18.8.2527-740d4c206" MachineIdentifier="[REMOVED]" ProcessedMachineIdentifier="[REMOVED]" AnonymousMachineIdentifier="[REMOVED]" MetricsEpoch="1"/>
This bug exists since years, I don’t know if it was already reported.
I made a copy and I restaure it manually each time I have the issue
This isn’t a bug.
This is how Linux behaves when the 10% margin has been exceeded. It will not allow future writes until below the min free setting of the filesystem.
This also occurs when the number of inodes has been exceeded.
The solution:
Moving Plex’s metadata (Library) directory on systemd based systems
This information is intended for those systems where cat /proc/1/comm returns systemd. If your system returns init, please see the next post in this thread.
While you may change /lib/systemd/system/plexmediaserver.service, it is under the control of the package manager and subject to replacement without warning at any time during an update. To provide stability, systemd allows creation of an override.conf file to customiz…
system
August 12, 2020, 7:32pm
3
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
