What does the Solr log file say? Often this is the result of Solr being in a weird state due to startup problems.
Best, Erick On Tue, Dec 8, 2015 at 8:43 PM, Debraj Manna <subharaj.ma...@gmail.com> wrote: > . After failed attempt to start solr if I try to start solr again on same > port it says solr is already running. Try running solr on different port. > > Can you let me know if it is possible to increase the timeout? So that I > can observe how does it behave. > On Dec 9, 2015 10:10 AM, "Rahul Ramesh" <rr.ii...@gmail.com> wrote: > >> Hi Debraj, >> I dont think increasing the timeout will help. Are you sure solr/ any other >> program is not running on 8789? Please check the output of lsof -i :8789 . >> >> Regards, >> Rahul >> >> On Tue, Dec 8, 2015 at 11:58 PM, Debraj Manna <subharaj.ma...@gmail.com> >> wrote: >> >> > Can someone help me on this? >> > On Dec 7, 2015 7:55 PM, "D" <subharaj.ma...@gmail.com> wrote: >> > >> > > Hi, >> > > >> > > Many time while starting solr I see the below message and then the solr >> > is >> > > not reachable. >> > > >> > > debraj@boutique3:~/solr5$ sudo bin/solr start -p 8789 >> > > Waiting to see Solr listening on port 8789 [-] Still not seeing Solr >> > listening on 8789 after 30 seconds! >> > > >> > > However when I try to start solr again by trying to execute the same >> > > command. It says that *"solr is already running on port 8789. Try >> using a >> > > different port with -p"* >> > > >> > > I am having two cores in my local set-up. I am guessing this is >> happening >> > > because one of the core is a little big. So solr is timing out while >> > > loading the core. If I take one of the core out of solr then everything >> > > works fine. >> > > >> > > Can some one let me know how can I increase this timeout value from >> > > default 30 seconds? >> > > >> > > I am using Solr 5.2.1 on Debian 7. >> > > >> > > Thanks, >> > > >> > > >> > >>
