I would recommend that you start by checking your webserver error logs for more information on the nature of the 500 error. If you can share any relevant message that you find, it will likely help us offer further suggestions. See:
In the meantime, I can offer a few general suggestions on possible causes and steps to resolve the issue.
My first guess would be that the job scheduler needs a restart. AtoM uses Gearman to handle some long-running tasks asynchronously in the background. When an archival institution is updated, AtoM will launch a job to check if the edits affect any related descriptions - for example, updating the search index so any changes to the institution's name are properly reflected.
The installation and configuration instructions for setting the job scheduler up can be found here:
Occasionally the atom-worker dies, and needs a restart. If you check the web-server logs and you see an error message that includes something like, "No gearman worker available that can handle the job," then you'll know this is the case.
To restart the atom-worker, see:
Some notes on this:
- You can check the status of the atom-worker at any time with: sudo systemctl status atom-worker
- This is useful to make sure the restart was successful. When the worker dies, AtoM will attempt to automatically restart it - however, to prevent the system from being caught in an endless loop, we added a restart limit - 3 retries every 24 hours. You can reset this fail limit with the following command:
- sudo systemctl reset-failed atom-worker
If this does not resolve the issue, and/or this is not what you find in the error logs, then please let us know what you discover, as well as more information about your installation (AtoM version, Operating system, PHP version, etc) and we can provide further suggestions.