-
Notifications
You must be signed in to change notification settings - Fork 67
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Excessive CPU usage caused by plugin making calls to admin-ajax.php?action=http_worker
#157
Comments
Here is my Woocommerce system report: WordPress EnvironmentHome URL: https://www.thestorytellingjeweller.com Server EnvironmentServer Info: Apache SUHOSIN Installed: – DatabaseWC Database Version: 3.1.2 Post Type Countsattachment: 1848 SecuritySecure connection (HTTPS): ✔ Active Plugins (26)Above The Fold Optimization: by PageSpeed.pro – 2.9.2 Jetpack by WordPress.com: by Automattic – 5.4 WP-Mail-SMTP: by Callum Macdonald – 0.10.1 SettingsAPI Enabled: ✔ Taxonomies: Product Visibility: exclude-from-catalog (exclude-from-catalog) WC PagesShop base: #3895 - /finished-jewelry/ ThemeName: HandMade TemplatesOverrides: handmade-3.3/woocommerce/archive-product.php Outdated Templates: ❌Learn how to update |
Hi @adam-sandor, thank you for providing the system report. It looks like you may be using the MailChimp for WordPress: by ibericode – 4.1.9 plugin and not MailChimp for WooCommerce 2.0.2. Can you confirm? |
I was using both. Now that I disabled the MailChimp plugin only the ibericode one is running. |
@adam-sandor please reference issue #158 |
Add details on --group option for WP CLI to README
After updating the plugin to version 2.0.2 my access log is full of POST requests like this:
181.224.152.147 - - [14/Oct/2017:19:44:29 +0200] "POST /wp-admin/admin-ajax.php?action=http_worker&nonce=c3674d9586 HTTP/1.0" 504 247 "https://www.thestorytellingjeweller.com/wp-admin/admin-ajax.php?action=http_worker&nonce=c3674d9586" "WordPress/4.8.2; https://www.thestorytellingjeweller.com"
The IP is always the IP of the server where the site is running. This causes my site's CPU usage to skyrocket to 50x the usual values which in turn causes my hosting provider to shut it down. This means until this is fixed I cannot use the plugin at all.
Looking at the source code I see there is a
DISABLE_WP_HTTP_WORKER
option I could enable. I'm not sure however if this would cause degraded functionality.Any ideas for workarounds or fixed to this problem?
The text was updated successfully, but these errors were encountered: