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!
Cheers,