Error Elasticsearch error: Elastica\Exception\ClientException

[Khairunnisah Khairunnisah]

I always get this error Elasticsearch error: Elastica\Exception\ClientException whenever I click menu (detail can be seen in attached picture) :

• Archival descriptions
• People and organizations
• Archival institutions
• and so on

This website runs on docker. 

How can I solve this?

[Dan Gillean]

Hi there,

Typically we see this error when either the Elasticsearch service is not running, or else it has not been allocated enough resources, such as memory or disk space (which can force ES into read-only mode). 

Regarding the possibility of a memory error: please note that the AtoM docker-compose environment is NOT intended for use in production as a persistent environment. It's intended use is for local testing and development on a personal computer. If you are trying to run a production-ready web accessible version of AtoM, you will likely need to scale the resources used in all containers at minimum. 

First, let's try restarting the Elasticsearch service to see if it helps. 

You can see all containers and their statuses with the following: 

• docker-compose ps
• See also: https://www.accesstomemory.org/docs/latest/dev-manual/env/compose/#connect-to-atom

To see the name of services listed, run: 

• docker-compose ps --services

To restart the elasticsearch service, try: 

• docker-compose restart elasticsearch

You might also want to try running the AtoM search:status command to see the status of your ES service: 

• docker compose exec atom php symfony search:status
• See: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/elasticsearch/#check-the-status-of-your-elasticsearch-index

You may need to repopulate the search index, and run other AtoM maintenance tasks as well. 

• docker compose exec atom php symfony search:populate
  
• See: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/populate-search-index/

For other basic maintenance tasks such as clearing the application cache, restarting services, rebuilding the nested set, etc. see: 

• Common CLI tasks: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#running-atom-s-most-common-maintenance-tasks
• Restarting services: https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#restarting-services

For other general information about troubleshooting Elasticsearch issues, see: 

• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/troubleshooting/#why-do-i-get-a-searchphaseexecutionexception-when-trying-to-search
  
• https://www.accesstomemory.org/docs/latest/admin-manual/maintenance/elasticsearch
  

Let us know how it goes!

Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
604-527-2056

@accesstomemory

he / him

--
You received this message because you are subscribed to the Google Groups "AtoM Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/d4b0c408-a96d-4d05-85ab-87a458abc0a3n%40googlegroups.com.