Problems with AtoM when restarting the machine

Skip to first unread message

Aug 24, 2022, 2:48:46 AMAug 24
to AtoM Users
Good morning, recently we had to turn off the emergency servers, including the server where we have the AtoM platform installed. When starting the machine it did not load correctly, it gave an Elasticsearch error even though this service had been launched correctly.

What we did was reindex with php symfony search:populate and then clear the php symfony cc cache and restart PHP and the problem was fixed.

We don't know if this happens because the server is not configured correctly. Is there any way that when restarting the machine it is not necessary to reindex everything? Or else an easier way to retrieve AtoM? Thanks in advance and greetings.

Dan Gillean

Aug 25, 2022, 2:29:43 PMAug 25
to ICA-AtoM Users
Hi Isabel, 

Without knowing more about your environment or the particular chain of events that led to the server being turned off, it's difficult to say why this happened. It's possible for example that the server shut off while AtoM was in the middle of an operation to update the search index, requiring a rebuild to resolve the issue after. 

It does not sound likely to me that the Elasticsearch service wasn't running - and if you have followed our recommended installation instructions, we set this up in such a way that the main services that the linux subsystem manages (elasticsearch, mysql, nginx, php-fpm, etc) should restart automatically following a server reboot. See for example: 
The very last part of the above section in the installation docs reads: 

Start the service and configure it to start when the system is booted.

sudo systemctl enable elasticsearch
sudo systemctl start elasticsearch

Additionally, the Elasticsearch service would have to be running for the search:populate command to run without errors, so if that's how you resolved the problem, it means that Elasticsearch was running as a service, but the search index itself may have been corrupted. 

I suspect that this may have been a rare occurrence, and that a full reindex shouldn't be necessary for every restart. Perhaps you can find a way to test this outside of active business hours, ensuring that no one is running any operations in AtoM before performing a server reboot and monitoring the outcome. If you do proceed with this, let us know how it goes!


Dan Gillean, MAS, MLIS
AtoM Program Manager
Artefactual Systems, Inc.
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
To view this discussion on the web visit
Reply all
Reply to author
0 new messages