Indexing stucks at same count

  • Resolved nikolausii

    (@nikolausii)


    3 years, 9 months ago

    I try to get an index for my site. But it stucks at the same count almost every time.
    The shortcode expansion is disabled, custom fields are none however I have tried it with but that had the same effect.

    I got the following information:

    Build the index

    Relevanssi-Output:
    Time elapsed: 0:14:36 | Time remaining: about 2 hours

    […]
Indexed 65 posts (total 8325), processed 8325 / 90592.

    Browser-Console:

    Truncating index.
Truncate index: true
Counting posts.
Counted 90592 posts.
[…]
{completed: 8325, percentage: 9.189553161427058, feedback: "Indexed 65 posts (total 8325), processed 8325 / 90592.\n", offset: true}
POST https://<url>/wp-admin/admin-ajax.php?_fs_blog_admin=true 500 in load-scripts.php?c=0&load[chunk_0]=jquery-core,jquery-migrate,utils&ver=5.7.2:2

    Index unindexed posts

    Relevanssi-Output:
    Counting posts... 82252 posts found.

    Browser-Console:

    Counting posts.
Counted 82252 posts.
Failed to load resource: the server responded with a status of 500 () in /wp-admin/admin-ajax.php?_fs_blog_admin=true:1

    Don’t know what else to do.

    The page I need help with: [log in to see the link]

Viewing 6 replies - 1 through 6 (of 6 total)
  • Thread Starter nikolausii

    (@nikolausii)

    Maybe the state of the index after a reload is interesting:

    State of the index 

    8340 documents in the index.
4736878 terms in the index.
169344 is the lowest post ID indexed.
    Plugin Author Mikko Saari

    (@msaari)

    500 server error usually means there’s something helpful in the server error logs. Check there to see if there’s some hint there.

    Relevanssi indexes posts in descending order of post ID, so if you can’t proceed, the problem post may be the next one in ID order. Is there something special about that post?

    Thread Starter nikolausii

    (@nikolausii)

    I found only this line to Relevanssi in the debug.log:
    PHP Fatal error: Maximum execution time of 180 seconds exceeded in /var/www/web304/htdocs/www.lexika.de/html/wp-content/plugins/relevanssi/lib/utils.php on line 1039

    The next post with ID 169345 looks normal to me, I don’t notice anything compared to the previous post.

    Plugin Author Mikko Saari

    (@msaari)

    The next post is 169343, because Relevanssi indexes in descending order.

    180 seconds is a long time for the process… indexing 50-60 posts shouldn’t take that long. Since there are no shortcodes or custom fields involved, it’s hard to say what’s taking so long. Are there any other plugins that might be involved in this?

    Thread Starter nikolausii

    (@nikolausii)

    Descending, sure, as you had written, sorry.

    Ok, post 169343 is the problem. The content has over 5.500.000 characters.
    I deleted the post and restarted the index, now it runs much further than usual and still runs.

    Can you maybe tell me off the top of your head where the maximum characters for a post is?
    The post could not be accessed on the wordpress site either. I checked the content, there is no error within the text, it will probably just be the length.

    Plugin Author Mikko Saari

    (@msaari)

    The hard limit is 4.2 billion characters (including all the HTML markup), so you’re not even close to that. But I assume you’ll run into problems much faster than that.

    It’s quite likely a post that big will cause problems.

Viewing 6 replies - 1 through 6 (of 6 total)
  • The topic ‘Indexing stucks at same count’ is closed to new replies.