Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ERROR : sendPeersProposal - Promise is rejected #258

Open
Jayaramdas2002 opened this issue Aug 22, 2018 · 3 comments
Open

ERROR : sendPeersProposal - Promise is rejected #258

Jayaramdas2002 opened this issue Aug 22, 2018 · 3 comments

Comments

@Jayaramdas2002
Copy link

gulp marbles_local gives me the following error

error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: 14 UNAVAILABLE: Connect Failed
at new createStatusError (/root/marbles/node_modules/grpc/src/client.js:64:15)
at /root/marbles/node_modules/grpc/src/client.js:583:15
warn: [fcw] warning - query resp is not json, might be okay: string Error: 14 UNAVAILABLE: Connect Failed

Kindly suggest how to solve this issue.

@dshuffma-ibm
Copy link
Contributor

#200

@Jayaramdas2002
Copy link
Author

I have followed the process but node query.js generated following error

Store path:/root/marbles/fabric-samples/fabcar/hfc-key-store
Successfully loaded user1 from persistence
Failed to query successfully :: Error: "targets" parameter not specified and no peers are set on this Channel instance or specfied for this channel in the network

@dshuffma-ibm
Copy link
Contributor

Missing targets could happen for a few reasons. First to check is if you actually have peers defined in your config JSON file. Second is if the fcw code was able to find these peers and parse them. Third is if the SDK is getting the peer target fields or not. There should be more logs to help you figure out where to start.

this file might be a good place to start looking: https://github.com/IBM-Blockchain/marbles/blob/master/utils/marbles_cc_lib.js you need to see the logs to figure out which function is being called. then look at the peer_urls fields and see if its blank. track it backwards to figure out what is going on.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants