Hi Agung Prasetyo W.,

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.  Alternatively you could update the status of the task to "waiting" and will try to do it again.  This has what the import script had done automatically for you here.  If a task is submitted to the indexer which has the Plugin, Action and Parameters, (to generate a unique hash), as an existing task in the event queue, if the existing task is set to waiting, it won't bother to add a duplicate task, if it is set to failed, it should (as it has done here) reset that task to waiting.

It is slightly odd that an import script would prompt the resetting of failed task, as I would expect import to create new eprint records and therefore tasks it would create would have to be unique as the parameters would have to be different from any task already in existence, as the ID of that eprint would have not been used up to now.

I cannot tell you what task "44e3e6296c10c8b5428eb84025508735" is intended to do.  Typically, as the indexer's name suggests, it is indexing metadata for a record, so that you can search for it later.  However, you would need to check the event queue admin page (https://HOSTNAME/cgi/users/home?screen=Listing&dataset=event_queue) to get a better idea.  However, if after resetting to waiting the task successfully completed, it will no longer be listed in the event queue.

Regards

David Newman

On 12/04/2026 18:14, Agung Prasetyo W. wrote:

CAUTION: This e-mail originated outside the University of Southampton.

CAUTION: This e-mail originated outside the University of Southampton.

Hi,

I have just exported 1000 items from the old server and imported them to the new server. But when I run import command, I got this error message:

./bin/import REPOID eprint XML 1000.xml --verbose --user 1

Starting EPrints Repository.
Connecting to DB ... done.
Undefined phrase: eprint_fieldopt_monograph_type_komponen (en) at line 128 in /usr/share/eprints/bin/../perl_lib/EPrints/MetaField/Set.pm
Undefined phrase: eprint_fieldopt_monograph_type_komponen (en) at line 128 in /usr/share/eprints/bin/../perl_lib/EPrints/MetaField/Set.pm
Warning! Invalid XML element: copyright
Warning! Invalid XML element: copyright
Warning! Invalid XML element: copyright
Warning! Invalid XML element: copyright
Warning! Invalid XML element: copyright

[2026-04-12T09:58:11Z] Resetting failed event 44e3e6296c10c8b5428eb84025508735 to waiting.
[2026-04-12T09:58:40Z] Resetting failed event d7715f1fcc490dad04cd6ce6955853ea to waiting.
[2026-04-12T09:59:43Z] Resetting failed event c02bd5cf7003d44702b19ce8b9adb88c to waiting.
[2026-04-12T10:00:27Z] Resetting failed event 8691a9b52d5a5b089846293787d9dcfa to waiting.
[2026-04-12T10:01:12Z] Resetting failed event 6f099edf05e6730d5658f9b0a80c6184 to waiting.
[2026-04-12T10:01:56Z] Resetting failed event 758613a35bbd4908d9f07e135a673c94 to waiting.
[2026-04-12T10:02:12Z] Resetting failed event 6a1fef01ae1e3f91aacd7fe65cee80a9 to waiting.
[2026-04-12T10:02:39Z] Resetting failed event abd67a2ab118c882dd17ebe2b30a7e5b to waiting.

Why so many "Resetting failed event 44e3e6296c10c8b5428eb84025508735 to waiting" error messages in this process ? Does it not affect the import process?

Thank you.

*** Options: https://wiki.eprints.org/w/Eprints-tech_Mailing_List
*** Archive: https://www.eprints.org/tech.php/
*** EPrints community wiki: https://wiki.eprints.org/