Smart contract upgrade timeout on hyperledger fabric

Question

When upgrading a smart contract the following error occurs:

Failed to invoke chaincode name:"lscc", error: timeout expired while starting chaincode couponcontract:8 for transaction

As this is an lscc error could anyone help on how to debug or identify what is causing it to break?

API version:

"dependencies": { "fabric-contract-api": "~1.4.0", "fabric-shim": "~1.4.0" },

Environment: aws t2.micro

I would like to understand why it was downvoted. It is a pertinent question. — Wederson Soares, Mar 12 '20 at 05:08

score 1 · Answer 1 · answered Mar 06 '20 at 13:31

1

Your chaincode is likely taking too long to start / launch. Try increasing CORE_CHAINCODE_EXECUTETIMEOUT. The default is 30s so try increasing to 60s.

answered Mar 06 '20 at 13:31

Gari Singh

11,418
2
18
41

Thanks @gari-singh, I've tried as you mentioned, but found the same error. :( – Wederson Soares Mar 09 '20 at 02:03

score 0 · Accepted Answer · answered Mar 11 '20 at 05:52

I've found the problem. As the hole network was installed in the same t2.micro instance, the process was consuming all the CPU when upgrading a contract. So, it was breaking duo the time elapsed was causing a timeout. I changed it to a t2.Medium(2 cpu) and now it is working like a charm!!

Smart contract upgrade timeout on hyperledger fabric

2 Answers2