Reputation: 349
I am trying to start Solr via Bash shell running on Ubuntu (on a Windows machine).
I am in the /solr directory and run bin/solr start
but I get the following error message:
```*** [WARN] *** Your open file limit is currently 1024.
It should be set to 65000 to avoid operational disruption.
If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in your profile or solr.in.sh
*** [WARN] *** Your Max Processes Limit is currently 7823.
It should be set to 65000 to avoid operational disruption.
If you no longer wish to see this warning, set SOLR_ULIMIT_CHECKS to false in your profile or solr.in.sh
Waiting up to 180 seconds to see Solr running on port 8983 [/] Still not seeing Solr listening on 8983 after 180 seconds!
2018-12-06 15:29:46.634 INFO (main) [ ] o.a.s.m.r.SolrJmxReporter JMX monitoring for 'solr.jetty' (registry 'solr.jetty') enabled at server: com.sun.jmx.mbeanserver.JmxMBeanServer@453da22c
2018-12-06 15:29:46.670 INFO (main) [ ] o.a.s.c.CorePropertiesLocator Found 0 core definitions underneath /mnt/d/Solr/solr-7.5.0/server/solr
2018-12-06 15:29:46.711 INFO (main) [ ] o.e.j.s.h.ContextHandler Started o.e.j.w.WebAppContext@4e50c791{/solr,file:///mnt/d/Solr/solr-7.5.0/server/solr-webapp/webapp/,AVAILABLE}{/mnt/d/Solr/solr-7.5.0/server/solr-webapp/webapp}
2018-12-06 15:29:46.714 WARN (main) [ ] o.e.j.x.XmlConfiguration
java.security.PrivilegedActionException: null
at java.security.AccessController.doPrivileged(Native Method) ~[?:1.8.0_191]
at org.eclipse.jetty.xml.XmlConfiguration.main(XmlConfiguration.java:1511) [jetty-xml-9.4.11.v20180605.jar:9.4.11.v20180605]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.8.0_191]
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) ~[?:1.8.0_191]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_191]
at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_191]
at org.eclipse.jetty.start.Main.invokeMain(Main.java:220) [start.jar:9.4.11.v20180605]
at org.eclipse.jetty.start.Main.start(Main.java:486) [start.jar:9.4.11.v20180605]
at org.eclipse.jetty.start.Main.main(Main.java:77) [start.jar:9.4.11.v20180605]
Caused by: java.net.BindException: Address already in use
at sun.nio.ch.Net.bind0(Native Method) ~[?:1.8.0_191]
at sun.nio.ch.Net.bind(Net.java:433) ~[?:1.8.0_191]
at sun.nio.ch.Net.bind(Net.java:425) ~[?:1.8.0_191]
at sun.nio.ch.ServerSocketChannelImpl.bind(ServerSocketChannelImpl.java:223) ~[?:1.8.0_191]
at sun.nio.ch.ServerSocketAdaptor.bind(ServerSocketAdaptor.java:74) ~[?:1.8.0_191]
at org.eclipse.jetty.server.ServerConnector.openAcceptChannel(ServerConnector.java:331) ~[jetty-server-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.server.ServerConnector.open(ServerConnector.java:299) ~[jetty-server-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.server.AbstractNetworkConnector.doStart(AbstractNetworkConnector.java:80) ~[jetty-server-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.server.ServerConnector.doStart(ServerConnector.java:235) ~[jetty-server-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[jetty-util-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.server.Server.doStart(Server.java:398) ~[jetty-server-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.util.component.AbstractLifeCycle.start(AbstractLifeCycle.java:68) ~[jetty-util-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1572) ~[jetty-xml-9.4.11.v20180605.jar:9.4.11.v20180605]
at org.eclipse.jetty.xml.XmlConfiguration$1.run(XmlConfiguration.java:1512) ~[jetty-xml-9.4.11.v20180605.jar:9.4.11.v20180605]
... 9 more```
What causes this issue and how can it be resolved?
Upvotes: 2
Views: 1200
Reputation: 2382
Caused by: java.net.BindException: Address already in use
means that there is already something listening on the port 8983. Might be a different Solr instance you already started, or something completely different.
You can use sudo lsof -i :8983
to find the process that is causing it.
Upvotes: 5