Details
Major Description
This is a bit of an odd one, and I'm not sure that I'm not doing something else incorrect here, but would like a sanity check on that:
1) Install 5.0.1 on a single CentOS 6 node
2) Setup that node by choosing the defaults, create an empty test bucket
3) Upgrade that node to 5.5.1. This is the text from the upgrade:
[root@ip-10-0-91-138 ~]# rpm -U couchbase-server-enterprise-5.5.1-centos6.x86_64.rpm
|
|
|
Stopping couchbase-server
|
[ OK ]
|
|
|
Minimum RAM required : 4 GB
|
System RAM configured : 15.70 GB
|
|
|
Minimum number of processors required : 4 cores
|
Number of processors on the system : 4 cores
|
warning: /opt/couchbase/etc/couchdb/local.ini saved as /opt/couchbase/etc/couchdb/local.ini.rpmsave
|
warning: /opt/couchbase/var/lib/couchbase/config/config.dat saved as /opt/couchbase/var/lib/couchbase/config/config.dat.rpmsave
|
Upgrading couchbase-server ...
|
/opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
|
Automatic mode: running without interactive questions or confirmations.
|
Analysing...
|
Previous config.dat file is /opt/couchbase/var/lib/couchbase/config/config.dat.rpmsave
|
Target node: ns_1@ec2-52-10-30-245.us-west-2.compute.amazonaws.com
|
Done: previous node configuration is empty.
|
Starting couchbase-server
|
[ OK ]
|
|
|
You have successfully installed Couchbase Server.
|
Please browse to http://ip-10-0-91-138:8091/ to configure your server.
|
Please refer to http://couchbase.com for additional resources.
|
|
|
Please note that you have to update your firewall configuration to
|
allow connections to the following ports:
|
4369, 8091 to 8094, 9100 to 9105, 9998, 9999, 11207, 11209 to 11211,
|
11214, 11215, 18091 to 18093, and from 21100 to 21299.
|
|
|
By using this software you agree to the End User License Agreement.
|
See /opt/couchbase/LICENSE.txt.
|
|
|
[root@ip-10-0-91-138 ~]#
|
(Notice the "previous node configuration is empty. message)
Going back to the UI, this node's configuration has been reset.
If, instead of accepting the defaults, I supply a hostname during the initial setup, this doesn't happen and the upgrade goes through successfully.
I think this is either an issue with ns_server not populating the right config data at startup, or the installer isn't properly picking it up during upgrade.
FWIW, this is being done in AWS and I used an external hostname for the node name in the second example if that makes a difference.