the_content
filter or add an additional new filter in shouldDisplay()
which allows returning false
there based on our own custom logic?
Currently function contentDisplay
is running at every single post/page display and sometimes causes general server overload issues when it looks for available forms and markup in database even though the output is never required/used on our site.
Like a lot of users, I’m facing of a large cache issue for a month or more and have to flush it twice a day. It’s not manageable at all.
Can you help debugging this? Our config seems to be fine and we’ve read almost all the docs and faq about that kind of issue. Nothing’s better.
Can you help me analyze and find which element (plugin, .js, .css) is taking all the cache in order to exclude it?
Thanks in advance.
[22-Mar-2022 10:47:35 UTC] WordPress database error DELETE command denied to user ‘user’@’localhost’ for table ‘wp_options’ for query DELETE FROM wp_options
WHERE option_name
= ‘auto_updater.lock’ made by do_action_ref_array(‘wordfence_daily_cron’), WP_Hook->do_action, WP_Hook->apply_filters, wordfence::dailyCron, wordfence::_refreshUpdateNotification, wfActivityReport->getUpdatesNeeded, wfUpdateCheck->checkAllUpdates, wfUpdateCheck->checkCoreUpdates, wp_version_check, do_action(‘wp_maybe_auto_update’), WP_Hook->do_action, WP_Hook->apply_filters, wp_maybe_auto_update, WP_Automatic_Updater->run, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock, WP_Upgrader::create_lock,
etc….
I checked the DB privileges for the user and sure enough, the DELETE permission had been revoked (now fixed), but my question is, why the cascade of error messages – seems like a bug to me.
In our logs we traced many calls like /?packlink_pro_controller=Async_Process&action=run&guid=3099_6150217c4b1257.25070646, one call each 10 sec (almost)
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:58:46 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2164_61501a25124926.28732912 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:58:53 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1295_61501a2c0049d4.00324635 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:58:59 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2640_61501a32cf8203.67645628 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:06 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2641_61501a39c2f3f9.78520337 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:13 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1195_61501a40a25d29.03434327 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:20 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2166_61501a4783cf87.08386108 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:27 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1708_61501a4e6ca876.21989626 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:34 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1711_61501a55459c71.45335880 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:41 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=26949_61501a5c203a33.86461605 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:48 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=773_61501a6345c160.41560856 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:08:59:55 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1295_61501a6a28f9c2.62637645 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:02 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2638_61501a70eb1453.68882541 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:15 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2640_61501a7e084265.92317763 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:22 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2166_61501a85b005e1.76439153 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:29 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1708_61501a8cd9ab33.35092403 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:36 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=1711_61501a93a92510.65735767 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:43 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=26949_61501a9a7eb854.83274598 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:50 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2164_61501aa15acb11.35288258 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:00:57 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=773_61501aa84cdc78.76652772 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:01:04 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=2638_61501aaf2dd739.11157317 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
XXX.XXX.XXX.XXX - - [26/Sep/2021:09:01:11 +0200] "POST /?packlink_pro_controller=Async_Process&action=run&guid=3099_61501ab62d3c68.17310046 HTTP/1.1" 499 0 "-" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36"
We got many 499 errors, we have to go deep with our analysis, but the problem is that all POST bypass Varnish cache and load a lot our application
Can we have more info about it? Is it possible to change the scheduler?
Thanks
Diego
]]>cerber_daily overloads database.
Maintenance tasks schedule maybe is better to be configurable instead of running on midday (peek time on some websites)
]]>Last night our WooCommerce site got overloaded again… :'(
So since this was the 2nd time this month I’m seeking for some advice on how to -hopefully- prevent it from happening again in the future.
The background
We are bunch of whisky enthusiasts who buy casks and split them into cask shares (all non-profit basis, just against cost price to keep it affordable for everyone). This concept has grown in popularity over the past 8 years and currently there are about 800 people who regularly buy a cask share.
Typically there are about 40 to 80 shares per cask available so with about 800 people interested in the more popular whisky brands it’s quite a rampage when the cask gets published on Wednesday at 19:00 CET… the server can’t handle the load with the populair brands and is then fully overloaded…
Current hosting package and server config
We are currently using the Enthusiast hosting plan of One.com which comes with 2 GB memory and 2x CPU priority (whatever that means in terms of actual CPU capacity I don’t know, I’ve already raised the question with One.com).
In the wp-config.php we’ve already configured: define('WP_MEMORY_LIMIT', '1500M');
but I’m not 100% sure if WordPress / WooCommerce actually uses up to that amount of memory in reality. I already opened the support request with One.com to look into this as I don’t have access to the memory / cpu statistics from the One.com Dashboard.
The question
Does anyone has any idea / pointers how much server capacity would be needed to handle this kind of peak load?
Are there other things I can look into to improve the performance of WooCommerce?
Btw – I’d already disabled most plugins and sections of the website which are not relevant to the WooCommerce environment prior to tonight’s release of the new cask. So everything was already running in a more or less ‘naked’ setup.
Oh – I already read https://docs.woocommerce.com/document/woocommerce-scaling-faqs/# but that is not getting me into the direction I need.
]]>First, MANY thanks for a usually excellent plugin.
This is for information rather than a request for help. The problem came up when I was creating a page with multiple examples of the Shortcodes Ultimate Gallery. I wanted to make an archive of all the posts on my website organised chronologically by year. The Shortcodes Ultimate Gallery lets me use the header image from each post as the link, which is great.
I was aware that I couldn’t put more than 100 links in each Gallery, but I had a Gallery for each year and I thought that would work. It did, up to a point. But after I’d filled 7 Galleries (for each of 7 years) with around 60 links in each, the page seems to have been overloaded. WP returned a fatal error warning. (See below.)
There’s no harm done. The site is still functioning as it should and all the Shortcodes Ultimate shortcodes I’ve got set up seem to be fine too (including one of the Gallery). But I had to bin the page I’d been working on. Now I need to think of another way to organise my archive.
Here’s the error warning (clipped from an e-mail WP sent me):
WordPress version 5.4.1
Current theme: GeneratePress Child – SC (version 0.1)
Current plugin: Shortcodes Ultimate (version 5.8.1)
PHP version 7.3.0RC1
Error Details
=============
An error of type E_ERROR was caused in line 133 of the file /storage/content/70/109970/thesupercargo.com/public_html/wp-content/plugins/shortcodes-ultimate/includes/shortcodes/custom-gallery.php. Error message: Uncaught Error: Cannot use object of type WP_Error as array in /storage/content/70/109970/thesupercargo.com/public_html/wp-content/plugins/shortcodes-ultimate/includes/shortcodes/custom-gallery.php:133
Stack trace:
#0 /storage/content/70/109970/thesupercargo.com/public_html/wp-includes/shortcodes.php(343): su_shortcode_custom_gallery(Array, ”, ‘su_custom_galle…’)
#1 [internal function]: do_shortcode_tag(Array)
#2 /storage/content/70/109970/thesupercargo.com/public_html/wp-includes/shortcodes.php(218): preg_replace_callback(‘/\\[(\\[?)(su_cus…’, ‘do_shortcode_ta…’, ‘\n2013 ̵…’)
#3 /storage/content/70/109970/thesupercargo.com/public_html/wp-includes/class-wp-hook.php(287): do_shortcode(‘\n2013 ̵…’)
#4 /storage/content/70/109970/thesupercargo.com/public_html/wp-includes/plugin.php(206): WP_Hook->apply_filters(‘\n2013 ̵…’, Array)
#5 /storage/content/70/109970/thesupercargo.com/public_html/wp-content/plugins/wordpress-seo/admin/links/class-link-watcher.php(144): apply_filters(‘
I’ve put a product online which has very high demand right now and I have limited stock. So every time I put up some stock the server gets swarmed by users trying to buy and the whole thing crashes
Is there any way of handling such high request items via a Plugin? Does anyone have any tips? The Server is a dedicated i7-2600, 16GB DDR3 with SSD and 1 GBit Port.
I’m happy for any help.
Thanks and stay safe
]]>