Orderer | 23:09:50.645 UTC addToMap -> DEBU 15d Adding to config map: /Channel/ApplicationĬli | -c, -channelID string In case of a newChain command, the channel ID to create. Orderer | 23:09:50.645 UTC addToMap -> DEBU 15c Adding to config map: /Channel Orderer | 23:09:50.645 UTC addToMap -> DEBU 15b Adding to config map: /Channel/Consortium Orderer | 23:09:50.645 UTC addToMap -> DEBU 15a Adding to config map: /Channel/Application/SampleOrgĬli | Error: Got unexpected status: BAD_REQUEST Orderer | 23:09:50.645 UTC addToMap -> DEBU 159 Adding to config map: /Channel/Application Orderer | 23:09:50.645 UTC addToMap -> DEBU 158 Adding to config map: /Channel Orderer | 23:09:50.645 UTC GetPolicy -> DEBU 157 Returning dummy reject all policy because Writers could not be found in /Application/Writers Orderer | 23:09:50.644 UTC GetPolicy -> DEBU 156 Returning policy Writers for evaluation Orderer | 23:09:50.644 UTC GetPolicy -> DEBU 155 Returning dummy reject all policy because Readers could not be found in /Application/Readers Orderer | 23:09:50.644 UTC GetPolicy -> DEBU 154 Returning policy Readers for evaluation Returning dummy reject all policy because Admins could not be found in /Application/Admins I uncommented the line "command: /bin/bash -c './script.sh'" in the yaml file.ĬONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMESīefcf58f4b59 hyperledger/fabric-ccenv "/bin/bash -c 'sle." 21 seconds ago Up 20 seconds chaincodeģ129dac3e13b hyperledger/fabric-peer "peer node start -." 21 seconds ago Up 20 seconds 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peerĥ6a92979e7cb hyperledger/fabric-orderer "orderer" 22 seconds ago Up 21 seconds 0.0.0.0:7050->7050/tcp ordererīefcf58f4b59 hyperledger/fabric-ccenv "/bin/bash -c 'sle." 2 minutes ago Up 2 minutes chaincodeģ129dac3e13b hyperledger/fabric-peer "peer node start -." 2 minutes ago Up 2 minutes 0.0.0.0:7051->7051/tcp, 0.0.0.0:7053->7053/tcp peerĥ6a92979e7cb hyperledger/fabric-orderer "orderer" 2 minutes ago Up 2 minutes 0.0.0.0:7050->7050/tcp orderer 23:29:26.020 UTC SetupChaincodeLogging -> INFO 002 Chaincode (build level: ) starting up. 23:29:26.020 UTC SetupChaincodeLogging -> INFO 001 Chaincode log level not provided defaulting to: INFO Peer | 23:29:26.026 UTC processStream -> DEBU 1b3 sending state message READYĬORE_PEER_ADDRESS=peer:7051 CORE_CHAINCODE_ID_NAME=mycc:0. Peer | 23:29:26.026 UTC notify -> DEBU 1b2 notifier Txid: does not exist
Peer | 23:29:26.026 UTC enterReadyState -> DEBU 1b1 Entered state ready Peer | 23:29:26.025 UTC HandleMessage -> DEBU 1b0 Fabric side Handling ChaincodeMessage of type: READY in state established
Peer | 23:29:26.025 UTC processStream -> DEBU 1af Move state message READY Peer | 23:29:26.025 UTC notifyDuringStartup -> DEBU 1ae sending READY Peer | 23:29:26.025 UTC notifyDuringStartup -> DEBU 1ad nothing to notify (dev mode ?) Peer | 23:29:26.025 UTC beforeRegisterEvent -> DEBU 1ac Got REGISTER for chaincodeID = name:"mycc:0", sending back REGISTERED Peer | 23:29:26.025 UTC registerHandler -> DEBU 1ab registered handler complete for chaincode mycc:0 Peer | 23:29:26.025 UTC beforeRegisterEvent -> DEBU 1aa Received REGISTER in state created Peer | 23:29:26.025 UTC HandleMessage -> DEBU 1a9 Fabric side Handling ChaincodeMessage of type: REGISTER in state created I was able to complete the steps till Terminal 2 but get an Error in the command "docker exec -it cli bash" for Terminal 3. I am trying to deploy chaincode using the chain code for developers tutorial " ".
0 kommentar(er)
