Lab 02: Welcomed Alice then rpc error: unknown desc=error executing chaincode: premature exec...

NelsonGlobalGeek

[email protected]:~/fabric-fundamentals/Lab02$ ./09_query_chaincode.sh

query chaincode messages
2018-10-06 23:51:08.845 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-10-06 23:51:08.852 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Query Result:
Fabric Fundamentals

2018-10-06 23:51:09.155 UTC [main] main -> INFO 003 Exiting.....
2018-10-06 23:51:14.256 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-10-06 23:51:14.256 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc
Query Result: Welcome to blockchain Alice!

2018-10-06 23:51:14.593 UTC [main] main -> INFO 003 Exiting.....
2018-10-06 23:51:19.576 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 001 Using default escc
2018-10-06 23:51:19.576 UTC [chaincodeCmd] checkChaincodeCmdParams -> INFO 002 Using default vscc

Error: Error endorsing query: rpc error: code = Unknown desc = error executing chaincode: premature execution - chaincode (messages:1.0.0) is being launched -
Not sure what happened? Is this a timing issue?

I've run Lab 01 and Lab 02 several times making various beginner errors. This prepares me well for my job in the real world and the cert. exam but it is a slow process. Is there a there a cheat sheet or guide for deciphering these messages and troubleshooting?

NelsonGlobalGeek

Redid Lab02 and it worked - not sure why...would still like the cheat sheet for deciphering the messages. Willing to put in some time to help write it if anyone is interested in teaming up

JonathanLevi

Hi @NelsonGlobalGeek - there are several error messages that are common and self-explanatory, while indeed, others may not be that "straight-forward" at first glance.

That error that you have experienced (and successfully resolved) was, indeed, to do with a timeout.

In case you want to dive "deeper" into this particular topic, you can play with the CORE_CHAINCODE_EXECUTETIMEOUT setting in the core.yaml file and see that if you change this number to a higher value the nodes will be more "forgiving" and will allow longer sessions without throwing out the premature execution error that you had above.