"plexmediaserver.service.d" issue in Centos 8

Plex Media Server Metadata & Adding Files
1

I have Plex installed on Centos 8. I used these instructions:

https://support.plex.tv/articles/200288586-installation/

After uploading videos, I am now trying to move the PMS library per these instructions:

My problem is that when I try to create the “override.conf” file it fails:

[root@localhost test]# systemctl edit plexmediaserver
Failed to create directories for “/etc/systemd/system/plexmediaserver.service.d/override.conf”: Not a directory

I have tried using the “systemctl edit plexmediaserver” and “nano /etc/systemd/system/plexmediaserver.service.d/override.conf” but get the same error.

I have tried reinstalling the OS from scratch several times just to make sure I didn’t mess anything up, but I get the same message each time. Not sure what to do, or what is going on. Any help would be greatly appreciated.

2

You need to be root to create it.

I’m just now getting Centos 8 installed in VM (I had a huge PEBKAC).
I’ll evaluate Centos 8 ASAP (maybe tonight)

3

ChuckPa, I slept on it and figured out how what I was doing wrong. I was loading DKMS and ZFS prior to adding Plex. I tried installing Plex before DKMS and ZFS and I was able to edit the override.conf file.

After I finish installing DKMS, ZFS, and ZFS Shares, etc I am able to get Plex up and running with video files added. Everything works, except when I try to finish the process of moving over the PMS. After trying to move it over, I can’t connect to the Plex server via my web browser anymore. I have tried both UMask and Umask.

If I can figure this out, I will gladly post the working version for anyone else. In the end I am trying to:

Install Centos 8
Run ZFS
Run Plex
Run transcodes off of seperate SSD
Run PMS off of another seperate SSD

At this point, the only thing missing is to run the PMS from a seperate SSD, otherwise everything else works. I am attaching the instructions I have right now for reference.Centos 8 ZFS Plex Test Server.txt (5.0 KB)

4

DKMS (Dynamic Kernel) shouldn’t be an issue unto itself.
I presume those modules are dynamically required for ZFS to run.

I do have a thought on the mount point:

  1. mkdir
  2. chown plex:plex of the mount point itself first
  3. mount the file system
  4. chown plex:plex again of the mounted FS’s root.

A similar thing happens with network shares

If you need more control over when PMS starts, in your customization override.conf,
you can add After= then name the ZFS or DKMS startup service(s).

Making sense?

5

I think so. I’ll play around with it and see. Thanks!

6

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.