Could not assemble transaction err proposal response was not successful error code 500 msg chaincode registration failed container exited with 0

Question

I'm trying to instantiate the chaincode, but an error happens, and I can not find solutions to it.

ubuntu 18.04
hyperledger fabric 1.4.1
I've followed the document and it succeeded last week. The same code works well on the local system not working on AWS.
Before instantiate, everything went on well including making channels.

packages

"fabric-ca-client": "^1.4.8",

"fabric-client": "^1.4.8",

"fabric-contract-api": "^1.4.5",

"fabric-network": "^1.4.8",

"fabric-shim": "^1.4.5",

peerlogs:

at Function.Module._resolveFilename (module.js:548:15)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 089     at Function.Module._load (module.js:475:25)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 08a     at Module.require (module.js:597:17)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 08b     at require (internal/module.js:11:18)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 08c     at Object.<anonymous> (/usr/local/src/index.js:3:18)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 08d     at Module._compile (module.js:653:30)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 08e     at Object.Module._extensions..js (module.js:664:10)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 08f     at Module.load (module.js:566:32)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 090     at tryModuleLoad (module.js:506:12)
2020-04-09 17:50:30.751 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 091     at Function.Module._load (module.js:498:3) code: 'MODULE_NOT_FOUND' }
2020-04-09 17:50:30.760 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 092 npm ERR! code ELIFECYCLE
2020-04-09 17:50:30.761 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 093 npm ERR! errno 1
2020-04-09 17:50:30.763 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 094 npm ERR! javascript@1.0.0 start: `fabric-chaincode-node start "--peer.address" "peer0.org1.example.com:7052"`
2020-04-09 17:50:30.764 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 095 npm ERR! Exit status 1
2020-04-09 17:50:30.764 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 096 npm ERR!
2020-04-09 17:50:30.765 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 097 npm ERR! Failed at the javascript@1.0.0 start script.
2020-04-09 17:50:30.765 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 098 npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
2020-04-09 17:50:30.770 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 099
2020-04-09 17:50:30.771 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 09a npm ERR! A complete log of this run can be found in:
2020-04-09 17:50:30.771 UTC [peer.chaincode.dev-peer0.org1.example.com-approval-1.0] func2 -> INFO 09b npm ERR!     /root/.npm/_logs/2020-04-09T17_50_30_766Z-debug.log

2020-04-09 17:50:31.123 UTC [endorser] callChaincode -> INFO 09d [mychannel][8c2210d0] Exit chaincode: name:"lscc"  (93085ms)
2020-04-09 17:50:31.123 UTC [endorser] SimulateProposal -> ERRO 09e [mychannel][8c2210d0] failed to invoke chaincode name:"lscc" , error: container exited with 1
github.com/hyperledger/fabric/core/chaincode.(*RuntimeLauncher).Launch.func1
        /opt/gopath/src/github.com/hyperledger/fabric/core/chaincode/runtime_launcher.go:63
runtime.goexi6

Answer 1

Hey, @Nithin,

Can you please post your peer logs, it will be helpful for me to investigate. Because unlikely, maybe it is a port issue.

Or, I would suggest removing the Docker Images on your system and replacing it with 1.4.1 and then using fabric-shim 1.4.1 too for consistency. This might clear the problem, but will certainly be a better place to continue investigations.

Comments

how can I replace the docker images to 1.4.1 and how can I get peer logs, actually I am using Hyperledger Version: 1.4.6

---

Hi, @Nithin,

Regarding your error, would you check once that the instantiation/upgrade proposal has been sent twice to the same target peer?

---

Hi, @Gitika

I got different error while deploying a smart contract, please help me to resolve below error

Error: error endorsing invoke: rpc error: code = Unavailable desc = transport is closing - proposal response: <nil>

---

Hi, @Nithin,

"transport is closing" error is often caused by the server closing the connection. Try to look at the server-side logging and see if there's any transport error there. 

These errors are happening extremely early in the connection. You could try setting grpc.WithWaitForHandshake in your DialOptions and see if anything else shows up in the logs. My guess is the connection was never actually valid. Are you using TLS or WithInsecure?