Lab 4 error during chaincode instantiation
Comments
-
No need to respond. i opened two terminal windows used one to join the peer channel and the other to install and instantiate chaincode. worked.
1 -
Hi! I had experienced the "network startFiles_basic not found" too, and fixed it now, but now another problem occurred.
root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker exec \ -e "CORE_PEER_LOCALMSPID=Org1MSP" \
So, got a 500 error with a different error message. The
docker logs
command shows that "chaincode registration failed".root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker logs peer0.org1.example.com --tail 9 2020-06-06 11:56:20.893 UTC [endorser] callChaincode -> INFO 06d [allarewelcome][2b9f9042] Entry chaincode: name:"lscc" 2020-06-06 11:56:24.636 UTC [endorser] callChaincode -> INFO 06e [allarewelcome][2b9f9042] Exit chaincode: name:"lscc" (3743ms) 2020-06-06 11:56:24.636 UTC [endorser] SimulateProposal -> ERRO 06f [allarewelcome][2b9f9042] failed to invoke chaincode name:"lscc" , error: container exited with 0 github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1 /opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/runtime_launcher.go:63 runtime.goexit /opt/go/src/runtime/asm_amd64.s:1337 chaincode registration failed 2020-06-06 11:56:24.636 UTC [comm.grpc.server] 1 -> INFO 070 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.26.0.7:60744 grpc.code=OK grpc.call_duration=3.744197085s
And, I'm sure that the chaincode is successfully installed.
root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker exec \ -e "CORE_PEER_LOCALMSPID=Org1MSP" \
There are some related information, but proposed solutions didn't help me.
Thanks for any help!
0 -
Let me emphasize the following. The
ccForAll
is NOT yet instantiated.root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker exec \ -e "CORE_PEER_LOCALMSPID=Org1MSP" \
0 -
Try it with adding the policy flag
peer chaincode instantiate -n ccForAll -v 1.0 -o orderer.example.com:7050 -C allarewelcome -c '{"Args":["Mach","50"]}' --policy "AND('Org1.peer', OR ('Org1.member'))"
0 -
@garycris Thanks for a quick response!
Unfortunately the
cli
container returned the same, and also, no change with thedocker logs
command.root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker exec \ -e "CORE_PEER_LOCALMSPID=Org1MSP" \
But, when I restart the docker containers, I noticed that the
ca.example.com
container has been exited with an error.root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker container list --filter status=exited CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES eef3ec0d5586 hyperledger/fabric-ca "sh -c 'fabric-ca-se…" 5 minutes ago Exited (1) 5 minutes ago ca.example.com
root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker logs ca.example.com 2020/06/07 01:34:09 [INFO] Created default configuration file at /etc/hyperledger/fabric-ca-server/fabric-ca-server-config.yaml 2020/06/07 01:34:09 [INFO] Starting server in home directory: /etc/hyperledger/fabric-ca-server 2020/06/07 01:34:09 [INFO] Server Version: 1.4.7 2020/06/07 01:34:09 [INFO] Server Levels: &{Identity:2 Affiliation:1 Certificate:1 Credential:1 RAInfo:1 Nonce:1} Error: Failed to find private key for certificate in '/etc/hyperledger/fabric-ca-server-config/ca.org1.example.com-cert.pem': Could not find matching private key for SKI: Failed getting key for SKI [[213 244 69 206 45 134 216 131 216 249 165 55 165 199 132 150 75 116 204 145 219 54 241 13 131 189 247 53 49 252 203 87]]: Key with SKI d5f445ce2d86d883d8f9a537a5c784964b74cc91db36f10d83bdf73531fccb57 not found in /etc/hyperledger/fabric-ca-server/msp/keystore
I'm not sure if this is related to my problem, but may be it's better to fix this first. I'll work on it.
0 -
The
ca.example.com
container is running correctly now, as I fixed theFABRIC_CA_SERVER_CA_KEYFILE
setting in docker-compose.yml.And, still having the problem with chaincode instantiations.
Seems it was not related.0 -
As a little progress, declaring
CORE_VM_DOCKER_ATTACHSTDOUT=true
in the docker-compose.yml's peer0.org1.example.com section, I can see the following log outputs.root@ip-10-0-0-174:~/Desktop/fabric-samples/startFiles# docker logs peer0.org1.example.com --tail 26 2020-06-07 03:37:01.818 UTC [gossip.election] beLeader -> INFO 03f cda1cd5dfab563dca265f574ef48565d9ec6969ef79c0c470b63c49ab24cfbf0 : Becoming a leader 2020-06-07 03:37:01.818 UTC [gossip.service] func1 -> INFO 040 Elected as a leader, starting delivery service for channel allarewelcome 2020-06-07 03:37:01.819 UTC [deliveryClient] StartDeliverForChannel -> INFO 041 This peer will retrieve blocks from ordering service and disseminate to other peers in the organization for channel allarewelcome 2020-06-07 03:37:01.821 UTC [deliveryClient] RequestBlocks -> INFO 042 Starting deliver with block [1] for channel allarewelcome 2020-06-07 03:37:15.958 UTC [endorser] callChaincode -> INFO 043 [allarewelcome][8c1b8de2] Entry chaincode: name:"lscc" 2020-06-07 03:37:19.561 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 044 Error starting SimpleAsset chaincode: error trying to connect to local peer: context deadline exceeded2020-06-07 03:37:19.561 UTC [shim] userChaincodeStreamGetter -> ERRO 001 context deadline exceeded 2020-06-07 03:37:19.561 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 045 error trying to connect to local peer 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 046 github.com/hyperledger/fabric/core/chaincode/shim.userChaincodeStreamGetter 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 047 /opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/shim/chaincode.go:112 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 048 github.com/hyperledger/fabric/core/chaincode/shim.Start 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 049 /opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/shim/chaincode.go:151 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 04a main.main 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 04b /chaincode/input/src/github.com/sacc/sacc.go:94 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 04c runtime.main 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 04d /opt/go/src/runtime/proc.go:201 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 04e runtime.goexit 2020-06-07 03:37:19.562 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 04f /opt/go/src/runtime/asm_amd64.s:1333 2020-06-07 03:37:19.630 UTC [dockercontroller] func2 -> INFO 050 Container dev-peer0.org1.example.com-ccForAll-1.0 has closed its IO channel 2020-06-07 03:37:19.753 UTC [endorser] callChaincode -> INFO 051 [allarewelcome][8c1b8de2] Exit chaincode: name:"lscc" (3795ms) 2020-06-07 03:37:19.753 UTC [endorser] SimulateProposal -> ERRO 052 [allarewelcome][8c1b8de2] failed to invoke chaincode name:"lscc" , error: container exited with 0 github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1 /opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/runtime_launcher.go:63 runtime.goexit /opt/go/src/runtime/asm_amd64.s:1337 chaincode registration failed 2020-06-07 03:37:19.753 UTC [comm.grpc.server] 1 -> INFO 053 unary call completed grpc.service=protos.Endorser grpc.method=ProcessProposal grpc.peer_address=172.27.0.8:58070 grpc.code=OK grpc.call_duration=3.796037055s
So, the essential error seems to be this.
2020-06-07 03:37:19.561 UTC [peer.chaincode.dev-peer0.org1.example.com-ccForAll-1.0] func2 -> INFO 044 Error starting SimpleAsset chaincode: error trying to connect to local peer: context deadline exceeded2020-06-07 03:37:19.561 UTC [shim] userChaincodeStreamGetter -> ERRO 001 context deadline exceeded
If anyone has experienced the same in context of chaincode development, please give me an advice.
0 -
No need of response. I fixed this by applying the following setting.
CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE=startfiles_basic
For overcoming the "network startFiles_basic not found" error, I applied a solution of using an external network.
This somehow caused the error of chaincode registrations.Sorry for bothering!
1
Categories
- All Categories
- 60 LFX Mentorship
- 113 LFX Mentorship: Linux Kernel
- 618 Linux Foundation IT Professional Programs
- 321 Cloud Engineer IT Professional Program
- 142 Advanced Cloud Engineer IT Professional Program
- 55 DevOps Engineer IT Professional Program
- 68 Cloud Native Developer IT Professional Program
- 6 Express Training Courses
- 6 Express Courses - Discussion Forum
- 2.3K Training Courses
- 19 LFC110 Class Forum - Discontinued
- 9 LFC131 Class Forum
- 31 LFD102 Class Forum
- 176 LFD103 Class Forum
- 22 LFD121 Class Forum
- 2 LFD137 Class Forum
- 61 LFD201 Class Forum
- 2 LFD210 Class Forum
- 1 LFD210-CN Class Forum
- 1 LFD213 Class Forum - Discontinued
- 128 LFD232 Class Forum - Discontinued
- LFD237 Class Forum
- 23 LFD254 Class Forum
- 653 LFD259 Class Forum
- 108 LFD272 Class Forum
- 1 LFD272-JP クラス フォーラム
- 4 LFD273 Class Forum
- 2 LFS145 Class Forum
- 28 LFS200 Class Forum
- 740 LFS201 Class Forum - Discontinued
- 1 LFS201-JP クラス フォーラム
- 12 LFS203 Class Forum
- 92 LFS207 Class Forum
- 301 LFS211 Class Forum
- 54 LFS216 Class Forum
- 47 LFS241 Class Forum
- 41 LFS242 Class Forum
- 37 LFS243 Class Forum
- 12 LFS244 Class Forum
- 41 LFS250 Class Forum
- 1 LFS250-JP クラス フォーラム
- LFS251 Class Forum
- 142 LFS253 Class Forum
- LFS254 Class Forum
- LFS255 Class Forum
- LFS256 Class Forum
- LFS257 Class Forum
- 1.2K LFS258 Class Forum
- 10 LFS258-JP クラス フォーラム
- 106 LFS260 Class Forum
- 145 LFS261 Class Forum
- 39 LFS262 Class Forum
- 83 LFS263 Class Forum - Discontinued
- 15 LFS264 Class Forum - Discontinued
- 11 LFS266 Class Forum - Discontinued
- 20 LFS267 Class Forum
- 18 LFS268 Class Forum
- 26 LFS269 Class Forum
- 204 LFS272 Class Forum
- 1 LFS272-JP クラス フォーラム
- LFS274 Class Forum
- 3 LFS281 Class Forum
- 249 LFW211 Class Forum
- 177 LFW212 Class Forum
- 9 SKF100 Class Forum
- SKF200 Class Forum
- 907 Hardware
- 220 Drivers
- 74 I/O Devices
- 44 Monitors
- 116 Multimedia
- 210 Networking
- 102 Printers & Scanners
- 86 Storage
- 764 Linux Distributions
- 88 Debian
- 66 Fedora
- 15 Linux Mint
- 13 Mageia
- 24 openSUSE
- 143 Red Hat Enterprise
- 33 Slackware
- 13 SUSE Enterprise
- 357 Ubuntu
- 482 Linux System Administration
- 40 Cloud Computing
- 70 Command Line/Scripting
- Github systems admin projects
- 95 Linux Security
- 80 Network Management
- 108 System Management
- 51 Web Management
- 72 Mobile Computing
- 25 Android
- 32 Development
- 1.2K New to Linux
- 1.1K Getting Started with Linux
- 545 Off Topic
- 132 Introductions
- 223 Small Talk
- 22 Study Material
- 831 Programming and Development
- 282 Kernel Development
- 515 Software Development
- 974 Software
- 260 Applications
- 185 Command Line
- 3 Compiling/Installing
- 119 Games
- 318 Installation
- 65 All In Program
- 65 All In Forum
Upcoming Training
-
August 20, 2018
Kubernetes Administration (LFS458)
-
August 20, 2018
Linux System Administration (LFS301)
-
August 27, 2018
Open Source Virtualization (LFS462)
-
August 27, 2018
Linux Kernel Debugging and Security (LFD440)