Ingest Failed

Project:RUcore SOLR Searching and Indexing
Version:7.4
Component:Code
Category:bug report
Priority:critical
Assigned:pkonin
Status:closed
Description

Ingest failed on System ID 50700:

Ingest Log (System ID = 50700)
Ingesting into fedora ...
Record System ID: 50700

Checking parent collection in presentation module database ... OK.

Checking handle server ... OK.

Getting Fedora PID ... OK - rutgers-lib:200917.

Inserting Fedora PID to structure map ... OK.

Renaming externally archived digital files (if applicable) ... OK.

Adding audit entry ...OK.

Obtaining record xml ... OK.

Ingesting ... OK.
<a href="http://rep-staging.libraries.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:200917" title="http://rep-staging.libraries.rutgers.edu/dlr/showfed.php?pid=rutgers-lib:200917">http://rep-staging.libraries.rutgers.edu/dlr/showfed.php?pid=rutgers-lib...</a>

Sending quicktime files to darwin streaming server (for video only) ... OK.

Indexing Solr/Lucene search engine ...
Error add index to Solr/Lucene: Error with add action for rutgers-lib:200917...

Purged ingested record: rutgers-lib:200917

Comments

#1

Version:7.0» 7.2
Assigned to:Anonymous» triggs

#2

Is this still a problem? Is this the one where there were issues with bad XML characters? or where we suspected that the indexer was being run before the ingest was complete?

#3

Version:7.2» 7.4

Moving to R7.4.

#4

Version:7.4» 7.5

Is this still a problem? I suspect it will happen whenever XML-1 datastreams with illegal characters are generated. I'm not really sure it should be a bug for me. The Solr indexer is behaving normally in catching these and refusing to index them. The problem is somewhere upstream at the point where the XML-1 files are created.

#5

Version:7.5» 7.4
Assigned to:triggs» pkonin

This was originally submitted by pkonin. Reassigning to him to determine if the problem can be replicated or has been reported since we installed R7.0 in March 2013 and R7.1 in May 2013. Please be generous in the comments and update the status and assignment of the issue.

#6

Status:active» closed

I am unable to replicate this error. Changed status to closed.

Back to top