PHP message: WordPress database error Deadlock found when trying to get lock

  • Resolved jaypabs

    (@jaypabs)


    6 years, 2 months ago

    I’m trying to fix this deadlock issue on my site without luck. I’m using WordFence and when I disable it, the error is gone. I disabled the plugin by removing it completely and reinstall it again, but the error also appear whenever I reinstall it.

    Note that I have uninstalled the plugin completely as suggested by WordFence.

    Anyone know what’s causing this?

    Here’s the log on my server:

    2018/09/14 01:13:38 [error] 21753#21753: *2868716 FastCGI sent in stderr: "PHP message: WordPress database error Deadlock found when trying to get lock; try restarting transaction for query INSERT IGNORE INTOpn_wfconfig(name,val,autoload`) VALUES (‘wfSyncGeoIP.lock’, ‘1536912818’, ‘no’) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::veryFirstAction, wfConfig::createLock, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query” while reading response header from upstream, client: 34.232.72.139, server: mysite.com, request: “GET /2017/09/19/sample-article/feed/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9011”, host: “mysite.com”
    2018/09/14 01:13:57 [error] 21753#21753: *2869493 FastCGI sent in stderr: "PHP message: WordPress database error Deadlock found when trying to get lock; try restarting transaction for query INSERT IGNORE INTOpn_wfconfig(name,val,autoload`) VALUES (‘wfSyncGeoIP.lock’, ‘1536912837’, ‘no’) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::veryFirstAction, wfConfig::createLock, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query” while reading response header from upstream, client: 54.241.188.65, server: mysite.com, request: “GET /test-article/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9011”, host: “mysite.com”, referrer: “search.yahoo.com/”
    2018/09/14 01:14:03 [error] 21753#21753: *2869668 FastCGI sent in stderr: "PHP message: WordPress database error Deadlock found when trying to get lock; try restarting transaction for query INSERT IGNORE INTOpn_wfconfig(name,val,autoload`) VALUES (‘wfSyncGeoIP.lock’, ‘1536912842’, ‘no’) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::veryFirstAction, wfConfig::createLock, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query” while reading response header from upstream, client: 13.56.241.76, server: mysite.com, request: “GET /2013/07/17/testing/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9011”, host: “philnews.ph”, referrer: “android-app://com.google.android.googlequicksearchbox”
    2018/09/14 01:14:03 [error] 21753#21753: *2869683 FastCGI sent in stderr: "PHP message: WordPress database error Deadlock found when trying to get lock; try restarting transaction for query INSERT IGNORE INTOpn_wfconfig(name,val,autoload`) VALUES (‘wfSyncGeoIP.lock’, ‘1536912843’, ‘no’) made by require(‘wp-blog-header.php’), require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::veryFirstAction, wfConfig::createLock, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query” while reading response header from upstream, client: 54.193.113.108, server: mysite.com, request: “GET /sample/ HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9011”, host: “mysite.com”, referrer: “mysite.com/articl1/”
    2018/09/14 01:15:14 [error] 21753#21753: *2871964 FastCGI sent in stderr: "PHP message: WordPress database error Deadlock found when trying to get lock; try restarting transaction for query INSERT IGNORE INTOpn_wfconfig(name,val,autoload`) VALUES (‘wfSyncGeoIP.lock’, ‘1536912914’, ‘no’) made by require_once(‘wp-load.php’), require_once(‘wp-config.php’), require_once(‘wp-settings.php’), do_action(‘plugins_loaded’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::veryFirstAction, wfConfig::createLock, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection_QueryCaching->query, W3TC\_CallUnderlying->query, W3TC\DbCache_Wpdb->query, W3TC\DbCache_WpdbInjection->query, W3TC\DbCache_Wpdb->default_query

    • This topic was modified 6 years, 2 months ago by jaypabs.
    • This topic was modified 6 years, 2 months ago by jaypabs.
Viewing 10 replies - 16 through 25 (of 25 total)
  • ultiworld

    (@ultiworld)

    We are also dealing with similar errors regarding deadlocks caused by WordFence. Noticed an uptick in them within the past few weeks, usually a few every day it seems like.

    Plugin Support wfphil

    (@wfphil)

    Hi all users in this topic,

    If the Wordfence plugin directory is deleted or renamed, and another copy of Wordfence is installed without the Wordfence wflogs directory being removed, then it looks like a site can get stuck in a state of needsGeoIPSync flag being on.

    One workaround would be to:

    1) Remove the ~/wp-content/wflogs/GeoLite2-Country.mmdb file.

    2) Delete _transient_timeout_wfSyncGeoIPActive and _transient_wfSyncGeoIPActive from the wp_options table

    This should then force everything to resynchronise.

    Thanks.

    Thread Starter jaypabs

    (@jaypabs)

    Hi @wfphil,

    This seems to be working now. No deadlock error yet for several minutes.

    I’ll update here again if I encounter the same problem.

    Thank you for the support.

    Thread Starter jaypabs

    (@jaypabs)

    I can confirm that the workaround above by wfphil is working. Deadlock error is gone.

    Plugin Support wfphil

    (@wfphil)

    Hi @jaypabs,

    Thank you for the update and glad to hear that it is working now. I will mark your topic as resolved.

    @christoxl, @barrypersonalctonet, @neltseng, @ultiworld

    If this doesn’t work for you and you want to come back here and say that this has not been resolved then please start your own topic as per forum guidelines below:

    “Unless users have the exact same version of WordPress on the same physical server hosted by the same hosts with the same plugins, theme, and configurations, then the odds are the solution for one user will not be the same for another. For this reason, we recommend people start their own topics.”

    Forum Guidelines

    Thank you.

    Thread Starter jaypabs

    (@jaypabs)

    Hi @wfphil,

    Sad to say but the error is back. And it gives a lot of CPU load on my server with this Deadlock error. After uninstalling it manually, the load of my server were back to normal.

    Plugin Support wfphil

    (@wfphil)

    Hi @jaypabs

    I am sorry to hear that this has come back. I will let the team know about this.

    Thank you.

    Plugin Support wfphil

    (@wfphil)

    Hi @jaypabs,

    Did it happen shortly after updating the plugin? If so, you can go through the workaround provided before. We do have a bug case open for this and scheduled for it to be fixed in version 7.1.19, as long as there aren’t any factors that prevent a fix from being implemented in that version.

    Thanks.

    Thread Starter jaypabs

    (@jaypabs)

    @wfphil,

    If I remembered well, it happens after I update/upgrade Ubuntu 18.04. Update includes but not limited to MySQL and PHP.

    Plugin Support wfphil

    (@wfphil)

    Hi @jaypabs

    Thank you for the update. The fix is scheduled to be included in the next version release of Wordfence.

    Thanks.

Viewing 10 replies - 16 through 25 (of 25 total)
  • The topic ‘PHP message: WordPress database error Deadlock found when trying to get lock’ is closed to new replies.