Roberto Bosshardt
Dan Gillean
If you have followed our recommended installation instructions (and this will work with the Vagrant box), you can check the most recent error log entries with:
- sudo tail -f /var/log/nginx/error.log
Feel free to share any related error message you find here if you're not sure how to proceed, and we will try to offer suggestions on next steps.
I suspect that the job scheduler may need to be configured, or restarted. The details for installing the job scheduler (Gearman) can be found here:
In the vagrant box, the job scheduler should come pre-configured, so you shouldn't need to manually install it. However, it's possible that the job scheduler simply needs a restart. You will know this is the case if you look in the error logs and see a message like, "No Gearman worker available that can handle the job."
To restart the atom-worker, see:
sudo systemctl restart atom-worker
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
Then run the restart command again if the previous attempts didn't work.
If none of these suggestions help to resolve the issue, and/or this is not what you find in the error logs, then please let us know what you discover and we can provide further suggestions.
--
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 ica-atom-user...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ica-atom-users/2b37156f-2618-4453-be4b-784432ba0bf6n%40googlegroups.com.