Project

General

Profile

Bug #4414

Plex Storage Mount Length

Added by Rob - over 6 years ago. Updated about 3 years ago.

Status:
Resolved
Priority:
No priority
Assignee:
Joshua Ruehlig
Category:
Middleware
Target version:
Severity:
New
Reason for Closing:
Reason for Blocked:
Needs QA:
Yes
Needs Doc:
Yes
Needs Merging:
Yes
Needs Automation:
No
Support Suite Ticket:
n/a
Hardware Configuration:
ChangeLog Required:
No

Description

Something seemed to break when updating Plex so I decided to remove it and reinstall it cleanly as I store my configuration folder outside of the plugin jail.

Upon attempting to re-add the configuration folder storage I now get the error: The full path cannot exceed 88 characters

I believe this has been caused because the plugin is now installed as plexmediaserver_1 where it was previously plex_1 which adds 11 additional characters

the full path would now be:
/mnt/ABCDEF/Jails/plexmediaserver_1/usr/pbi/plexmediaserver-amd64/plexdata/Plex Media Server - which is 92 characters

where before it was
/mnt/ABCDEF/Jails/plex_1/usr/pbi/plexmediaserver-amd64/plexdata/Plex Media Server - which was 81 characters

Is there any way the plugin can go back to plex_1 at all?

History

#1 Updated by Jordan Hubbard over 6 years ago

  • Assignee set to Sean Fagan
  • Target version set to 49

#2 Updated by Sean Fagan over 6 years ago

  • Status changed from Unscreened to Screened
  • Priority changed from Nice to have to No priority

Hm. Unknown. We could do so, but there wouldn't be a version bump in the name.

#3 Updated by Rob - over 6 years ago

Sean Fagan wrote:

Hm. Unknown. We could do so, but there wouldn't be a version bump in the name.

Whilst that is a fair point the only thing that has changed here is the jail name. None of the files in my system have moved because that would mean me disturbing my pretty directory structure :)

Also there is no way to safely rename the plugin jails to correct the issue ( see here: https://bugs.freenas.org/issues/2520 ) the only way to solve this is to get you guys to reverse the change :)

I've also started to wonder if this might have been the reason that the update to plex failed in the first place, i.e. the new update expected plexmediaserver_1 but because I had the older plugin the actual name was plex_1?

#4 Updated by Sean Fagan over 6 years ago

  • Assignee changed from Sean Fagan to John Hixson

John, I'm not entirely sure yet how it gets the name for the plugin. Help?

#5 Updated by Rob - over 6 years ago

Sean Fagan wrote:

John, I'm not entirely sure yet how it gets the name for the plugin. Help?

Not that I'd know but my best guess would be here:
https://bugs.freenas.org/projects/freenas/repository/freenas-plugins/revisions/master/entry/plugins/plexmediaserver/pbi.conf

Though I'm guessing there is a behind the scenes version of the plugins because that hasn't been updated in a while and most of the available plugins are not listed there.

#6 Updated by Erik Verheul over 5 years ago

Same problem here. I fixed it by creating a symlink like this ln -s '/usr/pbi/plexmediaserver-amd64/plexdata/Plex Media Server/Media' Media in the directory media in the plexmediaserver jail. When adding storage point to this media directory.

good luck,
Erik

#7 Updated by Jordan Hubbard over 5 years ago

  • Assignee changed from John Hixson to Sean Fagan

#8 Updated by Jordan Hubbard over 5 years ago

  • Assignee changed from Sean Fagan to Joshua Ruehlig

#9 Updated by Joshua Ruehlig over 5 years ago

  • Status changed from Screened to Resolved

I moved the configuration storage location to /var/db/plexdata so I believe this should be solved.

#10 Avatar?id=14398&size=24x24 Updated by Kris Moore about 3 years ago

  • Target version changed from 49 to N/A

Also available in: Atom PDF