Hello
We are trying to setup solr to gather statistics and found in the server
log this error:
-
Nov 21, 2012 11:20:37 AM org.apache.solr.common.SolrException log
SEVERE: org.apache.solr.common.SolrException: ERROR:unknown field
'bundleName'
at
Hi Domingo
I assume you did an upgrade.
This is new with DSpace 1.8.2 stats.
See:
https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7.x+to+1.8.x
Look for: Optional Upgrade Step: Fix Broken File Statistics
Cheers
hg
On 21 November 2012 13:50, Domingo Iglesias digles...@ub.edu wrote:
I'm not completely sure, but from your stracktrace it looks like you
may be hitting the localhost restriction (by default, Solr in DSpace
is set up so that you can connect to it only from localhost).
I'm not familiar with WebLogic, but here's how to do that in Tomcat:
I'm running dspace/tomcat behind Nginx as reverse proxy, i've changed also
the solr url into real hostname (not localhost:8080), and i can access SOLR
admin from outside. Do you know how to make SOLR more secure with that
setup ?
2012/11/21 helix84 heli...@centrum.sk
I'm not completely sure,
On Wed, Nov 21, 2012 at 1:08 PM, revskill revskil...@gmail.com wrote:
I'm running dspace/tomcat behind Nginx as reverse proxy, i've changed also
the solr url into real hostname (not localhost:8080), and i can access SOLR
admin from outside. Do you know how to make SOLR more secure with that
Hi Truong
Without knowing which platform you are using.
If it is linux based, then a simple firewall rule will protect port 8080.
For Ubuntu see: http://wiki.lib.sun.ac.za/index.php/SUNScholar/Firewall
On 21 November 2012 14:08, revskill revskil...@gmail.com wrote:
I'm running dspace/tomcat
Hi
Thanks for your responses.
Re-checking the config files we have seen that the following line
field name=bundleName type=string indexed=true stored=true
required=
false multiValued=true /
was missing in [dspace.dir]/solr/statistics/conf/schema.xml
2012/11/21 helix84 heli...@centrum.sk
Not as of yet. Our new build (on Ubuntu Server) seemed to work with no
issues. It may have something to do with how FreeBSD handles requests
to the SOLR webapp from localhost?
We didn't find any sysctl, firewall or TomCat settings that would have
interfered, so we figured it was something with
Hello,
I have deployed SOLR and _seem_ to have configured it correctly, it
responds when visiting http://localhost:8180/solr/ with two links:
SOLR and SOLR Admin. Clicking on the SOLR Admin link returns a 404 HTTP
error. In fact, any URI past /solr/* returns a 404.
This error is also
9 matches
Mail list logo
