Corrupted cache

[Space]

Code: Select all

[6/13/2021 7:38:01 PM] [ INFO] The cache file appears to be corrupted and will need to be rebuilt.
[6/13/2021 7:38:01 PM] [ INFO] After parsing a value an unexpected character was encountered: S. Path 'tRYPVAK3AfG2OQ1+tdOTKA.jsonEntry', line 54460, position 555.

Gary,

What are the potential reasons that a cache could get corrupted?

Is it possible that EPG123 generated a corrupted cache?

The cache was fine during the previous day's run...

I am still running 1.6.3.0.

Did SD ever switch to the new API? Could this be the cause?

I've never seen this before and it has me worried that I may have a hardware problem... I'm trying to rule out a potential disk issue.

EDIT: Also, perhaps a corrupted cache should have a higher status message than "INFO"? Particularly if it is not caused more often by an innocuous reason.

[garyan2]

Don't know what could have caused it. I originally had put this in when I was compressing the cache file and found some folks were getting corrupted cache files which is the main reason why I stopped compressing it. Could you search the epg123cache.json file for the md5 text tRYPVAK3AfG2OQ1+tdOTKA to see if it is still part your listings and post the entry?

This is only an information because it does not affect the integrity of the guide. EPG123 will simply create a new and fresh cache file (downloading everything again).

SD has not moved to the new API yet. It was rescheduled again for yesterday, but still hasn't happened.

[Space]

Unfortunately, that md5 is not in the current cache file.

Perhaps it would be a good idea to rename the existing cache file instead of deleting it when it is found to be corrupt? Although that may leave a bunch of cache files taking up space.

Perhaps just output the section that was causing the problem to a debug file...