Hi Patrick (and all),

Just a mention that we discovered this issue after the release of 2.8.0 and 
added this to the release notes:

added July 30, 2020: Due the addition of background jobs to the index in this 
release, plugins that create background jobs will cause an indexing loop if 
they are disabled. While the vast majority of users will not encounter this, it 
is most likely to be encountered if users have run the language cleanup plugins 
released in conjunction with 2.6.0. The workaround for now is to reenable the 
plugin (or keep it enabled if the job is run in 2.8.0). The plugin itself 
should not be re-run. This issue will be corrected in a future release.

You can either delete the jobs as Blake suggests or reenable the plugin. We 
expect to have this issue corrected in the next release.

Apologies for the inconvenience,
Christine

Christine Di Bella
ArchivesSpace Program Manager
christine.dibe...@lyrasis.org<mailto:christine.dibe...@lyrasis.org>
800.999.8558 x2905
678-235-2905


[ASpaceOrgHomeMedium]



From: archivesspace_users_group-boun...@lyralists.lyrasis.org 
<archivesspace_users_group-boun...@lyralists.lyrasis.org> On Behalf Of 
Galligan, Patrick
Sent: Tuesday, August 25, 2020 9:43 AM
To: Archivesspace Users Group <archivesspace_users_group@lyralists.lyrasis.org>
Subject: Re: [Archivesspace_Users_Group] Jobs indexing error

Blake,

Yeah, I’m guessing that the `asck` plugin we installed to check data a year ago 
makes those jobs invalid if the plugin isn’t installed.

Which is annoying.

Thanks for the help!

From: 
<archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Blake Carver 
<blake.car...@lyrasis.org<mailto:blake.car...@lyrasis.org>>
Reply-To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Date: Tuesday, August 25, 2020 at 9:31 AM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Jobs indexing error

***External*** This email originated from outside of the organization. Do not 
click links or open attachments unless you recognize the sender and know the 
content is safe.***


 You could just get rid of the aspace_check_job jobs. (back up the DB just in 
case)

select * job where job_blob like '%aspace_check_job%';

Then:

delete FROM job where job_blob like '%aspace_check_job%';



________________________________
From: 
archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>
 
<archivesspace_users_group-boun...@lyralists.lyrasis.org<mailto:archivesspace_users_group-boun...@lyralists.lyrasis.org>>
 on behalf of Galligan, Patrick 
<pgalli...@rockarch.org<mailto:pgalli...@rockarch.org>>
Sent: Tuesday, August 25, 2020 9:05 AM
To: Archivesspace Users Group 
<archivesspace_users_group@lyralists.lyrasis.org<mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: [Archivesspace_Users_Group] Jobs indexing error


Hi all,



Posting here in the off chance someone has run into this before. We’re testing 
out AS version 2.8, coming from 2.6.0 and running into a weird issue.



Indexing works fine until we get to the job records section of indexing, and 
then we run into an unhandled exception ultimately stops indexing from 
finishing, and it just starts up again at resource records after finishing the 
jobs.



I’ve attached the relevant section of our log.



Any ideas on how to fix this? I could just delete all of our job records from 
the table, but that seems like a bad solution to this issue.



Thanks,

Patrick Galligan

He/Him

Digital Archivist

Rockefeller Archive Center
_______________________________________________
Archivesspace_Users_Group mailing list
Archivesspace_Users_Group@lyralists.lyrasis.org
http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group

Reply via email to