docker logs taraxa_compose_node_1 > logs
taraxa_compose_node_1
on every environment. If this doesn't wrok, please check to make sure - use docker ps
to see a list of all your containers and figure out exactly what the name of your container is. docker logs --tail 50000 taraxa_compose_node_1 > logs
logs
file, just send it to the dev team along with your problem report. Thanks! docker image ls --digests
taraxa_compose_node_1
or something extremely similar to it. DIGEST:sha256:
wallet.json
file and delete it. It is typically located here, taraxa-compose/config/wallet.json
find . -name wallet.json
wallet.json
file. docker-compose restart
---- tl;dr ----
section, first line should tell you the node's sync status. STATUS: GOOD. NODE SYNCED AND PARTICIPATING IN CONSENSUS
PARTICIPATING IN CONSENSUS BUT NO NEW FINALIZED BLOCKS
, PBFT STALLED, POSSIBLY PARTITIONED. NODE HAS NOT RESTARTED SYNCING
, or STUCK. NODE HAS NOT RESTARTED SYNCING,
these happen from time to time and not necessarily specific to your node/taraxa-ops-master/taraxa_compose/config/testnet.json
"
db_snapshot_each_n_pbft_block" : 0
./var/lib/docker/volumes/taraxa_compose_data/_data/db/
db
and state_db
. The rest you can just clear out. state_db
and see where it's located. docker-compose.yml
file. Inside you'll see a section called ports
, so for example, you might do something like this on the second node, 10002
port to the actual port of 10003
. So if you want to set up more nodes, the mappings (the 10003
, 77781
etc. ports) will need to be different for each node. docker container ls