I will do so. Can you tell me what state you expect that directory to be in? It should exist when the application is installed? It’s missing on my system right now (which presumably explains why it doesn’t start), but the last re-install didn’t add it back.
The only thing in that directory right now is a Services.bundle:
[######@######-server ~]$ ll /home/######/plex/Library/Application\ Support/Plex\ Media\ Server/Plug-ins/
total 0
drwxr-xr-x 3 ###### ###### 22 Dec 15 2018 Services.bundle
I have now re-installed again, with a reboot in the middle for good measure, with still no change to behavior. Neither the removal nor the installation removed the override file, so plex started up immediately after install with my override and loading from my modified location. At no point was there ever a System.bundle directory under Library/Application Support/Plex Media Server/Plug-ins, the only thing there is still Services.bundle.
It should provide a new Services.bundle IF you’ve deleted it prior to reinstalling & restarting Plex.
The problem some face is a corrupt bundle download. Why that happens isn’t clear it’s a simple wget call which either succeeds or doesn’t.
Think back to initial startup which is where nothing exists and all must be retrieved.
If you want to verify all your network routing and everything is good,
Library to Library.keep
I see, your previous comment mentions ensuring System.bundle doesn’t exist, I don’t believe you’ve mentioned Services.bundle before. If you think a new Services.bundle will make a difference, I can do the re-install test again while making sure that directory is removed.
Take out both bundles from the Library directory and restart
It’s a good idea as well.
sorry I missed that.
I removed the Services.bundle directory and after reinstall, it was not replaced, I now have nothing in my plugins directory at all.
Here are the logs for the startup after that, interestingly the server still runs and seems to be in the same state it was before? My girlfriend was definitely watching something this time, so her stream picks back up as soon as the server begins starting up.
plex-logs.zip (2.3 MB)
I tested renaming my Library directory as you’ve suggested and got a weird result. Plex created a new Library directory and seemingly most of the subdirectory and files it’s expected to, but it did not create a Plug-Ins directory, and the logs are full of errors trying to write to that non-existent directory. Here are the logs from that attempt:
plex-logs1.zip (14.2 KB)
That’s bizarre. Go help it out?
Stop Plex,
Create the Plug-ins directory
Start it.
Something bizarre is going on here.
You might want to ask here to WAIT until you’ve got things working again before attempting to stream.
Okay, I manually created the Plug-ins directory with the same owner and privileges as everything else, and the logs are definitely no longer full of warnings checking for that directory, but the server does not respond at https://192.168.1.13:32400/web
I’m now completely baffled, but I think it’s listening only for IPv6:
[######@######-server ~]$ sudo netstat -nlp | grep 32400
tcp6 0 0 :::32400 :::* LISTEN 3547/Plex Media Ser
Logging clearly shows it detects the IPv4 address as the only address on the system:
Oct 22, 2019 17:03:58.610 [0x7f98a23c8740] DEBUG - Detected primary interface: 192.168.1.13
Oct 22, 2019 17:03:58.610 [0x7f98a23c8740] DEBUG - Network interfaces:
Oct 22, 2019 17:03:58.610 [0x7f98a23c8740] DEBUG - * 1 lo (127.0.0.1) (loopback: 1)
Oct 22, 2019 17:03:58.610 [0x7f98a23c8740] DEBUG - * 2 enp0s25 (192.168.1.13) (loopback: 0)
Oct 22, 2019 17:03:58.610 [0x7f98a23c8740] DEBUG - Creating NetworkServices singleton.
Here’s the rest of the logs:
plex-logs.zip (26.2 KB)
I re-applied the change to disable IPv6 support in Plex in the newly created Preferences.xml file, that got Plex at least listening for the right protocol but it still doesn’t respond to requests.
Here are the logs after making the change in Preferences.xml to disable IPv6:
plex-logs1.zip (35.8 KB)
Please check your PM.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
