Error While Executing Command - cb --soft_reset about cbtool HOT 16 CLOSED

Interesting... which OS distro/version are you using at the moment? can you confirm that it was not a transient error (e.g., did you try to re-run cb --soft_reset or even cb --hard_reset)?

from cbtool.

I am using ubuntu,
Distributor ID: Ubuntu
Description: Ubuntu 18.04.4 LTS
Release: 18.04
Codename: bionic

I can confirm it is not a transient error. I have run both soft and hard reset and none worked.

from cbtool.

I have just created another VM and tried running it on it and I got a different error.
Cbtool version is "0bd620b7"
Parsing "cloud definitions" file..... "/home/ubuntu/cbtool/lib/auxiliary//../..//configs/ubuntu_cloud_definitions.txt" opened and parsed successfully.

Checking "Object Store".....An Object Store of the kind "Redis" (shared) on node 10.5.5.195, TCP port 6379, database id "0" seems to be running.
Checking "Log Store".....A Log Store of the kind "rsyslog" (private) on node 10.5.5.195, UDP port 5114 seems to be running.
ERROR:root:network_functions.py/Nethashget.nmap nethashget - Unable to connect to TCP port 27017 on host 10.5.5.195: [Errno 111] Connection refused
Checking "Metric Store"..... Unable to detect a shared MongoDB server daemon running. Please try to start one (e.g., /usr/local/bin/mongod -f /etc/mongod.conf --pidfilepath /var/run/mongod.pid)

from cbtool.

ah, this might be an installer bug that we thought we had solved. Try the following (post the output here)

netstat -puntl | grep "6379\|27001"

sudo systemctl restart redis; sudo systemctl restart mongodb

If afterwards, you see MongoDB/Redis listening on the appropriate ports (try again netstat -puntl | grep "6379\|27001"), then you just restart CB.

from cbtool.

After the first run of netstat as root user
ubuntu@vmtest-1:/cbtool$ sudo -s
root@vmtest-1:/cbtool# netstat -puntl | grep "6379|27001"
tcp 0 0 0.0.0.0:6379 0.0.0.0:* LISTEN 26518/redis-server
tcp6 0 0 ::1:6379 :::* LISTEN 26518/redis-server

After I did systemctl for redis and mongodb. This is the result below
tcp 0 0 0.0.0.0:6379 0.0.0.0:* LISTEN 16814/redis-server
tcp6 0 0 ::1:6379 :::* LISTEN 16814/redi

I then did a hard-reset and it has started working.

Things to note, after I sent you the error, I did the following:

• created the db path for mongo db, because it was complaining that it didn't find it.
• I did a restart of mongodb, although it usually stalls at a point, I don't know why.

Based on the above, I don't know if it also helped.

Thank you for the help.

from cbtool.

Please can I ask, is the GUI and API service daemon URL supposed to be accessible? I tried the URL in a web browser and it tells me it can't load the page.

from cbtool.

Yes, the URL is supposed to be accessible... when you started the cb, did you see a pid for the process that implements the URL (it should appear on the startup messages)?

from cbtool.

Yes, I saw the PID, is there something I should do with that? Could it be because we have two networks configured? In the installation of OpenStack, we needed to create both external and internal network. If I try to use the external network address in the private configuration file of cb, cb doesn't run, but if I leave it as IP_AUTO, it runs fine. However, I can see that the IP addresses are those of the internal network.

from cbtool.

Apologies for the long hiatus. Just in case you still didn't solve the problem (and did not gave up CB entirely :-) ) , I wrote a small tutorial on how to debug the GUI on the FAQ (https://github.com/ibmcb/cbtool/wiki/FAQ-U#wiki-uq24). Let me know if it helps.

from cbtool.

from cbtool.

ok, understood. So on /tmp/restart_cb_gui_ubuntu debug, I assume you see no errors, and the code is left running there, right? Next question, when you, on a different terminal, issues a net stat -puntl | grep <PORT NUMBER OF THE GUI> what is the result?

from cbtool.

from cbtool.

from cbtool.

So, ok, the GUI daemon is listening on port 8080 (you can do a ps aux | grep 25222 and confirm it)... Now, when you try to access via browser, you still see the error, I presume... does the (GUI) process crashes while you attempt access?

from cbtool.

By the way, feel free to talk to us on Gitter (https://gitter.im/ibmcb-project/community#)... faster/more agile than exchanging emails :-)

from cbtool.

I have been talking with @aadewojo on Gitter and I believe this particular issue has been solved. Will close it for now (feel free to open it if needed)

from cbtool.