Hi Manuel,
Interesting. If I recall correctly, the full-width treeview drag and drop triggers a background job, but the sidebar treeview does everything synchronously - so, combined with the 500 errors you mention generating finding aids, I suspect the problem may actually be with the job scheduler / atom-worker configuration. I would recommend checking your webserver error logs for more information, and also checking on the status of the atom-worker. First, make sure you review the setup of the job scheduer, as per this page:
If everything seems okay, let's see if we can get more information about the error(s) specifically. Check the Nginx error logs to see if there is useful error info there:
If you are using Ubuntu 16.04, then you can also check the job scheduler error logs with the following:
- sudo journalctl -f -u atom-worker
You can check the status of the atom-worker and see if it is running with the following:
- Ubuntu 14.04: sudo status atom-worker
- Ubuntu 16.04: sudo systemctl status atom-worker
You can try to restart the atom-worker with the following if it is not running as expected:
- Ubuntu 14.04: sudo restart atom-worker
- Ubuntu 16.04: sudo systemctl restart atom-worker
In the 2.5 release we also have included a more hardy configuration block so the atom-worker is less prone to dying unexpectedly after periods of inactivity. If you have installed AtoM 2.4.1 using Ubuntu 16.04, then I think you should be able to use this new configuration with AtoM 2.4. See it here:
The one variable you may need to change is the ExecStart one - the example block in the documentation linked above assumes you are using PHP 7.2. Make sure you use the correct path if working with PHP 7.0.
Additionally, note the Tip in the docs:
If the worker hits the start rate limit (3 starts in 24h) to be able to start it again after fixing the issue, the failed status has to be cleared:
sudo systemctl reset-failed atom-worker
sudo systemctl start atom-worker
Hope this helps!