org.elasticsearch.transport.BindTransportException: Failed to bind to [9001]


Samebug tips

It might be that there's another process connecting to the same port you're trying to use, try to kill it or change the connection port.


7 months ago
Expert tip

Try changing the port in core-site.xml from 9000 to 9001 as it seems port 9000 doesn't work.


5 months ago
Expert tip

Solutions on the web

Solution icon of stackoverflow
via Stack Overflow by PT_C
, 1 year ago
Failed to bind to [9001]

Solution icon of stackoverflow
via Stack Overflow by Sri
, 1 year ago
Failed to bind to [9001]

Solution icon of stackoverflow
Failed to bind to [9001]

Solution icon of stackoverflow
via Stack Overflow by MattSom
, 7 months ago
Failed to bind to [9001]

Solution icon of github
Failed to bind to [56378]

Solution icon of web
via oschina.net by Unknown author, 1 year ago
Failed to bind to [9300-9400]

Solution icon of web
via digitalocean.com by Unknown author, 1 year ago
Failed to resolve host [null]

Stack trace

org.elasticsearch.transport.BindTransportException: Failed to bind to [9001]
	at org.elasticsearch.transport.netty.NettyTransport.bindServerBootstrap(NettyTransport.java:422)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.transport.netty.NettyTransport.doStart(NettyTransport.java:283)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:85)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.transport.TransportService.doStart(TransportService.java:153)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:85)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.node.internal.InternalNode.start(InternalNode.java:257)[elasticsearch-1.7.2.jar:na]
	at org.sonar.search.SearchServer.start(SearchServer.java:45)[sonar-search-5.4.jar:na]
	at org.sonar.process.ProcessEntryPoint.launch(ProcessEntryPoint.java:81)[sonar-process-5.4.jar:na]
	at org.sonar.search.SearchServer.main(SearchServer.java:79)[sonar-search-5.4.jar:na]
Caused by: org.elasticsearch.common.netty.channel.ChannelException: Failed to bind to: /127.0.0.1:9001
	at org.elasticsearch.common.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.transport.netty.NettyTransport$1.onPortNumber(NettyTransport.java:413)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.transport.PortsRange.iterate(PortsRange.java:58)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.transport.netty.NettyTransport.bindServerBootstrap(NettyTransport.java:409)[elasticsearch-1.7.2.jar:na]
	... 8 more
Caused by: java.net.BindException: Address already in use: bind
	at sun.nio.ch.Net.bind0(Native Method)[na:1.8.0_112]
	at sun.nio.ch.Net.bind(Unknown Source)[na:1.8.0_112]
	at sun.nio.ch.Net.bind(Unknown Source)[na:1.8.0_112]
	at sun.nio.ch.ServerSocketChannelImpl.bind(Unknown Source)[na:1.8.0_112]
	at sun.nio.ch.ServerSocketAdaptor.bind(Unknown Source)[na:1.8.0_112]
	at org.elasticsearch.common.netty.channel.socket.nio.NioServerBoss$RegisterTask.run(NioServerBoss.java:193)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.processTaskQueue(AbstractNioSelector.java:391)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.netty.channel.socket.nio.AbstractNioSelector.run(AbstractNioSelector.java:315)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.netty.channel.socket.nio.NioServerBoss.run(NioServerBoss.java:42)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.netty.util.ThreadRenamingRunnable.run(ThreadRenamingRunnable.java:108)[elasticsearch-1.7.2.jar:na]
	at org.elasticsearch.common.netty.util.internal.DeadLockProofWorker$1.run(DeadLockProofWorker.java:42)[elasticsearch-1.7.2.jar:na]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)[na:1.8.0_112]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)[na:1.8.0_112]
	at java.lang.Thread.run(Unknown Source)[na:1.8.0_112]

Write tip

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

Users with the same issue

Samebug visitor profile picture
Unknown user
2 times, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 1 year ago
Samebug visitor profile picture
Unknown user
Once, 2 years ago
158 more bugmates