Gents,
i have a bunch of log files to send you but everytime i try it says its to large where can i store or send them to get them to you? . i changed the logs to 3000 so it captures most of whats going on. another new issue last two days since loading new version is that plex looks fine with everything loaded one minute and then while later it goes blank and like its fresh and brand new with nothing loaded.
Are you referring to LogNumFiles ?
That would be very unwise as every time we switch log files we would be going through 3000 file rename actions and that may cause issues as it may take a long time to complete - 100 log files has been seen to be ok
You can upload zip to Dropbox or google drive etc and share link. But what is absolutely important is saying what the problem was and what time it was
https://drive.google.com/drive/folders/1sJFfCdOlbachhe9vLu8w7L0OVsH110A9?usp=sharing
this is where im loading plex logs unless you want to send me your email addresses @sa2000@ChuckPa
yes im referring to the log number files due to the systems writing out file every minute so trying to catch the logs and crashes as it happens prior is a night mare. we’ve also gotten recent crashes last few days of it stops recording all together and as of this morning guide refresh has stalled again. im trying to grab the files as we speak and will up load them soon as i can. let me know and thanks. it stopped again sometime yesterday havent been able to get into the recording schedule to see exactly when. keeps giving go to forums page.
For LogNumFiles it is ok to run with 50, 80 and we do have few users with 100. I do not recommend any value above these levels
Each issue needs to be addressed separately.
I have looked at the logs you have uploaded to your Google Drive and what is there are some logs captured on 1st, 2nd and 3rd October for a linux PMS named ubuntu1 which was used before in July 2018 and you brought back to life on 1st October. It is an old version of PMS (1.13.0.5023-31d3c0c65)
i presume these are not the logs you wish us to look at
@sa2000@ChuckPa folks here are all the logs ive kept over time and few db as well. i have recently pulled a new one today not sure if it has prior info or not. unfortunately its really hard to grab the logs when exactly things happens. hope this sheds some light over whats been happening the last few days of it running sluggish and slow as well as guide sticking and stopping all dvrs all together. let me know thanks. ill try and pull them daily or as it happens. also hole time scanning dvr recording its timing out and page wait and failing causing page to reset and start over. on 10/14/18 thanks
10/8 7 unrecorded shows between 1-2 am more lost through out the day
stopped on 10/9 around 12-1 am returned 5-6 pm
stopped on 10/10 around 5-6 am returned 1-2 pm
Isn’t this pure overload ? How many live tv / recording sessions ? how many transcodes ?
Oct 08, 2018 23:35:11.585 [0x7f7efcbf5700] DEBUG - DVR:Grabber: Going to record for 2149 seconds, final URL is http://192.168.0.5:5004/auto/v481
Oct 08, 2018 23:35:11.721 [0x7f7efe3f8700] DEBUG - DVR:Grabber: Going to record for 1789 seconds, final URL is http://192.168.0.8:5004/auto/v13
Oct 08, 2018 23:38:00.434 [0x7f7e0cfff700] DEBUG - DVR:Grabber: Going to record for 1740 seconds, final URL is http://192.168.0.8:5004/auto/v4
Oct 09, 2018 00:00:00.176 [0x7f7f4dbfe700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.7:5004/auto/v682
Oct 09, 2018 00:00:00.215 [0x7f7f09bff700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.5:5004/auto/v160
Oct 09, 2018 00:00:00.421 [0x7f7efebf9700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.7:5004/auto/v376
Oct 09, 2018 00:00:00.542 [0x7f7efcbf5700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.6:5004/auto/v88
Oct 09, 2018 00:00:00.813 [0x7f7eac3ea700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.8:5004/auto/v384
Oct 09, 2018 00:00:03.028 [0x7f7ec83ff700] DEBUG - DVR:Grabber: Going to record for 3598 seconds, final URL is http://192.168.0.6:5004/auto/v19
Oct 09, 2018 00:00:03.629 [0x7f7efdbf7700] DEBUG - DVR:Grabber: Going to record for 3597 seconds, final URL is http://192.168.0.5:5004/auto/v502
Oct 09, 2018 00:11:08.433 [0x7f7f4dbfe700] DEBUG - DVR:Grabber: Going to record for 2152 seconds, final URL is http://192.168.0.8:5004/auto/v481
Oct 09, 2018 00:30:00.195 [0x7f7f09bff700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.8:5004/auto/v88
Oct 09, 2018 00:30:00.437 [0x7f7efdbf7700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.5:5004/auto/v376
Oct 09, 2018 00:30:00.558 [0x7f7efebf9700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.8:5004/auto/v384
Oct 09, 2018 00:30:00.942 [0x7f7ec83ff700] DEBUG - DVR:Grabber: Going to record for 1800 seconds, final URL is http://192.168.0.7:5004/auto/v682
Transcode Sessions (you can derive how many in parallel)
Analysis of (xx live) count
You are running all the time with a high level of load
@sa2000 thats what i was afraid of was possibly overwhelming it or over loading it. not sure how many recordings i know i have four hd home run primes with 3 tuners each so 12 channels available 24/7 was looking to add a 5th for additional 3 more but havent. as far as the transcoding not sure where there coming from. unless its during play back but thats usually only 1-3 using it at a time. like i said on the logs unfortunately with it running heavy the way it is it logs almost every minute. so when it goes down was really hard to catch it cause usually by the time i got home or was made aware it would always overwrite them. but with the system we got thought could handle it guess maybe not. so what do we do or what can we do and where we go from here? what more can i provide for you?
The server was already at a high load level before midnight October 9th. You can see that from (xx live) count - where the chart i plotted starts with it already at about 60. Idle state is 10-20.
It is very very time consuming to analyze the data.
What you could do is restart the server and look at logs and pick the (xx live) counts from the Request: lines in the logs and record all the IP addresses the requests come from and see how the xx live count builds up. I presume products such as Tautulli would help you establish what requests are coming
@ChuckPa@sa2000
Gents i have uploaded more logs as well as screen shots. multiple times passed couple days tuners, locking up and not clearing recordings as well as still lag on overall system even though plenty of system resources to use, on older version and newer version. logs will be on the google drive under todays date soon as there done transferring. let me know and thanks.
tried that line of code is there spaces in between the brackets? one time didnt do anything, the other it returned lines with ~~~~ down the screen. do i need to replace the astricks with the log file name? help thanks
@sa2000 ok i will try that, i’ve uploaded most the logs to the google drive as well. it has stalled the tuners 5 times over the last 3 days on the new version.
