Server Version#: 1.13.4.5271-200287a06
Player Version#: (web)
I can’t seem to get any newer versions to work on an Ubuntu Install. The 1.13.5 would “start” but never “register” and show as online. The 1.13.6.5339-115f087d6 does the same thing where the processes show running, but it never “reconnects” as an available server.
However, reverting back to 1.13.4.5271 immediately shows it up.
Server: Ubuntu 18.04.1 LTS
Hi I am running into the same issue as well, I would like to know as soon as possible if there is a fix for this. I’ve looked through multiple other threads and nothing has worked.
There’s nothing you can do. Engineering is working on it.
Stay at 1.13.4 until it’s resolved.
Is there a way to revert back to the previous version? Or a link to the download for the previous version?
Without logs , diagnosis, and justification (critical failure report sent to engineering), older versions are not provided.
It’s always good practice to keep a couple versions of the installation package around in case of situations like this.
If you would like to continue with diagnosis, I’ll be more than happy to work with you.
To do this, I first need understand what you mean by ‘never register’
Then, I will need you to do the following:
/var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs
I can then review and look for glaring issues
Actually it’s the same on Mac. Strangely enough it was working for a couple of days and not nothing. Doesn’t want to connect, no access not even on 127.0.0.1. Application closes normally so does not appear to have crashed.
Supported log archives are .tar.gz and .zip
The .bz2.zip is empty when it gets here.
Whatever is at Mega.nz looks like a package binary (106 MB). Not downloaded.
I’ve tried all the different ways, tar, gzip, bzip bzip2, zip. every one empty.
Would you mind breaking out into a tar.gz or zip ?
Aug 27, 2018 17:45:13.703 [0x7fa14439c700] INFO - Linux version: 4.15.0-32-generic (#35-Ubuntu SMP Fri Aug 10 17:58:07 UTC 2018), language: en-US
Aug 27, 2018 17:45:13.703 [0x7fa14439c700] INFO - Processor AMD Ryzen 7 PRO 1700X Eight-Core Processor
Aug 27, 2018 17:45:13.703 [0x7fa14439c700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Aug 27, 2018 17:45:13.774 [0x7fa150906d40] INFO - OCSP: Successfully retrieved response from cache.
Aug 27, 2018 17:45:15.406 [0x7fa136ffe700] INFO - Refreshing paths watched by LibraryUpdateManager
Aug 27, 2018 17:45:15.772 [0x7fa13e3ff700] WARN - Crash: Crash reporting disabled
Aug 27, 2018 17:45:15.945 [0x7fa1333fe700] INFO - Sync: downloaded 0 sync list(s) with 0 sync items(s): 0 new, 0 updated, 0 deleted
Aug 27, 2018 17:50:23.530 [0x7fa150906d40] WARN - Timed out waiting for server to finish.
Turn on DEBUG logging and try again.
Since you can’t get to your server settings, you’ll need to enable the debug setting by going into the preferences.xml file and manually adding/editing that setting.
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
The setting you are looking for is logDebug. Set it to 1. Restart PMS and obtain a new set of logs.
1.3.6.5339 w/Debug enabled.
plexlogs-1.13.6.5339.20180831.tar.gz (13.2 KB)
I noticed, while having the Web UI loaded during upgrade from 1.13.4.5271 it will show “offline/unavailable” for the server. After a few seconds, it would appear to “return” or come back online and then the server drops off the available server list, never to return.
Upon reverting to 1.13.4.5271, within 15 seconds or so, the server re-appears and can be used as normal.
The same conditions apply after removing all the Plugins from the server, to eliminate another vector for failure.
Your log indicates PMS is running properly. Did you shut down PMS before gathering the log? I see in your log that it received a command to shut down. Just want to confirm that you did this and not done by something else.
The only thing I see is that you censored your local IP address. Did you do this becasue your computer is connected directly to your ISP? Not to a router? There have been reported issues when using this setup.
Found your comment when looking for a solution and wonder if you could help me also. I had a computer crash and had to move somethings around and ended up building a new computer for my Plex Server. I am running Fedora 28, server edition so the unit is headless. The computer is running a cpu of AMD Ryzen 7 1800x with 8gb ram. If you need more info on anything let me know please and I will provide it.
I started with plexmediaserver-1.13.5.5332-21ab172de.x86_64 and had problems of anyone outside my network being able to watch anything. Apps would open but nothing would play. One person using app on Android received a message of transcoding error. I could not get my Anroid phone to work using the same network either. I installed plexmediaserver-1.13.6.5339-115f087d6.x86_64 and things have only gotten worse. I can play everything on a Raspberry Pi, Plex Media Player, to my tv but am unable to view anything on my computer. All are connected via ethernet. The app on my phone on the home tab says everything is offline and will not play anything. When I click on the movie tab or tv shows tab they both load and work.
I have followed your instructions and attached data.zip of the logs.
Thanks in advance for any help you can provide.
johndata.zip (3.0 MB)
Per instructions, prior to packing up logs was to stop PMS. I restarted it and it’s been “running” for 2+ hours now, but it does not show up as an available server within the WebUI. Restoring the previous version (1.13.4.5271) brought it back “online” within 15 seconds.
The logs are cleaned for this package as I noticed debug dumping username and IP and there was no way to directly send the logs outside of this public forum.
The PMS is running on a dedicated server with public IP with an explicit rule to allow inbound port 32400.
I have zero issues with < 1.13.4.5271. The two versions after this has always had this problem.
In 1.13.5.5291 there was a change relating to servers with a wan IP address
Is it possible when you had the issues that Remote Access was not enabled in server settings?
Also please be aware that any network interface that has a name starting with v gets ignored
I can confirm that Drobo5N2 and Drobo5N also are showing similar issues when installed with 1.13.6.5339-115f087d6 in terms of being “available”.
Previously I had 1.13.4.5271 installed and earlier versions did not have these issues.
However, I believe that the root cause is that the process running on all Linux OS based architectures (x86, x64, ARM) is actually stopping on its own in less than 1 minute.
Why do I come to this hypothesis?
Using the Windows-based Drobo Dashboard app, after installing the latest app and starting PMS 1.13.6.5339-115f087d6,the Drobo Dashboard would show that the app was not actually running after about 35 seconds, but was definitely running for the first 30 seconds. (Time confirmed by refreshing the PMS app status window within the Drobo Dashboard).
This also corresponds to the fact that the Drobo5N2 and Drobo5N would show up as available on my local network (didn’t check internet) for about 30 seconds after I pressed start on the Plex app start button in Drobo Dashboard, but then would stop showing up as being available shortly there after.
After the PMS app stops, neither the Drobo5N nor Drobo5N2 show up as being available on my local network (Ethernet) or over the internet.
My two x64 Windows 10 64-bit based PCs running the latest version PMS 1.13.6.5339 do not have these issues thankfully. Once PMS starts, it keeps running and show up as being available both locally as well as over the internet.
For any other Drobo users that might be curious, I am running 3.2.0 [99430] of Drobo Dashboard on my Windows 10 PCs.
My Drobo5N is running “firmware” version: 3.5.16-8.109.96116.
My Drobo5N2 is running “firmware” version: 4.0.5-13.28.96115.
Not sure what Linux kernel those firmware numbers correspond to that are both running on these ARM-based NAS machines.
After performing an “update” using the Drobo Dashboard to the Drobo5N, it reverts to Version 1.13.2.5154 and of course stops complaining that the app needs to be updated (a totally different issue that Drobo needs to work out in the Drobo Dashboard) but the PMS app has been running on the Drobo5N for hours now.
I hope this insight helps.
Logs ?
Please enable debug logging - or check if already enabled
Assuming you have no access to server settings through the web, check the Preferences.xml file to see if there is a logDebug entry, ensure it is set to 1 - if there is no entry then it is default and that is the same as setting it to 1
https://support.plex.tv/articles/201105343-advanced-hidden-server-settings/
Restart the server and after the crash, locate the Logs directory and copy it out and zip and attach
This support article gives the path for most platforms
https://support.plex.tv/articles/202915258-where-is-the-plex-media-server-data-directory-located/
So in trying to get this to work, I confirmed my server was previously set for Remote Access, showing the public ip address and the message “Fully accessible outside your network”. I then backed up the Preferences.xml
I upgraded to the 1.3.6.5339 and watched it disappear from the WebUI.
I then compared the Preferences.xml. For some reason, the upgrade changed “PublishServerOnPlexOnlineKey” from 1 to 0.
I changed this back to 1 and restarted the services. Guess what occurred… The server is currently showing in the WebUI.
Logs for the above sequence ?
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
