The server is running.
I can play things via AppleTV and my iPhone.
If I try to log into PLEX on any local PC or the server, it tells me it is not available.
This seems to happen when it is scanning new audio but it happened yesterday after added a few TV episodes.
Is this something you guys are aware of?
1 Like
I have been looking at an issue relating to scanning but I only have one set of logs and I need more examples and if the server is unavailable during scanning or after.
Could I have logs from both the server and the web app ?
For the web app you need to enable verbose logging in advance when the localhost route is working - so connect to the server via localhost and then select settings / web / show advanced / debug and chsnge logging option from disabled to verbose. Save the changes and then later when the issue is encountered via this browser and url, logging should be on.
For server logging - debug is needed and it is on by default is advanced general server settings
When the problem arises, rake screenshot, note down the time, save the web app log (settings / web / show advanced / debug / view log / select all and copy and paste to text file )
Then collect the server logs - see this article for location of server logs. Copy out the Logs directory and zip the copy and attach here together with the web app log, screenshot (please do not crop) and indication of the time
And here is the problem with that. When this is happening, the server is not reachable through a browser so logging on via local host from the server itself doesn’t do anything since it can’t see the server. It says it is unreachable. So I don’t have a good way to pull the logs since I can’t get to admin. I do know my error logs are not disabled but also not set to verbose, just regular.
Let me link you to another post of mine with more info and see if this helps.
If not, I’m perfectly willing to go offline with you and haveyou remote to my server (PLEX is all it does) so you can dig to your heart’s content if it will help you out. It it still unreachable now and the last batch of audio I added to the library was Saturday night.
If you want to work offline, let me know how to get my email to you.
Don’t know if this will help, but I packaged up the entire log folder (minus the install and plug in logs)
logs.zip (3.5 MB)
I wasn’t aware that Chrome was saving logs as well. If it is where are they?
I also installed the Windows PLEX app and it couldn’t connect either so I’m including the log file from it as well.
Plex.log (571.5 KB)
What happens if you go to http://127.0.0.1:32400/web?
Same thing. The fun thing is when it is actively loading in music I can go to my iphone PLEX and watch the new albums load in as they are scanned. I can play them. I can play movies on Apple TV. I just can’t get to the server via browser (I’ve tried Chrome and Edge). Just keeps telling me that the server is unreachable and would I like to try again.
Hey Sir,
It JUST in the last half hour came back to working on web. So if you need a test bed to grab all the logs you want, here is your chance. Let me know what you want me to do as far as debugging (I changed it to verbose) and how you want me to package up the logs (which ones) since I can’t run the log export once it locks out the web. I can guarantee that if I load in another large chunk of audio it will lock out the web access again so if you want to controlled explosion, here is your chance.
I am at your service because this is a real pain and I actually LIKE the new audio scanner results but I can’t get it to live long enough to be practical.
Oops, it went away again. Crap.
sorry I was out for most of the day.
If the server is inaccessible, the Plex Web app should still be able to access its own Plex Web settings to get the Plex Web log through Settings / Web / Show Advanced / Debug and then clicking on View Logs and selecting the text and copying to a text file. See https://support.plex.tv/articles/201611836-plex-web-app-logs/
Of course this would only be of benefit if logging was enabled for Plex Web for the browser and the url (http://127.0.0.1:32400/web) through a similar sequence earlier on and instad of view logs, to actually set it to verbose
As for the server logs, it would be a matter of getting to the Logs directory in the filesystem as you have done and copying out and zipping the copy. Zipping directory in-situ rather than the copy would lose current open log files.
I will have a look at what you managed to capture
ok, it is back now. And yeah, I found the debug area and you are right (duh) that isn’t database specific. It is set to verbose now. Do you want a copy of the files zipped up or should I load some stuff up, kill it again, and pull a set then?
I can see some requests to the server taking a long time to complete.
Could you run some tests with curl to see how long the requests take and also to send me by private message the response that gets returned. These requests are what get used by Plex Web when trying to test the connection to the server and it is possible that they are timing out because of the length of time for the server to respond
First to try out the request, we need to find the security token for the server - you can either pick that up from the registry copying it out of
HKEY_CURRENT_USERSoftwarePlex, Inc.Plex Media Server\PlexOnlineToken
or following the steps here https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
Then we can try the request:
http://127.0.0.1:32400/media/providers?X-Plex-Token=xxxxxxxxxxxxxx
where xxxxxxxxxxxxxx is the token string
Copy the response to a text file and send it to me by private message
Refresh the browser a number of times to repeat the request and then send me the Plex Media Server.log - I can see the length of time to response from the log - when there is no issue
The plex.log you provided was from the Plex Desktop app - is that what you use ? I thought it was Plex Web - which would have different logs as mentioned in my earlier post
Is the Plex Desktop app on the same machine ?
Regarding the logs you provided, at what times was the server inaccessible through 127.0.0.1:32400 ?
It was down from Saturday evening until today around 3:40 central
I don’t know where plex web stores its logs.
run some tests with curl? Is that the providers link you put in below or is it something else.
I’ll work on getting that info to you as soon as possible.
You can do the 127.0.0.1:32400/media/providers?X-Plex-Token=xxxxxxxxxxx test either in a browser or using curl
If using curl in command line, you would need to download curl if not available within your windows install
The syntax would be something like
curl http://127.0.0.1:32400/media/providers?X-Plex-Token=xxxxxxxxxxxxxxx > media_providers.xml
Please run a few of them so i see the elapsed times in the log
If you need to download curl, see https://curl.haxx.se/download.html
You mentioned that http://localhost:32400/web/index.html
So that would be Plex Web and not the Plex Desktop app.
I have already given info on how to get the Plex Web log - enabling web verbose log beforehand when it is working and later on viewing the log when the server in unavailable.
See Http://localhost:32400/web/index.html is unavailable but PLEX works on devices - #2 by sa2000
I would like to repeat the above timing tests after we optimize the database
After completion of the optimize - which may take a few minutes, repeat the timing tests for http://127.0.0.1:32400/media/providers?X-Plex-Token=xxxxxxxxxxxxxx and let me have the log after a few such requests
Thanks for the logs - the optimize did not seem to help. Requests are still taking too long
Jan 13, 2020 20:02:07.346 [6596] DEBUG - Completed: [127.0.0.1:55886] 200 GET /media/providers (9 live) GZIP 15212ms 6804 bytes (pipelined: 1)
Jan 13, 2020 20:02:14.960 [6596] DEBUG - Completed: [127.0.0.1:55903] 200 GET /media/providers (8 live) TLS GZIP 12594ms 6872 bytes (pipelined: 1)
Jan 13, 2020 20:02:20.606 [6596] DEBUG - Completed: [127.0.0.1:55848] 200 GET /media/providers (7 live) GZIP 11058ms 6738 bytes (pipelined: 7)
Jan 13, 2020 20:02:36.887 [3196] DEBUG - Completed: [127.0.0.1:55927] 200 GET /media/providers (10 live) GZIP 13754ms 6804 bytes (pipelined: 1)
Jan 13, 2020 20:02:44.492 [6596] DEBUG - Completed: [127.0.0.1:55943] 200 GET /media/providers (10 live) TLS GZIP 11254ms 6872 bytes (pipelined: 1)
Any issues with the C: Drive performance ? The database is held here
How big is the database ?
It would be here
C:\Users\chene\AppData\Local\Plex Media Server\Plug-in Support\Databases
Filenames:
com.plexapp.plugins.library.db
com.plexapp.plugins.library.db-wal
com.plexapp.plugins.library.db-shm
Could I have the zip of the database to see how big are the various tables
To get the zip, use plex web Help and Support page to download the database
The zip may be too big to send by PM - could you upload to Google Drive / Dropbox etc and send me a link
Thanks
I’ll gather all that up tomorrow and shoot you a PM of a share folder on my Synology box.
com.plexapp.plugins.library.db - 743,162
com.plexapp.plugins.library.db-wal - 756,090
com.plexapp.plugins.library.db-shm - 5,792
I exported the database and put them in a shared folder and sent you the link. That zip file is only 168meg
Thank you. I will be looking into number of items of each type and will probably get a diagnostic build for you. I need to establish why these requests GET /media/providers are taking a long time to complete
I’m not making any changes to the server while you are working on this. Not adding any new media or anything. I don’t want to add any more variables. So go do that voodoo you do that you do so well and let me know what you need from me.
I still think this is localized to 1.18 as everything was peachy in 1.17.
To get here, I deleted all of my audio files (audio books and music mostly) and upgraded to the latest and it came right up. If you don’t remove those it doesn’t come back up. Well it might after a month or two. Then I started slowly adding audio back in. At first you could watch the scan in web. Then it would lock out for a few minutes and that lock out duration gets longer and longer the more audio you put back in. several hours then 12 hours and the last one was 2 days.
