Hi! We found in the logs of our website that WPML sometimes leads to critical database errors (called deadlocks) Could you check the log (below) and give us your recommendations - how can we avoid this and what is the cause of these deadlocks?
FastCGI: server "/var/run/hcgi/18256" stderr: WordPress database error Deadlock found when trying to get lock; try restarting transaction for query INSERT IGNORE INTO wp_options ( `option_name`, `option_value`, `autoload` ) VALUES ('wpml.WPML\\TM\\Settings\\ProcessNewTranslatableFields.lock', '1706460346', 'no') / LOCK / made by require_once('wp-load.php'), require_once('wp-config.php'), require_once('wp-settings.php'), do_action('wp_loaded'), WP_Hook->do_action, WP_Hook->apply_filters, WPML\LIB\WP\Hooks::WPML\LIB\WP\{closure}, WPML\FP\Promise->resolve, WPML\FP\Right->chain, WPML\FP\Right->map, WPML\BackgroundTask\BackgroundTaskLoader->WPML\BackgroundTask\{closure}, WPML\BackgroundTask\BackgroundTaskLoader->getSerializedTasks, WPML\FP\Fns::__callStatic, call_user_func_array, WPML\FP\Fns::WPML\FP\{closure}, call_user_func_array, WPML\FP\Fns::WPML\FP\{closure}, array_map, WPML\BackgroundTask\BackgroundTaskLoader->WPML\BackgroundTask\{closure}, WPML\BackgroundTask\BackgroundTaskViewModel::get, WPML\Utilities\Lock->create, WPML\Utilities\Lock->create, referer hidden link
Reference to our recent chat, meanwhile this ticket is attended by one of my colleagues, please prepare a staging/test site where we can debug/observe the issue in detail.
I've set your next reply as private to share this information safely.
IMPORTANT: If you don't see the section for providing access information, do not write in the message box or the information may appear as public.
Please share with us the access to your staging site when it is ready.
I'm enabling a private message for the following reply.
Privacy and Security Policy
We have strict policies regarding privacy and access to your information. Please see: https://wpml.org/purchase/support-policy/privacy-and-security-when-providing-debug-information-for-support/ **IMPORTANT**
- - Please backup the site files and database before providing us access. --
-- If you have a staging site where the problem can be reproduced, it is better to share access to the staging site.--
There is a server restriction on this site, and you didn't send me the access details for this. Please edit the last private message and add the access details to this server.
We need to check the DB of your site. For this, we need your approval to install the Adminer script. hidden link. But I get this error when I try to connect to your site with FTP.
Response: 530 Login authentication failed
Error: Critical error: Could not connect to server
I want to ask you please:
A. To correct the FTP access.
B. Allow me to install Adminer and check the site's DB.
I installed the Adminer script through FTP and can now access your site's DB. I've passed this information to our second-tier supporter, who will check the DB further. However, the WordPress admin access does not work for me anymore. I get this message:
Fehler: Der Benutzername admin_wpml ist auf dieser Website nicht registriert. Falls Sie über Ihren Benutzernamen unsicher sind, versuchen Sie es stattdessen mit Ihrer E-Mail-Adresse.
Could you please check and correct this?
You can edit the last private reply if needed.
Our second-tier supporters and developers have identified a potential problem with stuck WPML cron (background) jobs on your site. They made a change, and the issue might be resolved because of that change.
We want to ask you to share a DB dump PRIOR to the fix that we did today - so that we can identify properly the issue and try to prevent future such issues. For this, I'll enable private messages for the next reply.
Regards,
Itamar.
The topic ‘[Closed] WordPress database error Deadlock found’ is closed to new replies.
