Re: Unable to enable SSL with self-sign certs

TRUS_STORE is a typo (I used what was already there, I just uncommented it). I'm on a different network so I have to type everything by hand. I was hoping I put enough already , but ugh... probably more typos to come. Here it is: 2018-09-10 19:17:15.311 WARN: (main) [ ] o.e.j.u.c.AbstractLifeCy

Unable to enable SSL with self-sign certs

I installed solr 5.4.1 and java 1.8 on its own linux server and used the install_solr_service.sh file to install and setup solr. At this point I was able to start the process and access the dashboard from a browser. After shutting down solr I then attempted to enable SSL via the Enabling SSL

Keystore and Password is displayed in Dashboard

I have configured my solr instance to use ssl and it's working as expected. However, the keystore password is being displayed when I access the Solr Dashboard. Is there a way to hide this? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Permission Denied when trying to connect to Solr running on a different server

It was a config issue. The SELinux on the machine was not allowing apache to talk to port 8983. I verified this by temporarily turning off the enforcement (setenforce 0). Once I did this I was able to run search as expected. I then turned the enforcement back on (setenforce 1) and added a rule for

Re: Permission Denied when trying to connect to Solr running on a different server

I'm using the sunspot gem. It can't be rails because I was able to index from the app server and I can search from the rails console. Its just when I'm trying to access from the web application. And yes, my logs are in /var/solr/logs and there was nothing new there. It did write something when I

Permission Denied when trying to connect to Solr running on a different server

I have a ruby on rails application that used solr and the sunspot rails gem for search. For development I just run solr locally and that's been working fine. But I'm trying to set up a stand-alone solr server for production. So I installed it on its own server and created the core for my site. I up

Re: Recent configuration change to our site causes frequent index corruption

That makes sense, the ulimit was too small and I've updated it. I'm just curious why are there still so many 503 errors being generated (Error - Rsolr::Error::Http - 503 Service Unavailable - retrying ...) Is it related to all the "Error opening new searcher. exceeded limit of maxWarmingSearcher

Recent configuration change to our site causes frequent index corruption

I have Rails 5 application that uses solr to index and search our site. The sunspot gem is used to integrate ruby and sunspot. It's a relatively small site (no more 100,000 records) and has moderate usage (except for the googlebot). Until recently we regularly received 503 errors; reloading the p

Recent configuration change to our site causes frequent index corruption

I have Rails 5 application that uses solr to index and search our site. The sunspot gem is used to integrate ruby and sunspot. It's a relatively small site (no more 100,000 records) and has moderate usage (except for the googlebot). Until recently we regularly received 503 errors; reloading the p