[Netarchivesuite-users] Oldjobs directory growing too big

aponb at gmx.at aponb at gmx.at
Sat May 2 11:43:35 CEST 2009


>
> On rare occations (e.g. when a crawler looses the JMS-connection during a crawl) the 3rd step of the above will fail (mostly also the 2nd) because the harvester-application cannot send either upload-messages or the job-finished message. In these cases the jobs will not get reported as finished in the database and will remain in status STARTED. The only way to fix this currently is to copy the entire contents of a job-directory back to a harvester-instance (not running other jobs) and restart that instance. That will make the harvester find the old data and do whats nessecary to do actually all three steps if required.
>
> All this error handling is currently a manual process - but luckily is does not happen that often
>
>   

How can I restart that certain instance?
I put the content back into that harvester Dir and then I resubmitted
the failed job out of the User interface. That is probably not the right
way, because it created a new Job which was started a new crawl.
Thanks for your help!
a.






More information about the NetarchiveSuite-users mailing list