First, if you've upgraded from an older version, make sure that your atom-worker config file looks like this now:
We made some changes in the 2.5 release that should make the job scheduler more persistent, but issues can still happen.
Next, there is a command-line task we can use to clear all jobs from the queue. Since it looks like you don't have any other jobs running than this one, let's try that. The following should be run from AtoM's root installation directory - if you have followed our recommended installation instructions, this is typically /usr/share/nginx/atom. Run the following:
Let's also clear the application cache and restart php-fpm for good measure:
- Clear the application cache: php symfony cc
- Restart PHP-FPM:
- With PHP 7.0: sudo systemctl restart php7.0-fpm
- With PHP 7.2: sudo systemctl restart php7.2-fpm
We can make sure the job scheduler is running as expected with the following:
- sudo systemctl status atom-worker
If it's not running, try:
- sudo systemctl restart atom-worker
And then check the status again to make sure it's running as expected. Now we can try the import again.
Finally, note that while the job scheduler shouldn't die as much, if you restart it more than 3 times in 24 hours, then you will need to manually reset the restart limit. You can do this like so:
- sudo systemctl reset-failed atom-worker
- sudo systemctl start atom-worker
This is why it is important to check the status after running the various tasks - your restart attempts might trigger the limit, in which case you will need to run the reset-failed task before starting the worker again.