So this was activated on both?
Explanation/imagine this:
sometime in the night, when the file share is idle or even shutdown, Plex server is performing a library scan.
The file share is either not answering fast enough or is temporarily unavailable for some reason. Plex server will start deleting these unavailable items from its library - due to the above setting.
Next time the server performs a library scan, the file share is available again or reacts with regular speed, so these items are added again to the library - and the ‘added at’ time stamp is set to the current date…
1 Like
Great !! Thanks Otto,
Clarity for me… 9 or 10 hrs ago I was chatting with you folks and sending my logs. Chuck responded to the opening of my issue at Thu, Aug 30, 2018 at 12:33 AM and I was monitoring and connected to my server.
I made the change you suggested because I believe you logic… but at this point I am looking for something even in logs or troubleshooting to show where server, file-server, or my connection is causing a connectivity or performance issues last night or to cause the time to change or not be set. Would this show up in verbose logging…? File server is not huge but its only serving these files plex is NOT running on it. (trying to minimize what it does and prolong life of disks)
You won’t be needing ‘verbose’ logs. ‘Debug’ should be enough.
Concentrate on the ‘Scanner’ logs.
Is it possible to “Manage” what plex does in conditions where there is slow responsiveness or if it cannot resolve or connect to Plex.tv… ? Like maybe stop and try again later make no changes or updates to database
Disabling this checkbox is pretty much all of what you can do.
It is very hard for Plex to distinguish whether an ‘unavailable’ file is just a transient issue or if it’s gone for good.
Can you tell me what this means…
Aug 29, 2018 02:26:48.962 [11432] ERROR - Error response for update: 5 (Unhandled exception).
Without context, not really.
Its the only err in the Plex scanner logs 4 . (1,2,3, did not show errors)
And its at 230am… about the time Plex thinks I added the new versions… even though it was earlier…
The non-error lines are adding context to the error line. Without knowing these, I can only assume that there was indeed a failure of some kind.
Do you have a copy of the logs I sent…? this is what I am reviewing now… at your suggestion…
Next Erro I see is in “Plex Media Server analysis 5” log… at about 6 am
Aug 29, 2018 06:09:27.914 [9736] WARN - [FFMPEG] - Could not find codec parameters for stream 4 (Subtitle: hdmv_pgs_subtitle (pgssub)): unspecified size
Consider increasing the value for the ‘analyzeduration’ and ‘probesize’ options
I don’t have those logs.
The error in the ‘analysis’ log is irrelevant for this topic.
Ok,. Those logs were PM’d to Chuck.
I thought the statement:
“Consider increasing the value for the ‘analyzeduration’ and ‘probesize’ options”
was a ray of hope…
more errors…
a tonin chapter scanner (I know not on this topic) but could you advise if possible…?
Aug 29, 2018 06:12:17.047 [8936] ERROR - [MI] Read to end of file without finding a keyframe
Aug 29, 2018 06:12:17.048 [8936] ERROR - [MI] Read to end of file without finding a keyframe
Aug 29, 2018 06:12:17.075 [8936] ERROR - [MI] Read to end of file without finding a keyframe
Aug 29, 2018 06:12:17.076 [8936] ERROR - [MI] Read to end of file without finding a keyframe
Aug 29, 2018 06:12:17.077 [8936] ERROR - [MI] Read to end of file without finding a keyframe
Aug 29, 2018 06:12:17.079 [8936] ERROR - [MI] Read to end of file without finding a keyframe
I can’t tell you anything about this, but I doubt it is relevant for this topic.
I cannot give you detailed info on every error line.
Please just see how your servers behave now, with the above configuration change.
Ok thats it…
No errors in the deep scanner analysis…
I went through the scanner logs for the windows server and reported error I could see.
Since Chuck has left me with you,… does this mean I will not need any assistance with the Nvidia Shield…?
What do you mean?
The setting was on both servers active and you have disabled it now on both servers.
Correct… so are you saying problem solved…?
I cannot know that. I can only hope.
You need to monitor the future behaviour of your servers. If there are remaining issues, they will only manifest themselves in time.
[quote=“affinityhb, post:17, topic:302575”].
[/quote]
The bulk of all existing media dates are wrong… some say 2 mos but it was added over a year ago…
(and I only recreated the library a week ago)
Now I am confused as to where it is getting the dates.
