Tools, FAQ, Tutorials:
Watch Chaincode Container Log
How to watch the log file of chaincode Container Log?
✍: FYIcenter.com
You can follow this tutorial to watch the log file of a chaincode container:
1. Set up new terminal on the hosting system to follow the log file of the chaincode container linked to "peer0.org1":
$ docker ps --all | grep dev-peer0.org1 cc7aeb60bb85 dev-peer0.org1.example.com-mycc-2.0-04da... $ docker logs --tail 10 -f cc7aeb60bb85 ex02 Invoke Query Response:{"Name":"a","Amount":"80"} ex02 Invoke Query Response:{"Name":"b","Amount":"220"}
2. Set up another terminal on the hosting system to follow the log file of the chaincode container linked to "peer0.org2":
$ docker ps --all | grep dev-peer0.org2 5e2d37a1099f dev-peer0.org2.example.com-mycc-2.0-03c5... $ docker logs --tail 10 -f 5e2d37a1099f ex02 Invoke Aval = 90, Bval = 210 ex02 Invoke Aval = 80, Bval = 220
3. Query the chaincode instance from peer0.org1:
$ docker exec -it cli bash bash-4.4# echo $CORE_PEER_ADDRESS peer0.org1.example.com:7051 bash-4.4# peer chaincode query -C mychannel -n mycc -c '{"Args":["query","a"]}' 80
Only 1 message comes out from the chaincode container linked to peer0.org1.
ex02 Invoke Query Response:{"Name":"a","Amount":"80"}
No message comes out from the chaincode container linked to peer0.org2.
Query chaincode property only runs on the chaincode container linked to the peer who receives the query.
⇒ Invoke Operation on Chaincode Container
⇐ Peer Containers Not Joined to Channel
2020-06-08, 1207🔥, 0💬
Popular Posts:
What is EPUB 3.0 Metadata "dcterms:modified" property? EPUB 3.0 Metadata "dcterms:modified" is a req...
FYIcenter JSON Validator and Formatter is an online tool that checks for syntax errors of JSON text ...
Where to find tutorials on RSS specifications? I want to learn it to describe my API services. Here ...
How to extend json.JSONEncoder class? I want to encode other Python data types to JSON. If you encod...
How to read Atom validation errors at w3.org? If your Atom feed has errors, the Atom validator at w3...