PHP Errors 40 gigabytes in size

This appears to be due to a new indexing feature to speed up the site. This is not the first time there have been problems with this feature. Tell me how to turn it off, I’m tired!

Hi @progresssite,

Thank you for reaching out.

We understand that your are getting a huge error log file on your site because of a repeating error in the log. We are sorry you are experiencing this issue.

First off, we see that the repeating error is indeed related to the plugin trying to index your content into the Yoast indexables table. It looks like the plugin is trying to insert duplicate entries in the table where the entry already exists.

If not already, please make sure to be running our latest 15.0 release if you are currently running an older version. If you are on 15.0, we’d recommend you to try the following:

1) Install the Yoast Test Helper plugin, found here https://www.ads-software.com/plugins/yoast-test-helper/
2) Go to Tools → Yoast Test
3) Click the Reset Indexables tables & migrations button.
4) Go to SEO → Tools.
5) Click the Start processing and speed up your site now button and let it complete.

Can you let us know if that resolves the issue?

Did as you said, the problem remains https://yadi.sk/d/-ENQMGyiwGAWcA

Hi @progresssite,

Thank you for getting back to us.

Sorry to hear those steps did not solve this error on your site. To troubleshoot this further, we’d like to know a few things about your site and your set-up.

A) Are you using Yoast SEO 15.0?
B) Are you using WordPress 5.5.1?
C) Are all other plugins and themes also up to date? If not, please install any update and check if the issue persists.
D) Does your site/host meet our plugin requirements listed here: https://yoast.com/help/plugin-requirements/?
E) Does the same issue persist when Yoast SEO is the only active plugin on the site? You can check this either on a staging site or when you troubleshoot with the Health Check plugin. We have some information on checking for conflicts here: https://kb.yoast.com/kb/how-to-check-for-plugin-conflicts/.

Where can I write to you?
Information is not public

@jeroenrotty,

We are experiencing a similar issue as reported moments ago in this support forum.

Your indexing feature appears to demand a lot of memory (short term) which shared servers cannot supply thus crashing websites and triggering a “HTTP ERROR 500” on all browsers.

Help appreciated. Your standard troubleshooting procedures are not yielding beneficial results.

Cheers!

Hi all,

We’re sorry that it’s taking some time to work through these issues! We’re just making sure that this isn’t related to any other reasons why an error can happen, so we appreciate your patience.

@progresssite Thanks for sending us the log information. The support we can offer for Yoast SEO is only available in this public forum.

The “Duplicate entry ‘0’ for key ‘PRIMARY'” error indicates that the primary key is being reused which should not happen if the table has the correct permissions. Can you please check that the table ‘wp_yoast_seo_links’ has a primary key set for the ID column and is set to auto-increment. If you are not familiar with checking your database settings, your webhost can help.

@jetxpert Thanks for bringing the problem you’re having to our attention. We’ll reply to you on the separate topic you started.

@priscillamc Yes it is https://yadi.sk/i/IUh3lmtHwKrh_A

Hi, @jeroenrotty, @priscillamc

All plugins are the freshest, WordPress and plugins auto-update included.

Yoast SEO 15.0
WordPress 5.5.1

PHP 7.3
PHP memory 512Mb
cURL Information 7.52.1
OpenSSL/1.0.2u
Registered Stream Socket Transports tcp, udp, unix, udg, ssl, tls, tlsv1.0, tlsv1.1, tlsv1.2

mysql Ver 15.1 Distrib 10.2.33-MariaDB, for debian-linux-gnu (x86_64) using readline 5.2

I tried to disable all plugins except Woocommerce and Yoast SEO, and installed the Storefront theme, errors still appear in the same amount, here is the log https://yadi.sk/d/8RWNYCMMmN4WJA

Presumably, the problem may be related to the fact that for each separate city we have a separate subdomain, with one WordPress core.
Here is a screenshot from the database, table yoast_indexable, see column “permalink”
https://yadi.sk/i/m4zdSI8BUI1ofg

This is how it is implemented in wp-config.php https://yadi.sk/i/RTgSgpWH-DHI_g

@jeroenrotty, @priscillamc
As soon as the 15th version came out, these problems began, and a high load on the CPU and RAM appeared
https://yadi.sk/i/sZHDuR1RmzdPXA

Hi,

Would it be possible for you to check if the wp_yoast_undexable table has a primary key set for the ID column and is also set to auto-increment?

Please also do try re-running the Indexables feature using the Yoast Test Helper plugin and checking if this helps.

@mikes41720 Hi,

Would it be possible for you to check if the wp_yoast_undexable table has a primary key set for the ID column and is also set to auto-increment?

screenshot table https://yadi.sk/i/b0lzoYJ1vq8v7A

Please also do try re-running the Indexables feature using the Yoast Test Helper plugin and checking if this helps.

Tried doing this many times, the error remains the problem

@progresssite,

Thank you for bringing this issue to our attention!

We apologize?for the trouble you are currently experiencing with our plugin. Luckily, a “bug report” has been filed already.

What’s next?
Our product team will assess the severity of this problem in relation to other open bug reports and new features. Based on their assessment, the bug report will be given a priority. Our developers work on the highest priority issues first. Unfortunately, this means we cannot give you an estimate when they’ll start working on your report.

If you have any further information that may affect the prioritization or help our development team solve this bug, please feel invited to reply to this forum topic, leave a comment or subscribe to the GitHub report to get updates on the issue.

@maybellyne @mikes41720 Can you please tell me if there is a hook, can I disable this indexing?
If not, then implement such a hook in the next version of the plugin so that I can disable indexing in the theme file.
Since the site is not working because of this problem, we urgently need to solve it.

• This reply was modified 4 years, 1 month ago by progresssite.

We are afraid to say that there’s no hook available to disable the Indexables feature completely. However, if you think it would be a useful feature to have, please do feel free to submit a feature request for this in our GitHub Development Repository so our development team can decide on this.