wri / wri_sites

WRI profile
2 stars 2 forks source link

Platform sites indexing issue #325

Open StudioZut opened 5 days ago

StudioZut commented 5 days ago

We're still having issue with site content (on flagship and other platform sites) not always appearing in site search or sometimes in resource lists.

Example (Brasil): This profile was created, but not appearing in site search or in the staff list: https://www.wribrasil.org.br/equipe/laura-rossler -- I re-index manually 10-16, which fixed it.

Example (Brasil): "we noticed that our events page is also not updating correctly. We posted this (https://www.wribrasil.org.br/eventos/2024/wri-brasil-na-cop-16-biodiversidade) and its not showing on the events page (https://www.wribrasil.org.br/eventos)." -- this also was fixed after re-indexing manually.

Example (Brasil): 2 posts weren't showing up in their library at https://www.wribrasil.org.br/biblioteca : https://www.wribrasil.org.br/noticias/creditos-de-biodiversidade-podem-impulsionar-conservacao-da-natureza and https://www.wribrasil.org.br/noticias/o-que-e-uma-estrategia-climatica-de-longo-prazo -- Maria fixed 10-15 "I ran the queries to disconnect and reconnect to solr and that seems to have done it"

Example (Brasil): they found 2 posts that weren't appearing in past events (also fixed with re-indexing) Image

Dev tasks

mariacha commented 1 day ago

Pantheon caught some logs:

Uncaught PHP Exception Error: "Call to a member function getSearchId() on null" at /code/web/modules/contrib/search_api/search_api.module line 602[17-Oct-2024 04:28:23 UTC]

The search_api module doesn't have any issues open for this, and doesn't have a new release, so there must be something handing the search_api.module a call to getSearchId on a null item in an unexpected way.

Looking at the code, the error would only be thrown in the unlikely circumstance that the $view->getQuery() function didn't return anything.

So I don't think we'll get far down that path.

We had noticed the same issue a few days before, where the logs were returning the error we were seeing when the Solr database was on version 4.2, but it was on version 4.3.5 when I checked. Running through the commands to clear out and re-index eventually started working, but I wasn't convinced that these commands had fixed anything. It felt a lot more like the server was temporarily pointing to an old, bad schema version, and it just fixed itself with some cron run or something.

Perhaps at this point it's worth writing some kind of script to notify us if an error about "DOCS_AND_FREQS_AND_POSITIONS" happens on one of the sites, so we can get a sense of how often this comes up.

mariacha commented 1 day ago

Perhaps this module would help for sending out the notifications: https://www.drupal.org/project/logging_alerts

And/or this one for permanently logging any search notifications: https://www.drupal.org/project/dblog_persistent