Cannot connect to ApacheSolr

Hi,
I am also facing the same issue with beta6.It looks like the problem with schema.xml file.

When i run "java -jar start.jar" comand it is giving error.
I attached detailed error message.

Are you using Solr 1.4 (HEAD) or Solr 1.3?

The change to the schema.xml for beta6 from beta5 was to take advantage of the new Solr ISO mapping feature - without changing the class name one ends up getting string out of bounds exceptions and other problems.

We have been using a solr.war built from 2009-02-24 solr trunk.

I just rebuilt solr from their trunk: http://svn.apache.org/repos/asf/lucene/solr/trunk

That also works fine - so please check what Solr version you are using and read the README file.

Actually just checkout r6 version of SolrPhpClient from SVN instead of the package in the downloads list (march 11).

The README.txt needs to be updated (remove the recommendation to download the package from downloads page).

I'm using module from DRUPAL-6 latest as of now(i.e. beta6+), Solr nightly (23rd March), SVN checkout r6 of SolrPhpClient and it's all good on a fresh debian setup.

@Gurpartap Singh - the error above cannot have anything to do with the Solr PHP client - it's an Solr configuration exception when the java app is starting.

Hm, I had this window opened up before anyone had commented(apologies for change in status). So I was addressing the original problem reported by iandit. Not quite sure about the issue in #1 yet.

I am experiencing this same issue - working on beta5 but not on beta6 - so I also reverted back to 5.

And apologizing for being a noob here - a pointer on how to "rebuild solr from their trunk: http://svn.apache.org/repos/asf/lucene/solr/trunk" would be helpful.

If I bring up mysite.com:8983/solr/admin/, is there a link here to tell if this is 1.4 vs 1.3?

Thanks...

The minute I replaced SolrPhpClient with the latest svn checked-out version it started working again!
Go with comment #6 and it will work..

ok, well if the client makes a difference, then there must be 2 separate issues.

To build the Solr example application from its svn just run "ant example".

Ugh - ok, I just looked in at the download. Apparently the release was built *before* r6 was committed, so it's r5 not r6 and that's probably the source of the problem.

Same as #6 above with the March 24 nightly build of Solr... works! That was a huge headache. Another problem you may run into is if you have two instances of solr running, then stop one... it can cause errors.

2 java apps trying to update the same index could indeed be a bad thing.

I'm closing unless we get more info and/or an environment where this happens consistently.

Please see below - I've reopened this.

Seem to be having this problem as well.

Setup:
Java env: jdk-6u13 linux
Tomcat 6.0.18
SolrPhpClient March 11 release
Solr nightly build from: 2009-03-27
ApacheSolr Module: Beta 6

Module Config settings:
Solr Host Name: subdomain.domain.com (fictitious name - same format)
Solr Port: 8080
Solr Path: /solr
# of item to index per cron job: 50
Results Per page: 10
On Failure: Show Error Messages

I have attempted with with the above configuration, as well as a solr multicore instance on a windows platform - both give the same results. Solr is available and using drupal-0.9.2 schema.

One thing to note: When the settings are saved in the apachesolr module it looks like the request is being made because I can see the following in the tomcat request logs: webapp=/solr path=/select params{spellcheck=true&start0&q=solr&json.nl=map&wt=json&rows=0&spellcheck.build=true&version=1.2}
So the problem maybe the recognition of the response in the drupal module?

Did you get the SolrPhpClient via svn checkout or by simple download ?

SolrPhpClient: First I tried the download, then from checkout - r6 as suggested above.

Thanks for the help. It ended up being a problem on our end. Someone fat fingered the /etc/hosts file. Which explains the above issue.
So the above drupal/solr configuration did in fact work.

Just confirming, I have had the same problem and the following combination works (at least on a Tomcat server):

* Beta-6 Version of the module
* Solr 1.4 nightly build (31-3-09) downloaded from one of the mirrors listed on the project page
* The most current version of SolrPHPClient (downloaded from SVN on April 1st,2009)

[fixing title]

I am having the same issue, I have multiple times re-installed modules and still not much of luck. I can see the admin page, but from Drupal - I see the error message that Solr cannot connect to ApacheSolr.

I am having the same issue, I have multiple times re-installed modules and still not much of luck. I can see the admin page, but from Drupal - I see the error message that Solr cannot connect to ApacheSolr.

I have tried the solution proposed on this thread without success. To check out the SolrPhpClient version 6 from svn does not fix the issue so far as I can tell. There has been an update to both Drupal core and to ApacheSolr module since this issue was closed, so I think it may have stopped working in the meantime.

@picardo:

We can try to help with general installation support, but all of the maintainers of this project also have jobs, so unless you want to use Acquia Search, I'm limited in terms of time to help you debug your case.

That being said, try the following and then report back:

1. When you start up solr using the instructions, do you see any error lines in your terminal like SEVERE: Some error followed by a stack trace?

2. When you go to the apachesolr module settings page, what do you see? Does it say your server cannot be contacted?

3. Look in Reports -> Logs and tell me if there are any apachesolr messages.

Hope that helps. In the future, just saying it is broken does not help us fix it. If you provide logs / screenshots, we'll take a stab it.

Best,
Jacob

Solr 1.4 works fine, however I noticed Solr didn't like upgrading form an older version. I had to purge the existing and install 1.4 fresh. That said, I 'm also runing the apollo solr package with debianizes solr into a .deb. Since Apollo only supports stable releases of Solr, I had to check apollo out of svn and build apollo manually with Solr 1.4 before deploying on a server. With that in mind, there were still issues with the mapping-ISOLatin1Accent.txt and elevate.xml not being where Solr was looking for them which I just had to create symlinks too. Thanks pwolanin for you help on that one ;)

Same here. I found a solution and posted at http://drupal.org/node/504726

I wrote a how-to handbook for absolute beginners at http://drupal.org/node/504558

Hi,

I have installed varnish and Apache Solr over it.

The status report says "Cannot connect to ApacheSolr"
so I restart the tomcat6 server (etc/init.d/tomcat6 restart)
Then I refresh the drupal status report page and it says "Apache Solr has connected to the server".
When I refresh the page again, I get back the error that Apache Solr is not able to connect to the server. I am not sure what to do right now.

Any ideas what and where I should for?

Thanks,
nandavanan

What happens if you remove Varnish? If that fixes the problem, then I'm afraid the apachesolr issue queue is not the best place for help with configuring Varnish.

I am in a problem. I have tried everything, I have read every post/comment...I am running Solr in jetty, and the link http://localhost:8983/solr/admin/ shows the proper web page..But my problem still persists, that is when I enable the solr module in drupal it shows Apache Solr: Your site was unable to contact the Apache Solr server.
I have added SolrPhpClient folder and this output Apache Solr PHP Client Library: Correct version "Revision: 22". shows that I have added the right one.

Please tell what all possible reasons may cause this behavior by solr module in drupal.

Thanx

In Apache Solr module settings use 127.0.0.1 in "Solr host name" field

This drove me nuts for weeks, fixed the issue at last, see below:

fsockopen error (13) permission denied 

Summary:

SELinux is preventing the http daemon from connecting to itself or the
relay
ports

Detailed Description:

SELinux has denied the http daemon from connecting to itself or the relay
ports.
An httpd script is trying to make a network connection to an http/ftp
port. If
you did not setup httpd to make network connections, this could signal an
intrusion attempt.

Allowing Access:

If you want httpd to connect to httpd/ftp ports you need to turn on the
httpd_can_network_relay boolean: "setsebool -P httpd_can_network_relay=1"

Fix Command:

setsebool -P httpd_can_network_relay=1

@SangersDrupalDude

what would be its equivalent in windows environment?

Thanks,
Ben