-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
After latest upgrade PLEX fails to start. #67
Comments
Getting the same thing.... Could not find a FreeBSD download link on page https://plex.tv/api/downloads/5.json?channel=plexpass&X-Plex-Token=Ms7w5J6Nyu8Rp9ws4BxM |
I have no problems downloading the 1.32.6.7371-b6a09ad81-FreeBSD-amd64.tar.bz2 version of Plex, but the plexmediaserver service is failing to start. I see:
in /var/log/messages and no other errors. |
I tried a manual update and ended up with the same problem you have harvimt |
I had the same, rolled back to another snapshot of my plex jail and it worked again. After running the pms_updater.sh it once again failed to start. But then I noticed in my backup dir that there were 2 symlinks:
and
So when I added those again, it managed to start again. Hope this helps. |
Would the correct commands be:
|
That is correct, depending on where you installed plex you should change your path ofc. |
It's installed in a separate jail as a plugin. TrueNAS-13.0-U5.3 and jail is 13.0-RELEASE-p13. I'm getting this for some reason:
|
Ah I'm sorry, it should be the other way around: run these in /user/local/share/plexmediaserver I also have it installed in a truenas jail as a plugin btw |
I assume you did restart the service or jail? What does your /var/logs/messages say? |
I actually did. Shouldn't I do it? I mean the PMS_Updater script does restart the service anyway, doesen't it?
|
Yea you should, so that's not the issue. That looks exactly like what I had. could you maybe verify the permissions/ownership on the links? |
Both are root|wheel. |
I'm afraid I don't know what the issue is then. This is what solved it for me. Do you have any recent snapshots of your jail? Maybe rollback and start again from a working version |
Well it looks like running the "Update" from TrueNAS plugins menu restores the functionality and downgrades the version to a working one. Thank you for your time anyway tho. |
np! Glad you found a workaround for now at least :) and ye let's hope so |
Hello all, For me it worked to manually update the plex server with an earlier version: In my case: Path_to_the_local_file = 1.32.5.7349.8f4248874-FreeBSD-amd64.tar.bz2 |
I'm leaving a comment here to say I'm having the same problem as of this week too. |
The script itself seems fine, the actual package from plex seems to be what's broken... the script can install the package, it's just that then it does not run. There isn't an official TrueNAS plugin update for 1.32.6.7371-b6a09ad81 yet, they may add patches on top of what plex added. |
So do we just wait for the next update and see if installing that package returns our servers to working condition? |
As @harvimt said I assume plex broke something because it errors with a SIGSEGV. The script itsself is fine, it's just scraping the API, download and installs it. To somewhat fix your install you can download PlexMediaServer-1.32.5.7349.8f4248874-FreeBSD-amd64.tar.bz2 which is a bit older and use the -l parameter to install it. |
I did end up successfully downgrading. I followed some tutorial for a jail install when I originally used this script. Somehow I missed that it is designed to work for the plugin. I'm not sure what I thought was different exactly, or what benefit I thought I was getting, but it does in fact work for both. I did find it strange that a simple rollback to a previous snapshot did not yield a working downgrade though. |
Looks like this is actually a Plex problem and not a PMS problem. Downgrade is necessary. You can do this from PMS:
|
For me, I have found that if you hit "Update" in the TrueNAS GUI under Jails for plex that it will roll it back to whatever is in their database. I don't recall the version at the moment. |
Has this been fixed? I still get the issue when I try to update using the script, and have to roll back to a snapshot to get Plex working again. |
It's not that script issue, it's a Plex issue, nothing we can 'fix' |
I see. Is there a workaround? |
I think it is enough to just update/upgrade from the Plugin menu if you have installed it via plug-in menu. |
@ZeDima unfortunately I changed over to a manual install in a jail... |
You can use the method I posted above to manually downgrade from inside the jail instead of rolling the whole jail back. But I guess for now we all just disable whatever automation we use to call PMS and wait for Plex devs to fix the issue. |
Does anyone know if the Plex devs actually know about this? Cause I didn't see anything on the support site, but I could've missed it |
Lol so they haven’t even acknowledged it. Priceless.
…On Tue, Aug 29, 2023 at 2:48 PM Peter ***@***.***> wrote:
Well there's
https://forums.plex.tv/t/plexmediaserver-1-32-6-7371-broken-on-freebsd/849348/38
—
Reply to this email directly, view it on GitHub
<#67 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJ63V6KZY2LU7VS7O5YCVLXXY2QPANCNFSM6AAAAAA3G2Z3ZY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Plex forums are a mess, they don't really moderate or acknowledge things unless it somehow gets the attention of a dev, who might pop in and ask for logs and then never be heard from again |
Lovely. Maybe I ought to rethink my Plex Pass subscription, especially
considering I don’t really use any of the features it provides….
…On Tue, Aug 29, 2023 at 3:50 PM Shlomo Friedman ***@***.***> wrote:
Plex forums are a mess, they don't really moderate or acknowledge things
unless it somehow gets the attention of a dev, who might pop in and ask for
logs and then never be heard from again
—
Reply to this email directly, view it on GitHub
<#67 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AGJ63VZU5KGKSSQW3MUS5DTXXZBWTANCNFSM6AAAAAA3G2Z3ZY>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
Seems to be fixed now |
After installing latest update PLEX fails to start. Manually triggering the update the following issue is displayed.
The text was updated successfully, but these errors were encountered: