FYI we don't test CentOS or RHEL installations and there are some known issues with PHP 7.4 in AtoM 2.6 (which we've addressed for 2.7) so it is possible there is an installation dependency issue at play, but I'm hoping it's something simpler than this. Let's try to rule out some of the easier solutions first.
My first guess would be that the Elasticsearch service is unavailable. Can you try restarting it?
- sudo systemctl restart elasticsearch
After that, you can try using the search:status task to check on the current status of your ES instance:
If any of the entities are not fully indexed, try manually repopulating the search index, with:
The job scheduler does have its own error log you can check - in Ubuntu the following command can be used; I'm not sure offhand if this will work the same in RHEL:
Another thing to note in the section linked above: if you have followed our recommended installation instructions, the job scheduler has a fail counter to prevent it from being caught in an infinite loop of failing and trying to restart. This fail counter limits restart attempts to 3 times in 24 hours, before you must run the additional command to reset this counter:
- sudo systemctl reset-failed atom-worker
So, if you've attempted to restart the atom-worker without checking its status, it's possible it hasn't actually restarted if the fail counter had reached its limit!
Other standard maintenance tasks you could try that might help if nothing above has:
Ensure the filesystem permissions are properly set:
Rebuild the nested set to ensure that hierarchical relationships are properly stored in the relational database. When an actor is updated, a background job is automatically run to ensure that all related descriptions are updated and properly indexed. This could possibly fail if the nested set is corrupted. You can rebuild it with:
Generate slugs - if one of your records timed out during the save process, then it's possible it was left without a slug in the database, which can cause unexpected failures. Running the following task with no additional option parameters will only generate slugs for records missing them:
Clear the application cache and restart PHP-FPM - ensure you're seeing the latest and not a cached version of a record:
- php symfony cc
- sudo systemctl restart php7.4-fpm
It's always good practice when trying to troubleshoot an error to clear your browser cache as well, or else test in an incognito / private browser window.
Let us know if any of that helps! And if not, please share any relevant information you find in the atom-worker logs.