> Brent Ellingson
> Sr. Software Engineer
> BYU Library
> 801-422-6148
>
>
> Date: Mon, 23 Jan 2017 19:54:53 +
> From: "Majewski, Steven Dennis (sdm7g)" <mailto:sd...@eservices.virginia.edu>>
> To: Archivesspace Users Group
>
7g)"
mailto:sd...@eservices.virginia.edu>>
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2
Message-ID:
<1b0ea75c-ee19-492a-b057-fbaefbbfb...@es
ineer
BYU Library
801-422-6148
Date: Mon, 23 Jan 2017 19:54:53 +
From: "Majewski, Steven Dennis (sdm7g)"
mailto:sd...@eservices.virginia.edu>>
To: Archivesspace Users Group
mailto:archivesspace_users_group@lyralists.lyrasis.org>>
Subject: Re: [Archivess
;>> "date_type": "inclusive",
>>>> "label": "creation",
>>>> "jsonmodel_type": "date"
>>>> }
>>>> ],
>>>> "external_documents": [],
t;jsonmodel_type": "sub_container",
> "top_container": {
> "ref": "/repositories/3/top_containers/1573"
> }
> },
> "container": {
> "type_1": "box"
, 2017 11:39 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2
Hi,
It looks like the problem John is seeing with the indexer failing after
upgrading to 1.5.2 is caused by an issue with a record following the container
conversion. I’m following
lf
> Of James Bullen
> Sent: Wednesday, January 11, 2017 6:56 PM
> To: Archivesspace Users Group
> <mailto:archivesspace_users_group@lyralists.lyrasis.org>>
> Subject: Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2
>
>
> Hi John and Steve,
>
Date: Thursday, January 12, 2017 at 1:47 PM
To: Archivesspace Users Group
Subject: Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2
Steve,
You are not alone. We also ran into indexing error when trying to test upgrade
v1.5.1 to v.1.5.2 and see no record found again after the test
Steve,
You are not alone. We also ran into indexing error when trying to test
upgrade v1.5.1 to v.1.5.2 and see no record found again after the test
upgrade.
LYRASIS Support Desk ever helped us in solving a similar indexing
problem (no record found ) which ever drove me mad :) when upgrading
I’m trying to identify the data where it breaks. It looks like it gets the
first 275 archival objects in the first repo indexed. But I haven’t yet figured
out which one that is or seen anything different in the region where it fails.
But I can send you the whole 8MB gzip compressed mysqldump if
: Re: [Archivesspace_Users_Group] Indexer erroring in 1.5.2
Hi John and Steve,
Can either of you send some sample data that surfaces this bug?
Cheers,
James
On Jan 12, 2017, at 8:17 AM, Majewski, Steven Dennis (sdm7g)
mailto:sd...@eservices.virginia.edu>> wrote:
After seeing this mess
Hi John and Steve,
Can either of you send some sample data that surfaces this bug?
Cheers,
James
> On Jan 12, 2017, at 8:17 AM, Majewski, Steven Dennis (sdm7g)
> wrote:
>
>
> After seeing this message, I tried 1.5.2 on my Mac (10.11.6) laptop and I’m
> also seeing the same
>> undefined
After seeing this message, I tried 1.5.2 on my Mac (10.11.6) laptop and I’m
also seeing the same
undefined method `related_records' for nil:NilClass
error, whether or not I do an intervening ( and successful, BTW ) update to
1.5.1.
Reindexing never seems to progress and so browse resources never
Folks,
I am testing archivesspace 1.5.2 on CentOS 6, using a copy of our 1.4.2
production database.
Wondering why it seems like the indexer is taking so long to finish, I am
seeing this in
the archivesspace.out log, which makes me think the indexer is caught in an
endless loop:
Keep seeing the
14 matches
Mail list logo
