Creating sort index SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_status, post_modifi
Creating sort index SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_status, post_modifi
Creating sort index SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_status, post_modifi
Creating sort index SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_status, post_modifi
Creating sort index SELECT l.ID, post_title, post_content, post_name, post_parent, post_author, post_status, post_modifi
After the crash they turn into Sleeping processes and my server cannot recover without reboot.
Hi @beboptions,
Thank you for reaching out to us, we are sorry for the troubles you are experiencing with the plugin.
In order to troubleshoot correctly, we would want a little more details about your current site.
A) Are you using the latest WordPress?
B) Are all other plugins and themes up to date?
C) Does your site meet the plugin requirements?
D) Can you give us a little more information on your hosting infrastructure and mySQL set-up?
Update crashed all my setups. Moved back to last stable version. That’s 13.5. and 14.3. for me. Had an comparable issue by migrating from 13.x to 14.0
WordPress 5.4.2
All other plugins up to date
PHP version 7.3.14-1
Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email.
…
Error Details
=============
An error of type E_ERROR was caused in line 1441 of the file /srv/wordpress/wp-content/plugins/wordpress-seo/src/generated/container.php. Error message: Uncaught Error: Class ‘Yoast\WP\Lib\Migrations\Adapter’ not found in /srv/wordpress/wp-content/plugins/wordpress-seo/src/generated/container.php:1441
Stack trace:
#0 /srv/wordpress/wp-content/plugins/wordpress-seo/vendor_prefixed/symfony/dependency-injection/Container.php(271): Yoast\WP\SEO\Generated\Cached_Container->getMigrationRunnerService()
#1 /srv/wordpress/wp-content/plugins/wordpress-seo/src/loader.php(191): YoastSEO_Vendor\Symfony\Component\DependencyInjection\Container->get(‘Yoast\\WP\\SEO\\In…’)
#2 /srv/wordpress/wp-content/plugins/wordpress-seo/src/loader.php(136): Yoast\WP\SEO\Loader->load_initializers()
#3 /srv/wordpress/wp-content/plugins/wordpress-seo/src/main.php(81): Yoast\WP\SEO\Loader->load()
#4 /srv/wordpress/wp-content/plugins/wordpress-seo/src/functions.php(26): Yoast\WP\SEO\Main->load()
#5 /srv/wordpress/wp-content/plugins/wordpress-seo/wp-seo-main.php(341): YoastSEO()
#6 /srv/wordpress/5.4.2/wp-includes/class-wp-hook.php(287): wpseo_init(”)
#7 /srv/wordpress/5.4.2/wp-includes/class
Hi @markusmai,
Thank you for chiming in. However, it would be easier if you would create a separate forum topic so we can help you more directly.
Looking at the error stack, we expect that this is caused by an incomplete or corrupt update where not all files are extracted or some of them are corrupt. We would suggest trying to do a manual installation of the latest version.
If that doesn’t work for you, please create a separate topic so we can help troubleshoot. Thanks!
A) Are you using the latest WordPress?
Yes
B) Are all other plugins and themes up to date?
Yes
C) Does your site meet the plugin requirements?
Yes
D) Can you give us a little more information on your hosting infrastructure and mySQL set-up?
VPS Running WHM/Cpanel. Only 2 Sites, both running Yoast.
Why is Yoast doing MySQL Queries randomly? Is it because of Indexables being automated?
Please give us an option to turn that off. Yoast used to be fine and these Indexables have caused so much problems for everyone.
@beboptions Thanks for the additional information. Regarding D) can you please provide version information?
As for the MySQL queries, the indexeables features shouldn’t cause random MySQL queries. Were any new pages or items added prior to the issues?
@beboptions Thanks for confirming the PHP/Database versions.
Regarding the post you referenced, it appears to be related to the generation of the Yoast sitemap on a site that has a very large number of pages/posts. Is the sitemap for your site large as well?
If so, you can reduce the number of entries in the sitemap. By default, the number of entries in the sitemap is set to 1000 but by decreasing this value it will decrease the amount of resources required to generate the sitemap. To decrease the number of sitemap entries you can use the filter wpseo_sitemap_entries_per_page. We have more information on using this developer filter at the following link: https://kb.yoast.com/kb/enable-xml-sitemaps-in-the-wordpress-seo-plugin/#limit
Yes it is relatively large.
Which PHP File can I find wpseo_sitemap_entries_per_page
@beboptions You can add the filter to your theme’s functions.php file.
For the health and safety of your site, we recommend creating backups of your site and database before you make any changes.
I’ve had Sitemaps TURNED OFF this whole time! So that can’t be the problem. I dont know why Yoast is causing my Server to crash with MySQL Creating Sort Index Queries after 24 hours.
Are you sure indexables doesnt run on its own> i see this message.
“Wait for a week or so, until Yoast SEO automatically processes most of your content in the background. Remind me in a week.”
Hi,
If you dismiss the notification for running the indexables in your WordPress dashboard, it will still continue to lazily load your metadata into the new tables. You can learn more about it here — https://yoast.com/help/why-does-yoast-seo-ask-to-index-a-sites-seo-data/
If you do nothing or dismiss the notification, most of your SEO data will gradually be stored in the new table anyway.
All I can say after several days of testing is the only way to stop server from crashing is disabling Yoast. There is some serious issue with Yoast since indexables was introduced. I have had sitemaps turned off completely so that cannot be the issue.
