Archived topic
WordPress database error, Deadlock found
7 replies · Started by ch1800 on January 11, 2023
Hello,
I'm getting this error every couple of days at this site only since a couple of months but doesn't seem to affect the site in any visible way:
WordPress database error Deadlock found when trying to get lock; try restarting transaction for query DELETE FROMwp_optionsWHEREoption_name= '_transient_timeout_global_styles_generatepress' made by require('wp-blog-header.php'), require_once('wp-includes/template-loader.php'), include('/plugins/gp-premium/sections/functions/templates/template.php'), get_header, locate_template, load_template, require_once('/themes/generatepress/header.php'), wp_head, do_action('wp_head'), WP_Hook->do_action, WP_Hook->apply_filters, wp_enqueue_scripts, do_action('wp_enqueue_scripts'), WP_Hook->do_action, WP_Hook->apply_filters, wp_enqueue_global_styles, wp_get_global_stylesheet, get_transient, delete_option
Does this ring any bells?
Hi there,
global_styles_generatepress isn't something that exists in GeneratePress.
Perhaps it's custom functionality or a plugin?
Thanks for your feedback.
I also searched the DB ad all files and found nothing related. Strange.
I'll leave it as is and see whether it happens again later.
The fact that it's referencing our old Sections module is strange. Perhaps that module was altered or filtered into?
In fact, I always use sections and always activate the snippet that was recommended here since GP version 2:
https://generatepress.com/forums/topic/previous-latest-gpp-version-1-12-3/#post-1756795
Now, when checking this particular site, I'm surprised to see that this snippet is not there for some reason, while sections are active and working everywhere... While all other sites I manage have it active.
That snippet isn't necessary if the Sections module is already activated. The site you're using likely already had it activated before we deprecated it, or that function existed at some point allowing you to activate it, then it was removed.
Thanks Tom, I understand.
Last week, I added back this snippet to see whether it is resolved but now I see that I got the error again sometime yesterday. So, yes, it looks like the snippet does not relate to this error.
It is strange as this site has not been changed for over a year, only updated, and this error was never happening before.
As I don't see any impact on the site, I think I'll leave this as is and see how it goes.
Sounds good, let me know if anything new happens :)