Start and Stop Bitnobi - myantandco/RA-BitnobiPilotJuly2020 GitHub Wiki
- Open a terminal session on the server and run the
docker ps -a
command to verify that the Bitnobi containers are still running. This should display something like:
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
79f6966450b6 ra-bitnobi-frontend "/docker-entrypoint.…" 16 hours ago Up 16 hours 0.0.0.0:3001->80/tcp ra-bitnobi-frontend
7835dac51ae6 ra-bitnobi-backend "docker-entrypoint.s…" 16 hours ago Up 16 hours 0.0.0.0:8001->8000/tcp ra-bitnobi-backend
363af28c5646 bitnobi-mongodb "docker-entrypoint.s…" 16 hours ago Up 16 hours 27017/tcp ra-bitnobi-mongodb
fa6c5f736c45 bitnobi-jupyter "/bin/bash -c 'nohup…" 16 hours ago Up 16 hours 0.0.0.0:8889->8888/tcp ra-bitnobi-jupyter
- In the terminal session on your Bitnobi server navigate to the main bitnobi directory (e.g. ~/ra-bitnobi).
- run the
./stop.sh
command - After a few seconds type
docker ps -a
to list the docker containers. This should no longer show any bitnobi containers.
- Open a terminal session on the server and run the
docker ps -a
command to verify that none of the Bitnobi containers are running. - In the terminal session on your Bitnobi server navigate to the main bitnobi directory (e.g. ~/ra-bitnobi).
- run the
./start.sh
command - After a few seconds type
docker ps -a
to list the docker containers. This should display something like:
$ docker ps -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
83d5fdcf7033 ra-bitnobi-frontend "/docker-entrypoint.…" 5 seconds ago Up 3 seconds 0.0.0.0:3001->80/tcp ra-bitnobi-frontend
1f95c666eb68 ra-bitnobi-backend "docker-entrypoint.s…" 8 seconds ago Up 5 seconds 0.0.0.0:8001->8000/tcp ra-bitnobi-backend
3662313a9743 bitnobi-jupyter "/bin/bash -c 'nohup…" 9 seconds ago Up 6 seconds 0.0.0.0:8889->8888/tcp ra-bitnobi-jupyter
0f9d935bd69d bitnobi-mongodb "docker-entrypoint.s…" 9 seconds ago Up 7 seconds 27017/tcp ra-bitnobi-mongodb
- Go to the logs directory and examine the server-out.log file. The start of this file should show a successful connection to MongoDB, and a vault status of "sealed":false. There should be no error messages.