Details
-
Bug
-
Resolution: Fixed
-
Major
-
None
-
2.0
-
None
-
Security Level: Public
-
None
Description
According to this page: http://www.couchbase.com/docs/couchbase-manual-2.0/couchbase-getting-started-upgrade-individual.html
The upgrade process should be an rpm U, but that doesn't work when going from 1.8>2.0:
rpm -U couchbase-server-community_x86_64_2.0.0-beta.rpm
Stopping couchbase-server ...
Stopping couchbase-serverNOTE: shutdown failed
Upgrading couchbase-server ...
/opt/couchbase/bin/install/cbupgrade -c /opt/couchbase/var/lib/couchbase/config -a yes
Traceback (most recent call last):
File "/opt/couchbase/bin/install/cbupgrade", line 11, in ?
import sqlite3
ImportError: No module named sqlite3
Starting couchbase-server[ OK ]
You have successfully installed Couchbase Server.
Please browse to http://fcddeva01: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: 11211, 11210, 11209, 4369,
8091 and from 21100 to 21299.
By using this software you agree to the End User License Agreement.
See /opt/couchbase/LICENSE.txt.
Stopping couchbase-serverNOTE: shutdown failed {badrpc,nodedown}
--------------------------------------
I was under the impression that we were not supporting an in-place upgrade from 1.8 to 2.0, this upgrade scenario needs to be addressed and called out specifically as it will be frequently referred to and used by our existing customers.