I upgraded PMS using apt-get update && apt-get upgrade, but now I can’t access my previous library.
When I loaded the web client for the first time, it asked me to name the server (which I thought was unusual).
Now I appear to have 2 servers:
The new one - I named it “raspberrypi”. The server is empty, no libraries.
The old one - named “Raspberry Pi” - the web client says that this needs upgrading, and I can’t access it at all.
I can see that the library metadata (for the previous library) is still there in:
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server
I’ve read some topics on this forum, but I can’t work out what to do - and I don’t want to accidentally overwrite my previous library!
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server is the default location and most likely the location of the new and empty Library. So I suppose you did something unorthodox some time ago and have not updated your system in ages We have to find the location of your previous Library. Please take a look e.g. into /home/pi/Library and post the output of systemctl status plexmediaserver.
I have looked in /home/pi/Library and there is a set of folders there, but the Cache and Media folders (and others) are empty
However, the Library in /var/lib/plexmediaserver/Library/Application Support/Plex Media Server looks full.
Below is the output of systemctl status plexmediaserver (I had to re-type the output, so may be some typos sorry)
plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled)
Active: failed (result: start-limit) since Mon 2018-06-25 05:05:43 ACST; 13h ago
Process: 2360 ExecStart=/bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver "/usr/lib/plexmediaserver/Plex Media Server" (code=exited, status=255)
Process: 2356 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" || /bin/mkdir -p "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" (code=exited, status=0/SUCCESS)
Main PID: 2360 (code=exited, status=255)
Worked out how to get the text between computers. Here’s the full version of the output I got when I used
sudo systemctl status plexmediaserver
plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled)
Active: failed (Result: start-limit) since Mon 2018-06-25 05:05:43 ACST; 14h ago
Process: 2360 ExecStart=/bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver "/usr/lib/plexmediaserver/Plex Media Server" (code=exited, status=255)
Process: 2356 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" || /bin/mkdir -p "${PLEX_MEDIA_SERVER_APPLICATION_SUPPORT_DIR}" (code=exited, status=0/SUCCESS)
Main PID: 2360 (code=exited, status=255)
Jun 25 05:05:37 raspberrypi systemd[1]: plexmediaserver.service: main process exited, code=exited, status=255/n/a
Jun 25 05:05:37 raspberrypi systemd[1]: Unit plexmediaserver.service entered failed state.
Jun 25 05:05:43 raspberrypi systemd[1]: plexmediaserver.service holdoff time over, scheduling restart.
Jun 25 05:05:43 raspberrypi systemd[1]: Stopping Plex Media Server for Linux...
Jun 25 05:05:43 raspberrypi systemd[1]: Starting Plex Media Server for Linux...
Jun 25 05:05:43 raspberrypi systemd[1]: plexmediaserver.service start request repeated too quickly, refusing to start.
Jun 25 05:05:43 raspberrypi systemd[1]: Failed to start Plex Media Server for Linux.
Jun 25 05:05:43 raspberrypi systemd[1]: Unit plexmediaserver.service entered failed state.
PMS is controlled by systemd, the process manager on Raspbian. systemd tells us, that PMS was unable to start. So, if there is a PMS process currently running, it’s something not in control by systemd. That’s bad and the reason the “real” PMS with the correct paths is unable to start. I suppose you had setup some other process control mechanism before, e.g. monit (/etc/monit/conf.d/plex)? Some nightly auto reboot and and a auto PMS restart in case of a failure? Just remove all that stuff. It’s unnecessary, interferes with systemd and causes all your headaches. Just let systemd do it’s thing.
Just reboot your RPi after you have removed the other process manager and your old PMS should magically appear