You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Older versions of microfab (maybe v0.0.16?) appeared to allow transaction function invocation and chaincode lifecycle using the Fabric peer CLI command without and orderer endpoint being explicitly specified. With current versions of microfab (at least v0.0.19 and v0.0.20), these invocations fail unless the orderer endpoint is explicitly specific in the peer CLI command.
From a LF Distributed Trust Discord discussion:
Hello, hopefully someone can help i am stuck i have been working on the full stack tutorial and everything is correct until when i use the peer command to add and asset: "peer chaincode invoke -C mychannel -n asset-transfer -c '{"Args":["CreateAsset","{"ID":"001", "Color":"Red","Size":52,"Owner":"Fred","AppraisedValue":234234}"]}' --connTimeout 15s". This command is returnin the following error ' Error: error getting broadcast client: orderer client failed to connect to localhost:2006: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:2006: connect: connection refused" '. This is all the return after inserting the command ' 2024-12-06 17:51:43.999 GMT 0001 INFO [chaincodeCmd] InitCmdFactory -> Retrieved channel (mychannel) orderer endpoint: localhost:2006
Error: error getting broadcast client: orderer client failed to connect to localhost:2006: failed to create new connection: connection error: desc = "transport: error while dialing: dial tcp 127.0.0.1:2006: connect: connection refused" '
Could you try adding a -o orderer-api.127-0-0-1.nip.io:8080 option to your peer chaincode invoke command? I have a vague memory that an update to the version of microfab used might require the orderer to be specified explicitly
The client application code should still work just fine. If this is the issue, it would only affect using the Fabric CLI to do invocation
That works perfectly. Thank you
Accommodations were required when updating the microfab version used by fabric-samples and fabric-chaincode-java for this change in behaviour.
The text was updated successfully, but these errors were encountered:
Older versions of microfab (maybe v0.0.16?) appeared to allow transaction function invocation and chaincode lifecycle using the Fabric
peer
CLI command without and orderer endpoint being explicitly specified. With current versions of microfab (at least v0.0.19 and v0.0.20), these invocations fail unless the orderer endpoint is explicitly specific in thepeer
CLI command.From a LF Distributed Trust Discord discussion:
Accommodations were required when updating the microfab version used by fabric-samples and fabric-chaincode-java for this change in behaviour.
The text was updated successfully, but these errors were encountered: