Edrock200 53 Posted December 28, 2021 Posted December 28, 2021 I've got an odd issue on an emby box that has persisted through v4.5 through 4.6.7. the last full scan reports months ago. I will kick off a full scan, it will complete, and report correct. But the next time emby is restarted, same thing. I've confirmed the host clock and Emby docker container timezones are correct. Attached is an example of what I'm referring to.
Happy2Play 9783 Posted December 28, 2021 Posted December 28, 2021 Can you post as server log after running Schedule task library scan.
Luke 42085 Posted December 28, 2021 Posted December 28, 2021 I would check the date and time of the client machine as well.
Edrock200 53 Posted December 28, 2021 Author Posted December 28, 2021 I can def post the logs, but it doesn't seem to happen until a restart of the container, e.g. right now it shows this
Luke 42085 Posted December 29, 2021 Posted December 29, 2021 19 hours ago, Luke said: I would check the date and time of the client machine as well. This is what I would focus on first, for both the server and client machines.
Edrock200 53 Posted December 29, 2021 Author Posted December 29, 2021 So on that same host is a second emby docker instance with same tz settings. Checking it from same client pre and post restart doesn't revert. But let me dig into it some more. I once again suspect it's something on my end. Was just curious if this was a known thing or perhaps an easy fix/cause might be known. Thanks again for the fast replies and sorry for always bugging you guys. Really love the product and support though! These forums are much more responsive than other platforms and it's noticed and appreciated. 1
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now