Gert,

New information:

I tried using the "updateIndex fromPid" and got the following error:

Connection error (is Solr running at http://localhost:8080/solr/update ?): java.io.IOException: Server returned HTTP response code: 400 for URL: http://localhost:8080/solr/update

I entered "demo:5" in the "Pid" search field.

From what context does gsearch try to access http://localhost:8080/solr/update?

Solr is running on localhost, but I'm working remotely and the browser from which I'm using the REST interface is not.

This is the only thing that shows up in the tomcat logs after running this command:

Dec 2, 2010 2:59:37 PM org.apache.solr.core.SolrCore execute
INFO: [] webapp=/solr path=/update params={} status=500 QTime=5

Are there any step-by-step instructions for configuring GSearch available? The documentation is very spare. I followed the existing instructions to the letter. Can you see anything in my setup process that would cause this problem?

Everything I did step-by-step is laid out here:

http://pastebin.com/KkXGDg0Z

My edits to configvalues.xml may be where the problem arose. The instructions in this file just direct one to "Set the property values for your environment." I did that to the best of my ability, but perhaps I missed something? After editing this file, which I saved outside the tomcat server, as directed, I ran "ant -f configvalues.xml configOnWebServer". Besides copying configBasic/updater/ to config/updater, is there anything else that need to be done to configure GSearch to use Solr?

For your convenience, I've copied the configvalues.xml changes here:

<?xml version="1.0" encoding="UTF-8"?>
<!-- $Id: build.xml 6534 2008-01-30 16:22:28Z gertsp $ --><project name="FgsConfig" default="configOnWebServer" basedir=".">
...
<property name="soap.deploy.hostport" value="banyan:8080" />
<property name="soap.deploy.user" value="***************" />
<property name="soap.deploy.pass" value="***************" />
<target name="configDefault"
description="select the default config, by setting these three properties">
<property name="default.config.path" location="${solr.config.path}" />
<property name="default.config.prefix" value="${solr.config.prefix}" />
<property name="default.index.1" value="${solr.index.1}" />
...
</target>
...
<target name="configDemoOnSolr"
                description="set values for configDemoOnSolr">
...
<property name="solr.index.1.indexbase" value="http://banyan:8080/solr"; />
<property name="solr.index.1.indexdir" value="/home/admin/solr/data/index" />
...
<property name="solr.repos.1.fedorasoap" value="http://banyan:8080"; />
<property name="solr.repos.1.fedorauser" value="*************" />
<property name="solr.repos.1.fedorapass" value="*************" />
...
</target>


</project>

Thanks for your time.

Cheers,

Christopher Curry
Assistant Technical Librarian / Assistant IT Officer

American Philosophical Society
105 South Fifth Street
Philadelphia, PA 19106-3386
Tel. (215) 599-4299

ccu...@amphilsoc.org <mailto:ccu...@amphilsoc.org>

Main Library number: (215)440-3400
APS website: http://www.amphilsoc.org



On 12/02/2010 09:01 AM, Gert Schmeltz Pedersen wrote:
I notice

org.apache.solr.common.SolrException: ERROR:unknown field 'PID'

Which indicates that your schema.xml file does not mention the PID field. In 
configDemoOnSolr/index/DemoOnSolr/conf/schema.xml the PID field is specified, 
please do the same in your schema.xml . That may solve some or all of the 
problems.

Regards, Gert
------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Fedora-commons-users mailing list
Fedora-commons-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/fedora-commons-users

Reply via email to