ServeStream | Streaming Media Player for Android | Media library

I believe the issue is within the GetRecord grpc client implementation, specifically with the context implementation you are using.

By using context.WithTimeout and by calling the defer cancelFunc() in the same method, you are basically shutting down the stream before returning from GetRecord method.

If you want to still use the context.WithTimeout implementation, don't use the cancelFunc inside the GetRecord method, but either return the cancelFunc from it, or pass the ctx to GetRecord method.

Looking at the examples that this code is inspired from, could the problem be related to not having the "grpc_ctxtags" interceptor? See https://github.com/grpc-ecosystem/go-grpc-middleware/blob/06f64829ca1f521d41cd6235a7a204a6566fb0dc/logging/logrus/examples_test.go#L31

Here are a few hints: Chaincode container startup has a default timeout of 300s. If chaincode instantiation takes longer than that (e.g. because you're on a very slow network), you'll get a timeout. You can try to extend that timeout by setting CORE_CHAINCODE_STARTUPTIMEOUT as env variable on your peer. To see what is happening during chaincode instantiation, perform a docker ps: you'll see some temporary containers running (based on image fabric-ccenv). Check their logs using docker logs.

Until https://jira.hyperledger.org/browse/FAB-15287 is addressed the workaround for now is to modify the package.json files in the magnetocorp/contract and digibank/contract directories. Look for the entries

The composer network start command is attempting to start a 'chaincode' container for each of the peers, and from error you show, there are 2 of your peers that cannot start these new container.

The error looks like a Docker error - the containers cannot be started on a network bridge called "net_example". I would guess that you have an environment variable defined in one of your docker-compose-xxx.yaml files that defines this variable: CORE_VM_DOCKER_HOSTCONFIG_NETWORKMODE which determines which network bridge the new containers are attached to.

You will need to determine which network bridge our other Fabric containers are using, then set this variable in the .yaml to that bridge.

This previous post has some discussion on multi-host fabric.

Thanks to @R Thatcher for putting me onto the right direction. This was all down to mismatching cards, and was resolved by clearing out everything and starting again.

Specifically, in /fabric-dev-servers:

I also come across this issues recently. After checked some related issues and docs, the temporary solutions for me is restart the peer which you found Failed to invoke chaincode name "qscc" at its log:

I had fix it.

This is because I execute the peer chaincode instantiate operation on another machine and I should execute it on the specified node's machine.

E.g: