I dumped out my postgres 93 database and moved it to a new server, copied
over my /assetstore as well
installed postgres94 on the new server along with the pgcrypto extension,
imported my database,
ran through the database migration scripts...no errors...everything looked
fine...background indexing
on the new 6.0 installation proceeded and finally concluded with no
complaints.
Platform: Mac OSX 10.12.4, xmlui interface.
However, I had roughly 8780 items in my system based on the number in the
discovery index when it should have shown 8945; that is; when I hit "View
more" on the recent submissions page, I see on the 6.0 system:
"Now showing items 1-20 of 8790
and on the 5.5 system I migrated from:
"Now showing items 1-20 of 8945"
Looking "under the hood" I see that Postgres shows the same number of items
in the ITEM table for both installs (5.5 and 6.0) If I go back to my 5.5
installation and get the item number for something I see that's missing, I
can do an item search on the 6.x system and the "missing" item is
retrieved. If I then go to the item metadata screen for that item and hit
"update"...it now appears in the "Recently added" display on the system's
home page...and the number of items in the system increments by one (so
that appears to have indexed it).
For some reason the discovery index build is skipping about 155 records.
Looking through my solr log I don't see anything interesting...
Looking in dspace.log I find entries like this while the indexing is
running:
2017-04-21 07:05:19,592 INFO org.dspace.discovery.SolrServiceImpl @ Wrote
Item: 1920/8770 to Index
2017-04-21 07:05:19,612 ERROR org.dspace.discovery.SolrServiceImpl @ No
choices plugin was configured for field "dc_contributor_author".
java.lang.IllegalArgumentException: No choices plugin was configured for
field "dc_contributor_author".
at
org.dspace.content.authority.ChoiceAuthorityServiceImpl.getLabel(ChoiceAuthorityServiceImpl.java:153)
at
org.dspace.content.authority.ChoiceAuthorityServiceImpl.getLabel(ChoiceAuthorityServiceImpl.java:144)
at
org.dspace.discovery.SolrServiceMetadataBrowseIndexingPlugin.additionalIndex(SolrServiceMetadataBrowseIndexingPlugin.java:182)
at
org.dspace.discovery.SolrServiceImpl.buildDocument(SolrServiceImpl.java:1459)
at
org.dspace.discovery.SolrServiceImpl.indexContent(SolrServiceImpl.java:223)
at
org.dspace.discovery.SolrServiceImpl.updateIndex(SolrServiceImpl.java:402)
at org.dspace.discovery.IndexClient.main(IndexClient.java:154)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.dspace.app.launcher.ScriptLauncher.runOneCommand(ScriptLauncher.java:229)
at
org.dspace.app.launcher.ScriptLauncher.main(ScriptLauncher.java:81)
I check and the 1920/8770 record is in the discovery index so I don't know
that that error is telling me anything relevant to my issue...
In another spot in the log, I find this message:
2017-04-21 07:05:22,883 WARN org.dspace.discovery.SolrServiceImpl @ Error
while indexing sort date field, item: 1920/10351 metadata field:
dc.date.issued date value: null
It's only a warning but I find that 1920/10351 is not in my discovery index.
I'll stop my rambling...I have rebuilt the discovery index a few times
(with the -b and -f at different times)...no luck. Did a full extract,
reinstall of dspace, postgres, everything a second time...no change.
Open to any and all theories about what else to check.
-- Wally
Wally Grotophorst
George Mason University
--
You received this message because you are subscribed to the Google Groups
"DSpace Technical Support" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/dspace-tech.
For more options, visit https://groups.google.com/d/optout.
