Server Version#: FreeBSD jail 13.3
Player Version#: 1.40.3
I properly run plex on my FreeBSD jail using pkg Latest which is still at 1.40.2
I wanted to upgrade to 1.40.3 using tar.bz2 official archive
I extract the tarball under /usr/local/share/plexmediaserver directory
I properly set the permissions as it seems they are not set in the tar file !
I also created the missing ln -s "Plex Media Server" Plex_Media_Server as it is also missing in tarball
However, the server never starts. I couldn’t get any error messages even by enabling more verbose logging in rc.d startup script. It just doesn’t start
Anyone can help installing it from the tarball archieve ? Is it an issue with the static libraries ?
The update through the FreeBSD ports tree is in the works as we speak… Hopefully it will be available tomorrow, Friday at the latest… If you haven’t borked your installation to badly, hopefully you will be able update the proper way and everything will be installed in all the right places and with all the right permissions…
Thank you a lot
Yes, I could fix my installation by accessing the local server through an ssh tunnel with port forwarding
However, this doesn’t answer my question about how to properly update from the provided tarball ! Or is it only provided for developers to port to a proper pkg?
I do not run Plex in a jail, so you may need to make whatever edits needed to fit your setup.
cd into /usr/ports/multimedia/plexmediaserver or plexmediaserver-plexpass depending on the release you are following.
rm distinfo
ee Makefile
Edit Makefile, making changes to the lines that contain DISTVERSION and DISTVERSIONSUFFIX with the new values. Save and exit ee.
make makesum
This will try and download the requested tar.bz from Plex servers and ceate a new distinfo file. If no file downloads, reedit the Makefile with the correct values.
sha1 /usr/ports/distfiles/PlexMediaServer…tar.bz, inserting the full file name downloaded. Check that this hash matches the hash on the Plex download webpage. If it matches your file has downloaded correctly. If not, rm the file and repeat 4.
make install clean
If you want you could back up the port directory before you start but it’s really not that involved.
Ok, thank you a lot for taking the time to explain it better. I thought it was just overwriting install path
I tried it for testing purpose and it works properly
Best regards
No problem… Just so you know both versions of Plex were updated to the latest release in the ports tree yesterday afternoon… Of course, Plex released a new -plexpass version while the ports were being updated in the ports tree, so I’ll have to submit a new bug report for that now…
One last suggestion I have is to wait a day or two after the release announcement by Plex and keep an eye on the forums to make sure there is not any problems with the release before updating yourself… I try to do this myself but sometimes people force my hand and submit a bug report to get it updated as soon as it is announced…
As the FreeBSD port maintainer for both plexmediaserver and -plexpass, there are a few more steps I have to do to submit the bug report to update the port, then have to wait until a port committer picks up the bug report and applies my submitted patch to the port tree… Sometimes they are pretty quick at getting it done but a lot of times Plex releases a new update, especially the -plexpass version, before the previous one is committed, in which case I close the current bug report and have to submit a new one and the process starts all over again… Yes, it is a slow process, but it helps keep problems out of the FreeBSD ports tree…
I’d never file a bug support or request an update. I well know all the involvement made by developers. Your explanations gives even more about the “administrave” constraints added on developers.
I rarely update. I just wanted to understand how to install the provided binaries by my self. Your script in MakeFile makes it clear. Thank you for pointing me to the directions.
If I have time, I would provide an optional way to keep the custom/existing rc.d script and maybe copy the new default one to a backup directory. I find it annoying to have my rc.d custom setup overwritten on every update
What do you think about it?
Believe me, I’m no developer!!! I am not an employee of Plex or FreeBSD… The last serious programming I did was using Apple Basic on an Apple IIe back in the late 80’s… I’m just an 'ol retired fart that figured out what needed to be changed to update the Plex port in FreeBSD for myself… I was impatient waiting for the updated port in the ports tree…
When the last port maintainer gave it up, I decided to take it over… It was a learning curve for me, spent some time on the FreeBSD Forums asking questions and reading the FreeBSD Porter’s Handbook which is so far over my head, I still don’t understand most of it… The only other steps I have to take is run my changes through a QA testing program and then provide a diff file for a patch that contains the changes within the directory for the bug report on Bugzilla…
I did not write the Makefile, it was already there when I took over… If the powers that be over at FreeBSD ever decided to make major changes in the way ports work, I would be lost… I cannot follow half of what the Makefile does now… As far as making any major changes to it, that would be far beyond my current capabilities… While I apricate your offer, I think it would be best to leave things be and not implement coding into the ports tree to account for custom installs…
One last thing I would point out is that while TrueNAS maybe based on FreeBSD, TrueNAS is not FreeBSD and has customizations by the TrueNAS team not implemented in FreeBSD and sometimes, some things just work differently between them…
Great job for what you say, really, thank you.
The modification would be only one or two trivial lines in the MakeFile to copy the current rc.d custom script before it is overwritten and echo an info message to the user, so nothing envolving the ports tree
I will look at it whenever I have some time
