I’ve read a bunch of topics, but nothing is working out for me. I’m a bit of a linux noob. This is a VM running 18.04 LTS, upgrade as some point in the past from 16.04 LTS.
Issue: Upgrading past 1.14.x results in no more server settings page or media matching.
Something seems odd from my setup trying to follow the instructions elsewhere to put user customizations in /etc/systemd/system/plexmediaserver.service.d/override.conf
plex@plex:~$ sudo dpkg -r plexmediaserver
(Reading database ... 143368 files and directories currently installed.)
Removing plexmediaserver (1.16.6.1592-b9d49bdb7) ...
Removed /etc/systemd/system/multi-user.target.wants/plexmediaserver.service.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
plex@plex:~$ sudo dpkg -i plexmediaserver_1.16.6.1592-b9d49bdb7_amd64.deb
Selecting previously unselected package plexmediaserver.
(Reading database ... 140265 files and directories currently installed.)
Preparing to unpack plexmediaserver_1.16.6.1592-b9d49bdb7_amd64.deb ...
Unpacking plexmediaserver (1.16.6.1592-b9d49bdb7) ...
Setting up plexmediaserver (1.16.6.1592-b9d49bdb7) ...
Created symlink /etc/systemd/system/multi-user.target.wants/plexmediaserver.service â /lib/systemd/system/plexmediaserver.service.
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Processing triggers for mime-support (3.60ubuntu1) ...
Processing triggers for ureadahead (0.100.0-20) ...
Same redirect, but after login (with email/UN) I get:
Seemed stuck in a loop for a while, but after a few tries and/or clicks of the “Sign In” button it loads. No change, no settings.
There’s also an nVidia Shield on my LAN running a server (for 4k) but this issue predates it. Been stuck on 1.14 since later was released as a workaround.
stop plex
rename Preferences.xml to Preferences.xml.old
start plex
while in the VM’s browser: open http://127.0.0.1:32400/web
sign in,
claim it
begin setup EXCEPT Do not create new library sections. We are only resetting ownership.
Now exit the VM
Settings - Devices - Servers - delete the old instance name
Now it should open if the VM is working correctly.
If not, there are networking problems beyond what PMS can see & report.
VM is headless, but renamed and tried again with the SSH method. Same result. From your mention of networking I double-checked firewall stuff. Seems something is different with current releases from whatever guide I read years-past. Setup UFW and applied all the rules…
Got to the setup screen this time! “Please wait a moment while Plex starts.”
Then:
“A problem has been detected with a core component of Plex Media Server.
Please visit the forums and provide your logs, as described here.”
The SSH method is now displaying some XML-type file.
Well, I can consistently access the setup page now. No luck getting past “problem detected” though. Waited minutes at each page for anything to catch up, monitored “top”, ect.
Lots of these pop into the logs when it gets stuck:
Setup a new TEST server. **BE CERTAIN: Give this a ‘TEST’ name to avoid colliding with the real name (hostname is used by default.
If this completes successfully then there is a corruption deep in your existing installation. The next steps will include transferring any data, deleting it, then renaming the new instance (the test one) to have the name of the old.
WARN - Warning: ex: boost::filesystem::last_write_time: No such file or directory: "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-ins", couldn't check file: "/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Plug-ins"
The plugin folder didn’t get recreated when it rebuilt Library down it seems.
Been running 1.14 or lower for several years without much issue. Seen it pulling of ~6 transcodes at a time.
ESXi 6.7 U2 virtual machine
Has access to 6 logical of an i7-5820K
Are you using their current emulation or have you backed it off to 13.x (something ??)
There was a major Ubuntu compatibility problem IIRC which made PMS go nuts.
