EPrints Technical Mailing List Archive

See the EPrints wiki for instructions on how to join this mailing list and related information.

Message: #10357

< Previous (by date) | Next (by date) > | < Previous (in thread) | Next (in thread) > | Messages - Most Recent First | Threads - Most Recent First

Re: [EP-tech] Resetting failed event {id} to waiting.

CAUTION: This e-mail originated outside the University of Southampton.
As David says, the command line interface to the indexer is your friend here.

Depending on your setup you may want something like this:

sudo -u eprints ~eprints/bin/indexer stop
sudo -u eprints ~eprints/bin/indexer start --clear  # to forget all the failed jobs
sudo -u eprints ~eprints/bin/indexer start --retry  # to retry all the failed jobs

Bear in mind that if you typically start/stop the indexer from the web interface, you might be used to it running as the Apache user (e.g. www-data or httpd) instead of eprints.

Cheers,
Alex.

On Thu, 2026-04-23 at 21:22 +0700, Agung Prasetyo W. wrote:

I've tried deleting the failed indexed process, but the failed status reappears. There are still 24,000 queue tasks. Is there a way to complete the 24,000 queue tasks or reset them to 0?

If a task has failed in EPrints it will sit in the event queue until something is done about it.  You could delete it through the web interface or by stopping the indexer and starting it from the command line with the --clear option.

-- 
Alex Ball (he/him)
Research Data Librarian (Systems)
University of Bath, Bath BA2 7AY, UK
http://www.bath.ac.uk/library/