Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Hi,
I have an issue with the module search API: when i'm trying to reindex all my contents, the following message pop up :
SearchApiException: Could not index items since important pending server tasks could not be performed. in search_api_index_specific_items() (line 1481 of /homez.800/mywebsite/www/sites/all/modules/search_api/search_api.module).
All my modules and drupal core are up to date. Any idea what's going on ?
Thanks
Ryan
Comments
Comment #1
Dale Baldwin CreditAttribution: Dale Baldwin commentedGot the same issue here as well with all modules and core up to date.
Comment #2
drunken monkeyAre there some (other) log entries with failures from the Search API?
The message means that some operations on the search server previously failed and were added internally as a pending task. Before any new indexing can occur, these tasks have to be executed to avoid leaving the server in a corrupted state. However, it seems that this operation, whatever it is, keeps on failing, thus preventing any indexing from happening.
If you still have this problem (sorry for my late reply, I was on vacation), maybe take a look (apart from the logs) at the
search_api_task
table to see what kind of task is pending and continuously failing.Comment #3
lsolesen CreditAttribution: lsolesen commentedComment #4
Alex-CDE CreditAttribution: Alex-CDE commentedSame problem, work fine if I run CRON manually. But with automatic CRON, I have this message :
SearchApiException while deleting items from server SolR: "0" Status: : php_network_getaddresses: getaddrinfo failed: Name or service not known in SearchApiSolrConnection->checkResponse() (line 541 of /home/xxxx/public_html/sites/all/modules/contrib/search_api_solr/includes/solr_connection.inc).
Comment #5
drunken monkeyThat's not the "same problem", that's an entirely different problem. Please create a new issue for it.
Comment #6
drunken monkeyIncidentally, it seems the original issue creator doesn't have the problem anymore, so closing here.