Could not listen: eaddrnotavail

[blacksu...@gmail.com]

I'm deploying couchbase-server-community-4.1.1 on google compute engine.While configuringhostname with the external IP,it fails with the following message:Could not listen: eaddrnotavail.How can I solve this problem?

[Sergey Avseyev]

Could you check if the interface with the external IP is accessible on the node? And post output as Aliaksey asked in this post https://groups.google.com/d/msg/couchbase/BOUBMBrybVk/npHvNzv3rTwJ? 

--
Sergey Avseyev

2016-11-14 12:07 GMT+03:00 <blacksu...@gmail.com>:

I'm deploying couchbase-server-community-4.1.1 on google compute engine.While configuringhostname with the external IP,it fails with the following message:Could not listen: eaddrnotavail.How can I solve this problem?

--
You received this message because you are subscribed to the Google Groups "Couchbase" group.
To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[blacksu...@gmail.com]

I configured it from UI with http://externalIP:8091.And if I configured the hostname with 127.0.0.1,the server can be started,and the REST API such as http://externalIP:8093/query/service can be use.

The ifconfig output is as follow,no external IP found here but only internal IP

eth0      Link encap:Ethernet  HWaddr 42:01:0a:f0:00:02  
          inet addr:10.240.0.2  Bcast:10.240.0.2  Mask:255.255.255.255
          UP BROADCAST RUNNING MULTICAST  MTU:1460  Metric:1
          RX packets:458460542 errors:0 dropped:0 overruns:0 frame:0
          TX packets:356003390 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:85932715556 (80.0 GiB)  TX bytes:49969373781 (46.5 GiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:87749684 errors:0 dropped:0 overruns:0 frame:0
          TX packets:87749684 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:15486377907 (14.4 GiB)  TX bytes:15486377907 (14.4 GiB)

On Monday, November 14, 2016 at 5:15:23 PM UTC+8, Sergey Avseyev wrote:

Could you check if the interface with the external IP is accessible on the node? And post output as Aliaksey asked in this post https://groups.google.com/d/msg/couchbase/BOUBMBrybVk/npHvNzv3rTwJ? 

--
Sergey Avseyev

2016-11-14 12:07 GMT+03:00 <blacksu...@gmail.com>:

I'm deploying couchbase-server-community-4.1.1 on google compute engine.While configuringhostname with the external IP,it fails with the following message:Could not listen: eaddrnotavail.How can I solve this problem?

--
You received this message because you are subscribed to the Google Groups "Couchbase" group.

To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+...@googlegroups.com.

[Sergey Avseyev]

You could setup DNS names for your nodes and use them during initialization, and on the node itself make that DNS name to be resolved into private IP address (e.g. in /etc/hosts).

This gives your setup, where all configuration will use DNS names instead of IP addresses, and the clients will pick up external IP address from DNS provider, and nodes will use private interface. If nodes of the cluster in the same private network you could also let them resolve DNS names into private IPs 

--
Sergey Avseyev

To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+unsubscribe@googlegroups.com.

[blacksu...@gmail.com]

Is there any other way to solve this problem?I don't have a domain name,and I don't want to pay for it just for a test.

[Sergey Avseyev]

you could deploy both clients and servers into the same network and use private addresses

--
Sergey Avseyev

To unsubscribe from this group and stop receiving emails from it, send an email to couchbase+unsubscribe@googlegroups.com.

[blacksu...@gmail.com]

Thanks for your advice.My data source and cb server are not in the same network.I followed your advice and solved the problem with virtual dns setting in my code.