Details
-
Bug
-
Status: Closed
-
Critical
-
Resolution: Fixed
-
Cheshire-Cat
-
Untriaged
-
Ubuntu 64-bit
-
1
-
Unknown
-
Build Team 2021 Sprint 6, Build Team 2021 Sprint 7
Description
Node init fails on some debian9 and ubuntu18 VMs with this error:
root@deb91-qe:/tmp# /opt/couchbase/bin/couchbase-cli node-init -c localhost -u Administrator -p password;
|
/opt/couchbase/bin/couchbase-cli: 4: cd: can't cd to /opt/couchbase/bin/../lib/python
|
Installing Python 3 - one moment...
|
sh: 0: Can't open /opt/couchbase/bin/../lib/python/cbpy-installer.sh
|
/opt/couchbase/bin/couchbase-cli: 25: exec: /root/Library/Python/couchbase-py/7.0.0-py4/bin/python3: not found
|
root@deb91-qe:/tmp# /opt/couchbase/bin/couchbase-cli node-init -c localhost -u Administrator -p password;
|
ERROR: Unable to connect to host at http://localhost:8091: HTTPConnectionPool(host='localhost', port=8091): Max retries exceeded with url: /nodeInit (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x7fa5621cd828>: Failed to establish a new connection: [Errno 111] Connection refused'
|
These are the install steps:
dpkg --purge couchbase-server; kill -9 `ps -ef |egrep couchbase|cut -f3 -d' '`;
|
rm /var/lib/dpkg/info/couchbase-server.*;
|
rm -rf /opt/couchbase/;
|
apt-get update;
|
cd /tmp;
|
rm -rf *upgrade-from;
|
dpkg -i couchbase-server-enterprise_7.0.0-4756-debian9_amd64.deb
|
sed -i 's/export PATH/export PATH\nexport CBFT_ENV_OPTIONS=bleveMaxResultWindow=10000000/' /opt/couchbase/bin/couchbase-server; grep bleveMaxResultWindow=10000000 /opt/couchbase/bin/couchbase-server > /dev/null && echo 1 || echo 0;
|
/opt/couchbase/bin/couchbase-cli node-init -c localhost -u Administrator -p password;
|
debian9 VM: 172.23.96.143
ubuntu16 VM: 172.23.120.233
Attachments
Issue Links
- mentioned in
-
Page Loading...
Neither am I,
. Per the logs, the problems are caused post uninstall. Just needed to know what has been changed from an informational standpoint.
As requested earlier, need a proper timeline as to what is essentially happening to the config directories through this test and juxtapose it against the server logs to understand what is happening and where the problem lies.