Is reinstall really the only way to fix hostname change?


#1

I set up one-node Couchbase cluster with AWS public DNS. I didn’t realize that the hostname will change if I restart the instance, and now my Couchbase does not start anymore, throwing following error:

[ns_server:error,2015-12-16T08:23:37.309Z,nonode@nohost:dist_manager<0.130.0>:dist_manager:init:178]Configured address <my hostname> seems to be invalid. Will refuse to start for safety reasons.

I thought this would be simple to fix, Couchbase being mature database and everything, but I can’t find a way to fix my server without reinstalling it. Is there seriously no other way to fix such a simple thing???


#2

Update the files with correct ip and restart Couchbase it should work.

In version 3.x /opt/couchbase/var/lib/couchbase/ip_start
In version 4.x /opt/couchbase/var/lib/couchbase/ip


N1QL not working in the official Couchbase 4.0.0 CE AMI
#3

The following has been reported to solve this problem. With the Couchbase service down do:

% cd /opt/couchbase/var/lib/couches
% sudo rm -f couchbase-server.node ip_start

and then try to restart the Couchbase service:

%/etc/init.d/couchbase-server start


#4

Thanks for the info. As I fortunately didn’t have yet important data at the server, I already decided to perform reinstall.