too many Deadlock found when trying to get lock mysql error

  • In our database we found so many errors like errors below from this plugin :

    WordPress database error Deadlock found when trying to get lock; try restarting transaction for query DELETE FROM wp_options WHERE option_name = ‘_transient_ure_key_cap’ made by include(‘wp-blog-header.php’), include(‘wp-load.php’), include(‘/newpartition/public_html/web/wp-config.php’), include(‘wp-settings.php’), include(‘/plugins/user-role-editor/user-role-editor.php’), User_Role_Editor->__construct, URE_Own_Capabilities::get_key_capability, get_transient, delete_option

Viewing 4 replies - 1 through 4 (of 4 total)
  • Plugin Author Vladimir Garagulya

    (@shinephp)

    Thanks for this note.
    Will it help if you increase this transient life time changing 60 at line 74 of user-role-editor/includes/ure-own-capabilities.php to 120, for example?

    I will remove transients usage from this part with a next update.

    Vlad

    I too am getting similar in error logs for v 4.30 as follows:

    mydomain.co.uk [Mon Feb 20 02:57:37 2017] [error] [client 108.162.246.43:33236] AH01215: 
WordPress database error Deadlock found when trying to get lock; try restarting transaction for query 
DELETE FROM <code>rY73sP5x_options</code> WHERE <code>option_name</code> = '_transient_timeout_ure_key_cap' made 
by require('wp-blog-header.php'), require_once('wp-load.php'), require_once('wp-config.php'), 
require_once('wp-settings.php'), include_once('/plugins/user-role-editor/user-role-editor.php'), 
User_Role_Editor->__construct, URE_Own_Capabilities::get_key_capability, get_transient, 
delete_option: /home/sites/mydomain.co.uk/public_html/index.php

    and also this one….

    mydomain.co.uk [Mon Feb 20 03:18:43 2017] [warn] [client 141.101.98.96:59195] AH01220: 
Timeout waiting for output from CGI script /home/sites/mydomain.co.uk/public_html/wp-
admin/admin-ajax.php

    The deadlock error appears to have gone now on updating to v4.31.1

    Plugin Author Vladimir Garagulya

    (@shinephp)

    Thanks for the feedback.
    ‘Deadlock’ problem during WordPress transients cleanup is general for sites with high load. For example:
    WooCommerce.

    It’s recommended to use some caching plugin (like W3 Total Cache or other) and activate object caching. WordPress will not use database for transients in this case, so deadlock problem will not appear.,

Viewing 4 replies - 1 through 4 (of 4 total)
  • The topic ‘too many Deadlock found when trying to get lock mysql error’ is closed to new replies.