I reviewed your logs again, ignoring the Web version. The only other thing I can see is that you appear to be using your own web domain. Can you remove these entries and see if that makes a difference?
I tried that with no change, this also affects my local clients to, which should be direct connecting to my local IP correct?
My nginx logs do show a lot of when this seems to be really bad. Checking It regularly sometimes its better than others. Last night for example, plex kept throwing an error that it couldn’t get the playlist for the items. If it helps, I have a Splunk server set up, I can provide someone(s) access that has all of my logs in it? I’m really starting to think the web app is a symptom and not the root cause
upstream timed out (110: Connection timed out) while reading response header from upstream
I see a lot of things such as :
Sep 15, 2019 23:59:00.646 [0x7f2783fff700] ERROR - Failed to begin transaction (../Statistics/StatisticsManager.cpp:248) (tries=1): Cannot begin transaction. database is locked
Alternatively here is a CSV of all errors for my plex index
1568651688_662.csv.zip (178.8 KB)
Could this be a slow HDD? I have a Seagate Firecuda (7200 RPM with SSD), so unless its something linux isn’t handling well with the SSD position. I never had this issue on macOS but I moved everything over to Linux with a new hard drive that I thought was supposed to be better but I’m starting to think otherwise.
I don’t see any signs.
Have you tried turning Nginx off?
Yeah- the same thing happens regardless if I route it through Nginx or access it directly through the port and IP, this happens remotely and locally.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
