TYPO3 9.5 "Cannot unserialize TYPO3\CMS\Core\Locking\FileLockStrategy" during cache reading
after several issues related to the caches (we're using LazyObjects) now there's an issue with the reading from cache.
Error page is attached.
As reference for the model structure you can look into https://forge.typo3.org/issues/91364 where I added the models that are used to be stored in cache (ticket is from the original issue related to v10).
Since 9.5.17 these issues are also in v9.
The error always occurs after the page rendering itself worked once, but it seems to be also a general issue cause this also happens if we run a Command that deletes the cache entries for specific products.
Happy to answer any additional questions that may come up to get this solved asap - cause it prevents us from updating our app we currently run on 9.5.16 which did not had these issues.
#4 Updated by Carsten Hülsmann 10 days ago
Oliver Hader wrote:
Is there a possibility to get a slim version of that extension (narrowed down to the actual problem causing this problem)?
There also should be an error on serializing
FileLockStrategy- this was introduced with #88573 in terms of security hardening.
I'm not sure if this will be possible. The extension is just part of a whole TYPO3 project.
There are services that rely on env vars - which are required to render a page (e.g. to fetch additional Data from a PIM on the fly).
I'll check what I can do, to narrow it down as far as I can without breaking the other stuff.
Regarding the missing error on "serializing" - we had that before the latest update (unfortunately I can't say anymore if it was actually a FileLockStrategy issue). Then everything seemed to work well but than this issue appeared.
Just a heads up: I'm currently clarifying if I'm allowed to share the whole Extension.
#5 Updated by Carsten Hülsmann 3 days ago
Instead of sharing the whole extension here (which wouldn't work as mentioned above) and to narrow it down is nearly impossible in this project so I wouldn't like to share it for now.
However I build a work around now by putting the rendered view into the cache instead of the product object including it's relations.
Unfortunately I've seen this error also occuring by manually starting scheduler tasks - so I believe this is not neccessarily related to the Product Object itself but maybe a configuration issue (which I couldn't find by now).
In case I am able to reproduce this issue (e.g. in the Scheduler) I can mention it here or in another ticket.