I’m running FreeNAS, and I have installed Plex Media Server manually into a Jail (not the plugin!).
But now plex keeps asking me to manually update it, and I have no idea how.
Google isnt any help either.
How do I manually update plexmediaserver on a FreeNAS jail (11.2) ?
Its apparently not as simple as;
service plexmediaserver stop
pkg update
pkg upgrade
service plexmediaserver start
what guide did you use to install? what does pkg info say? Does it show plex installed?
Ive cobbled together my own guide since freeBSD documentation is a big heap of nothing. :’)
pkg install plexmediaserver
sysrc plexmediaserver_enable=YES
sysrc plexmediaserver_user=newmedia
service plexmediaserver start
service plexmediaserver stop
find / -user plex
chown -R newmedia:newmedia <FOLDERNAME>
service plexmediaserver start
And with that it was up and running. It started telling me there was an update the next day.
Anyone? Id like to update it at some point…
what does pkg info plexmediaserver say?
plexmediaserver-1.13.2.5154
Name : plexmediaserver
Version : 1.13.2.5154
Installed on : Fri Aug 3 18:59:26 2018 CEST
Origin : multimedia/plexmediaserver
Architecture : FreeBSD:11:amd64
Prefix : /usr/local
Categories : multimedia
Licenses :
Maintainer : feld@FreeBSD.org
WWW : https://plex.tv
Comment : Plex Media Server component
Options :
RELAY : on
Shared Libs required:
libstdc++.so.6
libreadline.so.8
Annotations :
FreeBSD_version: 1101001
cpe : cpe:2.3:a:plex:plex_media_server:1.13.2:::::freebsd11:x64
no_provide_shlib: yes
repo_type : binary
repository : FreeBSD
Flat size : 181MiB
Description :
Plex Media Server is used to host the content and plugins that are then
streamed to Plex Media Center and Plex mobile app clients, either on the
same machine, the same local area network, or over the Internet. Content
may be transcoded by the server before it's streamed in order to reduce
bandwidth requirements, or for compatibility with the device being
streamed to.
WWW: https://plex.tv
are you executing the pkg update / upgrade inside the jail?
Yes? Am I not supposed to?
Can I see the contents of /etc/pkg/FreeBSD.conf and /usr/local/etc/pkg/FreeBSD.conf?
i’ll need to see it both inside of the jail and for the system. yes you should be doing this inside the jail.
Sorry it too me a while, I went on vacation.
/etc/pkg/FreeBSD.conf
# $FreeBSD: releng/11.2/etc/pkg/FreeBSD.conf 333474 2018-05-10 23:58:33Z gjb $
#
# To disable this repository, instead of modifying or removing this file,
# create a /usr/local/etc/pkg/repos/FreeBSD.conf file:
#
# mkdir -p /usr/local/etc/pkg/repos
# echo "FreeBSD: { enabled: no }" > /usr/local/etc/pkg/repos/FreeBSD.conf
#
FreeBSD: {
url: "pkg+http://pkg.FreeBSD.org/${ABI}/quarterly",
mirror_type: "srv",
signature_type: "fingerprints",
fingerprints: "/usr/share/keys/pkg",
enabled: yes
}
There is no /usr/local/etc/pkg/FreeBSD.conf
Path ends at /usr/local/etc/ with ls:
bash_completion.d pkg.conf transmission
fonts pkg.conf.sample wgetrc
mono rc.d wgetrc.sample
periodic ssl
create a local pkg file using your favorite text editor at this location:
/usr/local/etc/pkg/repos/FreeBSD.conf
in the file paste this:FreeBSD: { url: "pkg+http://pkg.FreeBSD.org/${ABI}/latest", mirror_type: "srv", signature_type: "fingerprints", fingerprints: "/usr/share/keys/pkg", enabled: yes }
notice i changed the url string to latest instead of quarterly. FreeBSD has started to default to quarterly for pkg updates instead of latest.
It was hiccuping a little with the init, but as usual, a jail reboot started 'er up again.
And sure enough, now its updated itself to the latest version.
Thanks!
Here is script for 11.2-RC1
Check Readme for install instructions.
Thanks for instructions, @lucekgr, but I get stuck in last step. It promts:
./PMS_Updater.sh: No match.
Am I missing something?
I wouldn’t use that script. It’s a hack maintained by another person, meant more for the people using the Plex plugin (vs. a regular jail), breaks often and then you’re dependent on the script maintainer to update/fix it.
I’m not clear on why you’re having so many issues, and the advice here seems overly complicated. Updating PMS in FreeBSD is as simple as a single command, exactly what depends on if you’re using packages (prebuilt binaries) or ports (you compile from source). I’d suggest starting here:
https://www.freebsd.org/doc/handbook/ports-using.html
Following the official ways of updating will be far preferable to unofficial hacks.
Personally, I use ports as that’s the traditional FreeBSD way, and it’s not like PMS takes long to compile. I combine upgrading the ports tree then rebuilding PMS all in one script, but you can chain it all together in a single line at the command line.
If the official update procedure worked, I wouldn’t be here complaining about it…
The library that FreeNAS employs is apparently some kind of special snowflake.
I’m still on 1.13.8.5395 because last time I updated it, it fudged everything up.
I basically had to do a clean install to ‘update’.
I am not clear from the information you’ve provided so far what is unique about how you’ve done your setup that is giving you so much issue. I can tell you however that this isn’t an inherent issue with FreeNAS, jails, etc that makes it a “special snowflake”. I’ve rebuilt my FreeNAS jail from scratch 3-4 times now over the past 4y and each time it was smooth and straightforward. The simplified summary: create jail, download and install ports tree, install PMS from ports, rsync over my PMS data from the old jail. In FreeNAS 11.2/iocage there was new stuff w/ vnet but that info is well disseminated at this point. Upgrades are basically as simple as: portsnap fetch update; portmaster -a
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
