i have opened the port for inboud and out bound rules.
i have installed the service, when i am running i am getting following error:
BindTransportException[Failed to bind to [9300-9400]]; nested: ChannelException[Failed to bind to: /xx.xx.xx.xx:9400]; nested: BindException[Cannot assign requested address: bind];
at org.elasticsearch.transport.netty.NettyTransport.bindToPort(NettyTransport.java:478)
at org.elasticsearch.transport.netty.NettyTransport.bindServerBootstrap(NettyTransport.java:440)
at org.elasticsearch.transport.netty.NettyTransport.doStart(NettyTransport.java:321)
at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:68)
at org.elasticsearch.transport.TransportService.doStart(TransportService.java:182)
at org.elasticsearch.common.component.AbstractLifecycleComponent.start(AbstractLifecycleComponent.java:68)
at org.elasticsearch.node.Node.start(Node.java:278)
at org.elasticsearch.bootstrap.Bootstrap.start(Bootstrap.java:206)
at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:272)
at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:35)
Caused by: org.jboss.netty.channel.ChannelException: Failed to bind to: /40.69.33.112:9400
at org.jboss.netty.bootstrap.ServerBootstrap.bind(ServerBootstrap.java:272)
at org.elasticsearch.transport.netty.NettyTransport$1.onPortNumber(NettyTransport.java:460)
at org.elasticsearch.common.transport.PortsRange.iterate(PortsRange.java:69)
at org.elasticsearch.transport.netty.NettyTransport.bindToPort(NettyTransport.java:456)
... 9 more
any help in this regard appreciated.
one more thing: we are running Solr on the same VM
Signals that an error occurred while attempting to bind a socket to a local address and port. Typically, the port is in use, or the requested local address could not be assigned.
Is it possible that you misconfigured network.host to an IP address that does not exist on any of your network interfaces? Maybe use one of the special values instead of going for an explicit value.
Hi, thanks for reply
No, i have double checked it.. ip is correct and more over Solr search is accessible with the same ip (We have both searches on the same VM.).
The IP address (which is still visible in the stacktrace of your original post) is a public IP and probably not one available on your network interfaces in the VM. To see which ones are available (after you've configured 0.0.0.0) have a look at the bound_addresses that appear in the ES log output.
So that's your answer then (use 10.0.0.4). If that address is dynamically assigned (e.g. when VM is restarted) you can also use one of the special values which allow you for example to bind to an addresses of a specific network interface, for example en0.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.