-
Notifications
You must be signed in to change notification settings - Fork 611
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[4.x]: Could not acquire a lock when updating singles #14871
Comments
I’m not able to reproduce this. It could be that a previous mutex lock wasn’t released properly, for that single section’s entry. Are you overriding the |
Commenting out my mutex override fixed this. Thank you! |
Before you close this, do we still need redis for multi-server sites? I had the code below, with the mutex commented out now, as you said.
|
Nope! As of 4.6 it’s fine to use the built-in |
What happened?
Description
I was getting a lot of errors of the form Could not acquire a lock to save a revision for element 60 when trying to apply project config. I turned off versioning on all sections and was able to apply proejct config.
Now I'm trying to turn it back on, and every single is giving me this error on its elementId when I try to turn on revisions.
Steps to reproduce
Expected behavior
Versioning can be turned on
Actual behavior
I get an error:
Additional Information
Craft: 4.8.10 (though it was happening for previous versions as well)
Plugins:
Craft CMS version
4.8.10
PHP version
8.1
Operating system and version
Mac, Linux
Database type and version
MySQL, Mariadb
Image driver and version
No response
Installed plugins and versions
Admin Bar 4.3.0
Asset Usage 3.3.0
Blitz 4.16.3
CKEditor 3.8.3
CodeMirror 2.0.0
Colorit 4.0.0
Element API 4.1.0
Field Manager 3.0.8
HOMM XML Sitemap 1.0.3
Hyper 1.1.27
Imager X Lite 4.4.0
Inlin
Mix 1.7.1
Retcon 2.7.5
Retour 4.1.16
SuperTable 3.0.13
The text was updated successfully, but these errors were encountered: