Plex Database folder not updated in the config

The new update broke my installation. I redid the install, but the service still fails to start, throwing this error in the Plex log file:

Feb 22, 2017 10:45:02.378 [0x7f3beaad6800] ERROR - FATAL ERROR: Codecs: Initialize: 'boost:
:filesystem::create_directory: Too many levels of symbolic links: "/media/20b65062-b646-419
c-8b51-393b73d64796/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/c9
ea179-1157-linux-ubuntu-x86_64"'

Zitat von Tom

The new update broke my installation. I redid the install, but the service still fails to start, throwing this error in the Plex log file:

Code

Feb 22, 2017 10:45:02.378 [0x7f3beaad6800] ERROR - FATAL ERROR: Codecs: Initialize: 'boost:
:filesystem::create_directory: Too many levels of symbolic links: "/media/20b65062-b646-419
c-8b51-393b73d64796/plexmediaserver/Library/Application Support/Plex Media Server/Codecs/c9
ea179-1157-linux-ubuntu-x86_64"'

OK, I fixed it by removing some symlinks here and there. All in all a troublesome experience.

Zitat von mbourd25

Hi gang, I am finally able to see the Plex server, but I had to point my Plex webpage to openmediavault.local:32400 instead of my regular 192.168.1.116:32400 plex webpage.

The IP address of my OMV server is 192.168.1.116, how come it can't see that address for my Plex webpage?

Thanks gang for your help.

Maybe this is a dumb question but have you tried to ping openmediavault.local to se if you get that ip? And did you remember the /web at the end. Some times it also helps to clear the browsers' cache or open an incognito tap.

Zitat von henkall

Maybe this is a dumb question but have you tried to ping openmediavault.local to se if you get that ip? And did you remember the /web at the end. Some times it also helps to clear the browsers' cache or open an incognito tap.

Hi henkall, I already cleared the cache, used another computer in my house. I even used one of my tablets and I still couldn't reach the server by pointing to 192.168.1.116.

But forgot about trying to ping the server to both IP address and name server, I will try that tonight.

Thanks for your help and ideas.

Did you install the Plex pass version of PMS?

that's why you're getting that error message. The repo only has the public version.

Zitat von pezman

Anyone know why i'm getting this error when updating apt list
W: Conflicting distribution: https://downloads.plex.tv public InRelease (expected public but got )

That is probably related to this:
http://forum.openmediavault.or…-omvextras-3-4-17-SOLVED/

Zitat von henkall

Maybe this is a dumb question but have you tried to ping openmediavault.local to se if you get that ip? And did you remember the /web at the end. Some times it also helps to clear the browsers' cache or open an incognito tap.

Hi henkall, I just pinged my omv server using the server name, openmediavault.local, and it returned 192.168.1.116.

Why is Plex not responding to it's ip address?

That is odd. Have you tried 192.168.1.116:32400/web
Or
Openmediavault:32400/web

I seem to be running into this issue now as well. Running OMV 3.0.76 but just now noticing this has been going on since I set it up. The directory I'm pointo to for the database is not being used, instead it's in /var/lib

I should have noticed something sooner. A while ago I whacked the server, had to rebuild it since I was re-building the raid (Expanding it) from 2 drives to 4. When I set up plex, I pointed it to the same folder that was already there from the previous build with all the metadata and such and it came up empty. But my login info was still there? Weird. I've noticed my system drive got really full all in a short period and is still expanding, come to find out it's the damn plex folder.

1. How do I move this? (I'm guessing rsync job of course)
2. How do I solve this? Gui/Plugin still broken? I mean nothing has been posted here for months but here I am with the same problem after several upgrades to OMV and to Plex itself. Latest upgrade was right from the OMV Plugins themselves and not done manually.

Try this.

Disable the plugin and Save the changes. Then enable the plugin and save the changes. This can take a long time to complete so be patient.

Zitat von gderf

Try this.

Disable the plugin and Save the changes. Then enable the plugin and save the changes. This can take a long time to complete so be patient.

This has been done a few times to be honest, misc config changes and upgrading Plex manually caused me to turn it off and on. By Disable you mean forcefully through services or through the Plex WebUI? I mean will it move my DB to that folder?

I mean in OMV GUI | Services | Plex Media Server | Settings as seen in this attachment.

However, it should also be ensured that the release is not written up and contains no soder symbols.

Zitat von gderf

I mean in OMV GUI | Services | Plex Media Server | Settings as seen in this attachment.

I have done that, multiple times since the DB swelled up. So this time I've disabled the service, then I renamed the existing folder on the raid to plexmediaserver.old and moved it to a temp dir on the raid. I then enabled the service and now it seems to be writing the DB there? I'm guessing it's copying it so i'm going to let it sit for a while. If it's moving them, great. If not, I'll let it run for a week and make sure it's cool before cleaning up the system drive. Not sure why it did this before and why it didn't pick up on the existing DB when I rebuilt the bastard. But hey, no harm so far.

It moved the files to the raid, so now they are in the right spot. I'll monitor it and make sure it stays there. Who would have thought the stupid and easiest option would work. Dunno why it never caught on before, I've reset it several times.

Hi guys, sorry if this thread is a little old, but it's the exact same problem I had.

I found out after my transmission stopped all downloads because of "no space available" that Plex was using /var/lib/plexmediaserver instead the mergerfs directory.

I tried to put outside the mergerfs also, but it started give me (error=255) when launching the pms binary with "service plexmediaserver start"
(The line with "/bin/sh -c ..." in the systemd file.)

Since i "had" to do a clean install uppon a lost of one of my drives, I will try again later today or tomorrow and edit this post.

I was almost going to virtualbox since this is the most problematic package ever, but I'm afraid of transcoding performance.

Greetings from Rio, Brazil.

I'll be back