Hangs while building index

  • I’m running into an issue where whenever I go to build the index it makes it through 30 posts and then just hangs.

    The output I see in the indexing logs looks like this, no matter how long I let it go:

    Wiping out the index... Done.
Counting posts... 1572 posts found.
Indexed 10 posts (total 10), processed 10 / 1572.
Indexed 10 posts (total 20), processed 20 / 1572.
Indexed 10 posts (total 30), processed 30 / 1572.

    In the browser console I see three successful log messages (with completed, percentage, etc) and then I get this error. Not sure if it’s related.

    POST https://my-domain/wp-admin/admin-ajax.php 500 (Internal Server Error)

    This is a fresh install of the plugin. I’ve tried disabling/re-enabling the plugin as well as reinstalling the plugin with the same result.

    I get the same results with “custom fields” set to “none” and “Expand shortcodes” unchecked.

    Help is much appreciated. Thanks!

    • This topic was modified 8 months, 1 week ago by leeritter.
Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Mikko Saari

    (@msaari)

    The error is likely related, but also doesn’t mean anything in itself. However, it means there’s probably something useful in the server PHP error log. If you can find out the actual PHP error from the error log, I can tell what’s up. Otherwise, I’ll be guessing.

    Thread Starter leeritter

    (@leeritter)

    Thanks for the quick reply, Mikko! I don’t have direct access to our logs, so it took me a minute to dig this up, but it looks like lots of memory exhaustion errors:

    [27-Mar-2024 06:37:44 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/test.surfersjournal.com/public_html/wp-includes/functions.php on line 7111
[27-Mar-2024 06:37:44 UTC] PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 20480 bytes) in /var/www/html/test.surfersjournal.com/public_html/wp-includes/functions.php on line 4299

    I’ve been told our memory settings are quite high. Do you have any suggestions on how to proceed?

    Plugin Author Mikko Saari

    (@msaari)

    Yeah, when you run out of 512 MB of memory, that means there’s a problem. There’s something in your posts that Relevanssi doesn’t like.

    Is shortcode expansion enabled in Relevanssi indexing settings? If it is, try disabling it. Shortcodes can cause problems like this.

    Thread Starter leeritter

    (@leeritter)

    Hmm, shoot. Yeah I was running this with “custom fields” set to “none” and “Expand shortcodes” unchecked.

    It’s strange because the indexing worked on my local machine using nearly the same database, but in production it stalls out.

    Any other ideas on how to troubleshoot this?

    Plugin Author Mikko Saari

    (@msaari)

    These memory issues are usually the hardest to troubleshoot, it’s not easy to find out what eats the memory in PHP processes.

    If the indexing always hangs in the same step, a specific post may be the problem. The Relevanssi indexing page shows you the lowest post ID indexed; the next post in line is the one below that.

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘Hangs while building index’ is closed to new replies.

Tags