My cpu spikes just doing a simple product update in WooCommerce.
I see these errors in logs
[20-Oct-2023 13:16:01 UTC] woocommerce_blocks_checkout_order_processed is deprecated since version 7.2.0! Use woocommerce_store_api_checkout_order_processed instead. This action was deprecated in WooCommerce Blocks version 7.2.0. Please use woocommerce_store_api_checkout_order_processed instead.[20-Oct-2023 13:16:13 UTC] woocommerce_blocks_checkout_order_processed is deprecated since version 7.2.0! Use woocommerce_store_api_checkout_order_processed instead. This action was deprecated in WooCommerce Blocks version 7.2.0. Please use woocommerce_store_api_checkout_order_processed instead.[20-Oct-2023 13:16:26 UTC] woocommerce_blocks_checkout_order_processed is deprecated since version 7.2.0! Use woocommerce_store_api_checkout_order_processed instead. This action was deprecated in WooCommerce Blocks version 7.2.0. Please use woocommerce_store_api_checkout_order_processed instead.[20-Oct-2023 13:16:35 UTC] woocommerce_blocks_checkout_order_processed is deprecated since version 7.2.0! Use woocommerce_store_api_checkout_order_processed instead. This action was deprecated in WooCommerce Blocks version 7.2.0. Please use woocommerce_store_api_checkout_order_processed instead.[20-Oct-2023 19:45:06 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}
Thanks for reaching out. The errors you’re seeing in your logs are related to deprecated actions in WooCommerce, that’s why an update is recommended. The deprecation itself should not cause CPU spikes
Since you mentioned that you are getting CPU spike in resource usage, you may want to make sure that your hosting environment setup meets the WooCommerce Server Recommendations here: https://woocommerce.com/document/server-requirements/
Here are some articles that have discussed ways to minimize CPU usage spikes:
The hosting company is saying this is an issue. I am on all the up to date plugin versions. It’s a very odd deal because I dont’ have the issue with other instances. I suspect it’s a db issue on the backend.
Could you please share a copy of your site’s System Status Report so that we can better understand your site’s current environment?
Here’s how to get them:
System Status Report: navigate to WooCommerce → Status → select Get system report and then Download for support. This will download a TXT file that has the contents of the SSR to share with us.
Fatal Error log: Share a copy of any fatal error log found under WooCommerce → Status → Logs.
2023-10-03T20:43:21+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 77824 bytes) in /home/rjdrwkck/public_html/wp-includes/functions.php on line 650 2023-10-03T21:56:55+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 36864 bytes) in /home/rjdrwkck/public_html/wp-content/plugins/jetpack/_inc/lib/class.core-rest-api-endpoints.php on line 3665 2023-10-03T21:56:59+00:00 CRITICAL Allowed memory size of 134217728 bytes exhausted (tried to allocate 262144 bytes) in /home/rjdrwkck/public_html/wp-includes/Requests/src/Transport/Curl.php on line 481
The CPU spikes could be related to the Cron reschedule event error you’re experiencing or the deprecated actions error. This error typically occurs when there’s a problem with the WP-Cron events or the Action Scheduler.
The memory exhaustion errors indicate that your site exceeds the allocated memory limit. This could be due to a plugin, theme, or script demanding more resources than your server can provide.
Given the complex nature of this issue, I would recommend the following steps:
Check your WP-Cron events and Action Scheduler. You might need to adjust the schedule or fix any errors that are causing the Cron reschedule event error.
Increase your PHP Time Limit from 30 to 1200, PHP Post Max Size from 512 to 2GB, and PHP Max Input Vars from 1000 to 6144.
If the issue persists, you might need to conduct a conflict test to see if any of your theme or plugin is causing the high CPU usage. You can find a more detailed explanation of conducting a conflict test here.
If you’re not comfortable with these steps, please consider hiring a developer or contacting your hosting company for further assistance.
I hope this helps! Please let us know how it goes or if you need further assistance.
I also got this from the hosting company. Why is Jetpack causing so many issues?
After conducting our investigation, it appears that there are multiple issues stemming from the Jetpack and WordPress SEO plugins, which could be the root cause of the problem. Additionally, we’ve observed a significant spike in website traffic over the past month. Notably, the most frequently accessed URL is ‘/wp-json/oec-products-purchase-notifier/v1/get-notifications,’ which is undoubtedly associated with a plugin that may be contributing to these issues.These are some points which you need to check this out in order to resolve your issue .
Furthermore, we’ve detected some issues related to JavaScript. Please review the screenshot below for further information.
"[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/rjdrwkck/public_html/wp-content/plugins/woocommerce/src/Internal/Admin/Analytics.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/rjdrwkck/public_html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:90[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Class "Yoast\WP\Lib\Dependency_Injection\Container_Registry" not found in /home/rjdrwkck/public_html/wp-content/plugins/wordpress-seo/lib/abstract-main.php:42[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Interface "YoastSEO_Vendor\Symfony\Component\DependencyInjection\ResettableContainerInterface" not found in /home/rjdrwkck/public_html/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php:38[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/rjdrwkck/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-waf/src/class-waf-runner.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/rjdrwkck/public_html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:90[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Class "Yoast\WP\Lib\Dependency_Injection\Container_Registry" not found in /home/rjdrwkck/public_html/wp-content/plugins/wordpress-seo/lib/abstract-main.php:42[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Class "Yoast\WP\Lib\Dependency_Injection\Container_Registry" not found in /home/rjdrwkck/public_html/wp-content/plugins/wordpress-seo/lib/abstract-main.php:42[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/rjdrwkck/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-backup/src/class-package-version.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/rjdrwkck/public_html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:90[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Class "WPSEO_Register_Capabilities" not found in /home/rjdrwkck/public_html/wp-content/plugins/wordpress-seo/wp-seo-main.php:460[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/rjdrwkck/public_html/wp-content/plugins/wpforms/pro/includes/admin/class-updater.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/rjdrwkck/public_html/wp-content/plugins/wpforms/pro/wpforms-pro.php:61[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/rjdrwkck/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-connection/src/class-rest-connector.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/rjdrwkck/public_html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:90[31-Oct-2023 17:23:14 UTC] PHP Fatal error: Uncaught Error: Failed opening required '/home/rjdrwkck/public_html/wp-content/plugins/jetpack/jetpack_vendor/automattic/jetpack-backup/src/class-package-version.php' (include_path='.:/opt/alt/php81/usr/share/pear:/opt/alt/php81/usr/share/php:/usr/share/pear:/usr/share/php') in /home/rjdrwkck/public_html/wp-content/plugins/jetpack/vendor/jetpack-autoloader/class-php-autoloader.php:90[31-Oct-2023 17:23:25 UTC] Cron reschedule event error for hook: action_scheduler_run_queue, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}[31-Oct-2023 17:23:26 UTC] Cron reschedule event error for hook: rocket_rucss_pending_jobs, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"rocket_rucss_pending_jobs","args":[],"interval":60}[31-Oct-2023 17:23:26 UTC] Cron reschedule event error for hook: rocket_rucss_on_submit_jobs, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"rocket_rucss_on_submit_jobs","args":[],"interval":60}[31-Oct-2023 17:23:26 UTC] Cron reschedule event error for hook: action_scheduler_run_queue_rucss, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"every_minute","args":["WP Cron"],"interval":60}[31-Oct-2023 17:23:26 UTC] Cron reschedule event error for hook: rocket_preload_process_pending, Error code: invalid_schedule, Error message: Event schedule does not exist., Data: {"schedule":"rocket_preload_process_pending","args":[],"interval":60
From your hosting company’s feedback and the error logs you’ve shared, it looks like the Jetpack and WordPress SEO plugins may be causing some of the issues you’re experiencing. The /wp-json/oec-products-purchase-notifier/v1/get-notifications URL, which is being accessed frequently, is likely associated with one of these plugins.
The PHP fatal errors you’re seeing are due to missing files or classes. This could be due to a number of reasons such as a failed update, missing files during installation, or a conflict with another plugin or theme.
Here’s what I recommend:
Try deactivating and reactivating the Jetpack and WordPress SEO plugins. If the issue persists, you may need to uninstall and reinstall these plugins.
Check if there are any updates available for these plugins. If there are, please update them.
If the issue still persists after reinstalling the plugins, you might need to conduct a plugin conflict test. This involves deactivating all your plugins and then reactivating them one by one to identify which one is causing the issue.
If you’re not comfortable performing these steps, I recommend getting in touch with a developer or your hosting company for further assistance.
I hope these steps help. Please let us know how it goes or if you need any further assistance.
