[TYPO3-english] typo3temp folder under NFS

Sergio Catalá scatala.enet at gmail.com
Tue Feb 10 14:13:33 CET 2015


Hi Loek,

The problem only occurs when we clear typo3temp/Cache folder and it has to
be rebuilt again (no extensions write under typo3temp/). Then, as you
mentioned, several processes try to write the cache at the same time and,
after some minutes, we see the "Could not acquire lock" error. Only when we
restart the DNS, and no one is able to access the website (only us), we can
rebuild the cache again properly.

We tried to change the "lockingMode" parameter to (flock, or semaphore) in
the Install tool, but without success. All developers point to the fact
that the locking method is hard-coded as "simple".

After some research (here the main blueprint:
http://wiki.typo3.org/Blueprints/LockingForCaches) and talking to Markus
Klein about it, the Typo3 core is still working on a proper locking
mechanism.

He recommended me to separate the typo3temp/ folders on every machine and
not to use NFS to share it between different servers, but that didn't work
for us.

We are still pending of a solution to this problem. Every time we clear the
cache, the problem occurs again.

Regards,
Sergio


More information about the TYPO3-english mailing list