It happens sometimes 3 times aday and some times 3 days passes between. what logs do u guys need to check for errors:( its driving me insane.
what options do i check guys 
Its really driving me insane
Please post your log files (Settings - Server - Help - Download Logs) after making certain Verbose logging is not checked. We need to see a duration of time. Verbose logging denies this due to the amount of data in the files.
There u go, it did some wierd stuff when it was syncing stuff yesterday aswell
For info, the server is on a virtual machine running off SSD’s with 2 xeons windows server 2016
Thank you for the logs. Due to the amount of streaming you’re doing, I only see 1 hour retention in your log files.
Should you desire to extend this (adds about 25MB more log space above it’s current 30MB size), you can do so by setting the advanced setting in the registry.
The procedure is here. https://support.plex.tv/hc/en-us/articles/201105343-Advanced-Hidden-Server-Settings
The recommended value to use is 10 instead of the default 5. The value you are interested in is LogNumFiles
After setting this value, restart PMS.
When it faults again for you, this will give you a bit longer to get to the dashboard and obtain those same log files as you just did. It will let us see what happened.
ok, Trap has been set sir, waiting for the big bad bugs 
what is the maximum value for this setting ?
I have used 50 in extreme cases. How much disk space do you wish to utilize? Also, please remember, the average compressed upload of 25 MB log files is 4-5 MB of forum space. The forum has a limit somewhere
Still running without issues for some reason.
Wondering if update 1.7.5 fixed it.
waiting 10 more days to close this
I’ve had similar problems in the past and this was my /tmp filling up to the level where no new files could be created on it.
@sica said:
I’ve had similar problems in the past and this was my /tmp filling up to the level where no new files could be created on it.
I assume u can point me to exactly where that is?!
AAAAAND there we go, crash !
ooops dident attach file
If I add 6 hours to my local time (I presume you are CET time?), I see the error.
Something has blocked access to the database. There is a known deadlock issue (PMS ‘sleeps’ for no reason then resumes). This looks very different. It appears as if suddently the database file itself can no longer be read by PMS. This is not how the deadlocks appear.
In the logs you provide, It has happened twice.
Please check the machine & ‘chkdsk’ it? There is a fundamental access problem.
Jul 13, 2017 11:55:51.126 [8628] DEBUG - Requesting more shows since stacking only returned 2 items.
Jul 13, 2017 11:55:51.189 [5572] ERROR - SQLITE3:BB2C524B, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\1\etilqs_2ePSBQoLeswNYyK) - The system cannot find the path specified.
Jul 13, 2017 11:55:51.189 [5572] ERROR - SQLITE3:BB2C524B, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 13, 2017 11:55:51.189 [5572] ERROR - SQLITE3:BB2C524B, 14, statement aborts at 668: [select distinct media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_locatio
Jul 13, 2017 11:55:51.189 [5572] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 13, 2017 11:55:51.189 [5832] DEBUG - Completed: [80.62.117.7:60496] 500 GET /hubs?count=50 (20 live) TLS GZIP 3443ms 405 bytes (pipelined: 2)
Jul 13, 2017 11:55:51.361 [8628] ERROR - SQLITE3:BB2C524B, 14, os_win.c:41841: (3) winOpen(C:\Users\ADMINI~1\AppData\Local\Temp\1\etilqs_JznenbxkqZg8wdK) - The system cannot find the path specified.
Jul 13, 2017 11:55:51.361 [8628] ERROR - SQLITE3:BB2C524B, 14, cannot open file at line 41850 of [fc49f556e4]
Jul 13, 2017 11:55:51.361 [8628] ERROR - SQLITE3:BB2C524B, 14, statement aborts at 668: [select distinct media_items.id as 'media_items_id', media_items.library_section_id as 'media_items_library_section_id', media_items.section_location_id as 'media_items_section_locatio
Jul 13, 2017 11:55:51.361 [8628] ERROR - Soci Exception handled: sqlite3_statement_backend::loadRS: unable to open database file
Jul 13, 2017 11:55:51.361 [5832] DEBUG - Completed: [80.62.117.7:47062] 500 GET /hubs?count=50 (20 live) TLS GZIP 4266ms 405 bytes (pipelined: 1)
Jul 13, 2017 11:55:51.392 [5812] DEBUG - Auth: We found auth token (xxxxxxxxxxxxxxxxxxxx), enabling token-based authentication.
Jul 13, 2017 11:55:51.392 [5812] DEBUG - Auth: Came in with the master token, authorization succeeded.
Jul 13, 2017 11:55:51.392 [5156] DEBUG - Request: [127.0.0.1:59886 (Loopback)] PUT /video/:/transcode/session/t
This is the suspected RDP issue and use of per session temp directory for terminal services sessions
Relates to this windows registry HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\PerSessionTempDir
Have you launched Plex Media Server in an RDP session?
It appears that %TEMP% cannot be relied on when the above is true
See this forum thread post and rest of forum topic https://forums.plex.tv/discussion/comment/1477456/#Comment_1477456
You can see from the above the log extract that sqlite3 used a temp directory C:\Users\ADMINI~1\AppData\Local\Temp\1\ and not C:\Users\ADMINI~1\AppData\Local\Temp\
Ok guys, it seems i might have done a diskcleanup at some point where it deleted the temp folder “(C:\Users\ADMINI~1\AppData\Local\Temp\1\etilqs_JznenbxkqZg8wdK) - The system cannot find the path specified.”
i repaired the database with the SQL tool and it seems to be running perfectly now
and Yes it had been launched in an RDP session, but it has auto login as the administrator, so i guess the RDP diddent start the session.?
