[Dspace-tech] Create index error

[Hilton Gibson]

Hi All

Help appreciated. I get the following after deleting indexes and then
trying to create them again.
The script I run is attached. This used to work. We recently upgraded to
Ubuntu 10.04 and DSpace 1.6.2, but this script ran successfully after
the upgrades.
The problem has only occurred during the last week or so. I suspect that
something trying to be indexed is throwing the error, some metadata
field content.
Am I right ?
>>>>
Creating new indexes... Please wait.
Exception: read past EOF
java.io.IOException: read past EOF
at
org.apache.lucene.store.BufferedIndexInput.refill(BufferedIndexInput.java:146)
at
org.apache.lucene.store.BufferedIndexInput.readByte(BufferedIndexInput.java:38)
at org.apache.lucene.store.IndexInput.readInt(IndexInput.java:66)
at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:207)
at
org.apache.lucene.index.IndexFileDeleter.<init>(IndexFileDeleter.java:168)
at org.apache.lucene.index.IndexWriter.init(IndexWriter.java:722)
at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:452)
at org.dspace.search.DSIndexer.openIndex(DSIndexer.java:781)
at org.dspace.search.DSIndexer.createIndex(DSIndexer.java:425)
at org.dspace.search.DSIndexer.main(DSIndexer.java:539)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:616)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:212)
>>>>

Thanks in advance.

hg

--
Hilton Gibson
Systems Administrator
JS Gericke Library
Room 1053
Stellenbosch University
Private Bag X5036
Stellenbosch
7599
South Africa

Tel: +27 21 808 4100 | Cell: +27 84 646 4758

[Hilton Gibson]

[Smith, Ina <ismith@sun.ac.za>]

Dear all

 

We experience major difficulties re-indexing our content on DSpace 1.6.2 (http://scholar.sun.ac.za). When using the Basic Search and Advanced Search, nothing is retrieved. Any advise out there?

 

We get the following after deleting indexes and then trying to create them again.

The script we run is attached. This used to work. We recently upgraded to Ubuntu 10.04 and DSpace 1.6.2, but this script ran successfully after the upgrades.

The problem has only occurred during the last week or so. We suspect that something trying to be indexed is throwing the error, some metadata field content.

Are we right?

 

Many thanks in advance

 

Kind regards

Ina

 

Ina Smith

E-Research Repository Manager | Library and Information Service | University of Stellenbosch | Private Bag X5036, 7599 | South Africa

http://scholar.sun.ac.za | E-mail: ism...@sun.ac.za | Tel:  +27 21 808 9139 | Skype: smith.ina | Office hours: Mo-Fr: 08h00-16h30

E-Navorsingsbewaarplekbestuurder | Biblioteek- en Inligtingsdiens | Universiteit van Stellenbosch | Privaatsak X5036, 7599 | Suid-Afrika

http://scholar.sun.ac.za  | E-pos: ism...@sun.ac.za | Tel:  +27 21 808 9139 | Skype: smith.ina | Kantoorure: Mo-Fr: 08h00-16h30

[Peter Dietz]

Hi Hilton,

I'm not sure what happened, however based on a thread I was reading, I suspect that one of the lucene index files have become corrupt. This is fine, since you're deleting it, and trying to create a new one. More information would be needed 

Since your having issues, instead of running your entire rebuild process, try just isolating to the script inside of it that is causing this issue.

It looks like it errors out during this step though:

# Create new index tables
echo "Creating new indexes... Please wait."
/home/dspace/bin/dspace index-init

You could try to manually delete the contents of the lucene search index which is the step before that: rm -Rf /home/dspace/search/*

And you can get more detailed output from the index-init step if you turn verbose mode on, which is generally useful for providing more insight as to how far the process is able to complete.

So then just end up running: /home/dspace/bin/dspace index-init -v

And if it errors out, you can send a few lines before the stacktrace.

--
Peter Dietz
Systems Developer/Engineer
Ohio State University Libraries