you were right about the ports. I could now resolve the Connection
refused error, thanks! Populating the index now gives me a
"org.apache.solr.common.SolrException: Forbidden". I assume this is
equivalent to the 403 now, right? I've checked that localhost is
127.0.0.1, and also that 127.0.0.1 and my local IP are in the allowed
On 09/19/2013 10:24 AM, helix84 wrote:
> On Thu, Sep 19, 2013 at 9:59 AM, Joachim Bingel <bingel@...> wrote:
>> I followed the steps to enable Solr, but still I can neither populate the
>> index nor open the Solr page. By the way, the wiki  says enabling Solr is
>> not even necessary for my purpose of outside metadata access.
> True (I wrote that), even though at least adding discovery to event
> consumers is desirable.
>> On my local
>> test DSpace instance, this wasn't necessary, either.
>> I still get the "Connection refused" error as reported in my previous mail
>> if I try to populate the index... Any ideas what I can do about this?
> Connection refused and 403 are two different errors that require
> different approaches.
> Connection refused means either a firewall is blocking the connection
> or nothing is listening on that port. Check which port you specified
> in solr.search.server (e.g. 8080) and check using "sudo netstat -tulpn
> | grep 8080" whether a java process is indeed listening on that port.
> I'd expect HTTP 403 response only in case the localhost restriction is
> in effect and you're accessing it from another machine.
> If you put "localhost" into solr.search.server, make sure your
> /etc/hosts file translates localhost to 127.0.0.1 and if you're using
> RemoteAddrValve that 127.0.0.1 is among the allowed addresses. The
> localhost restriction doesn't work with IPv6.
> Compulsory reading: DSpace Mailing List Etiquette
Institut für Deutsche Sprache, Zentrale Forschung
R5, 6-13, 68161 Mannheim
+49 - (0)621-1581-456 | http://www.ids-mannheim.de