I got most of the tutorial up and running just fine, i.e subgraph creation, publishing subgraphs to Apollo Studio, and setting up the router.
When I try to run a unified query on the supergraph, however, I get the following error,
2022-11-10T19:20:59.880454Z apollo-router/src/services/subgraph_service.rs:173 ERROR [trace_id=dc031984b0655a46580ce9ac8c7fd6e6] apollo_router::services::subgraph_service: fetch_error="hyper::Error(Connect, ConnectError(\"dns error\", Custom { kind: Uncategorized, error: \"failed to lookup address information: nodename nor servname provided, or not known\" }))"
2022-11-10T19:20:59.880537Z apollo-router/src/plugins/include_subgraph_errors.rs:67 INFO [trace_id=dc031984b0655a46580ce9ac8c7fd6e6] apollo_router::plugins::include_subgraph_errors: redacted subgraph(locations) error
2022-11-10T19:20:59.880566Z apollo-router/src/query_planner/execution.rs:188 ERROR [trace_id=dc031984b0655a46580ce9ac8c7fd6e6] apollo_router::query_planner::execution: Fetch error: HTTP fetch failed from 'locations': HTTP fetch failed from 'redacted': redacted
I have both subgraph servers running and can query these individually via Apollo studio.
Subgraphs are published to Apollo Studio using rover cli
The connection string for the router is configured correctly - as I'm getting the error in the terminal
Following this tutorial - https://www.apollographql.com/tutorials/voyage-part1/referencing-an-entity
Related
I'm currently trying out Elasticsearch. I've already made the first steps and installed it following the official instructions. But in my initial attempts, I get this incomprehensible error message. See this text below:
ÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöü
 Elasticsearch security features have been automatically configured!
 Authentication is enabled and cluster connections are encrypted.
Ôä╣´©Å Password for the elastic user (reset with `bin/elasticsearch-reset-password -u elastic`):
77kydX8WQaI6V5RXnEDB
Ôä╣´©Å HTTP CA certificate SHA-256 fingerprint:
b40aedc367164cf6d0f6a09ea2d6e6b258e41b94bbcd43db8f268238d590d472
Ôä╣´©Å Configure Kibana to use this cluster:
ÔÇó Run Kibana and click the configuration link in the terminal when Kibana starts.
ÔÇó Copy the following enrollment token and paste it into Kibana in your browser (valid for the next 30 minutes):
eyJ2ZXIiOiI4LjUuMyIsImFkciI6WyIxOTIuMTY4LjEuMTc5OjkyMDAiXSwiZmdyIjoiYjQwYWVkYzM2NzE2NGNmNmQwZjZhMDllYTJkNmU2YjI1OGU0MWI5NGJiY2Q0M2RiOGYyNjgyMzhkNTkwZDQ3MiIsImtleSI6IkFNZFBUNFVCenk4T19Mcy1lNmFvOmFoWnBnM1AtU3JDcEdlTXFPLS00M0EifQ==
Ôä╣´©Å Configure other nodes to join this cluster:
ÔÇó On this node:
Ôüâ Create an enrollment token with `bin/elasticsearch-create-enrollment-token -s node`.
Ôüâ Uncomment the transport.host setting at the end of config/elasticsearch.yml.
Ôüâ Restart Elasticsearch.
ÔÇó On other nodes:
Ôüâ Start Elasticsearch with `bin/elasticsearch --enrollment-token <token>`, using the enrollment token that you generated.
ÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöüÔöü
-----------------------------------------------------------------------
and this message, when I try to run the Elasticsearch on port 9200:
[2022-12-26T17:55:47,141][WARN ][o.e.x.s.t.n.SecurityNetty4HttpServerTransport] [DESKTOP-VLBL46H] received plaintext http traffic on an https channel, closing connection Netty4HttpChannel{localAddress=/[0:0:0:0:0:0:0:1]:9200, remoteAddress=/[0:0:0:0:0:0:0:1]:60933}
I am failing with a DNS 14 message when trying to call a lambda function to invoke chaincode on my Amazon Managed Hyperledger Blockchain.
ERROR Failed proposal response. Status code: undefined. Message: 14 UNAVAILABLE: DNS resolution failed. Stack: Error: 14 UNAVAILABLE: DNS resolution failed
at Object.exports.createStatusError (/opt/nodejs/node_modules/grpc/src/common.js:91:15)
at Object.onReceiveStatus (/opt/nodejs/node_modules/grpc/src/client_interceptors.js:1209:28)
at InterceptingListener._callNext (/opt/nodejs/node_modules/grpc/src/client_interceptors.js:568:42)
I believe that it is due to a grpc link used to access the peer node endpoint.
I've tried logging all of the request fields, but it is difficult to figure out which configuration is missing.
Try to perform nslookup against the peer address. If it fails, see whether you have created VPC Endpoint for the Hyperledger Fabric network.
I'm figuring out how I can test my golang project using Bloomrpc. I've turned on the backend server, client server and db server but an error pop up like this on Bloomrpc:
I am new using cloud platform. I trying to deploy a service using go and grpc. I found this tutorial https://github.com/GoogleCloudPlatform/golang-samples/tree/master/endpoints/getting-started-grpc and everything was complete successful until I have to call the service.
In the moment that I use the client to call the service I get this error:
could not greet: rpc error: code = Unavailable desc = all SubConns are in TransientFailure, latest connection error: connection error: desc = "transport: Error while dialing dial tcp 35.199.74.154:80: connectex: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because
connected host has failed to respond.
I would like to know if someone can help me with that problem.
I'm following these instructions using the orgID given by the Watson IoT platform.
I then created the MQ Client in Node-RED using this orgID and
d:orgID:mydevicetype:mydevicedid using arbitrary mydevicetype and mydevicedid.
These are the Node-RED error messages:
"Error: Connection refused: Not authorized"
"Error stopping node: Error: [BaseClient:disconnect] Client is not connected"
I then created a device on the Watson IoT platform using the mydevicetype and mydevicedid and eas provided a token.
I got the same error using use-token-auth as the user and the token as password.
Device log on the Watson IoT platform:
Invalid userID () for device auth:
ClientID='d:orgID:mydevicetype:mydevicdeid',
ClientIP=169.50.40.xxx
Can you try:
url: mqtts://[orgId].messaging.internetofthings.ibmcloud.com
port:8883
username: use-token-auth
password: [the token you got when you created the device]
client id: d:[orgID]:[mydevicetype]:[mydeviceid]
Looks like not much different from what you've tried, perhaps your are not using a secure (mqtts) connection ?
If the client id that you are specifying really is:
d:orgID:mydevicetype:mydevicdeid
then your problem is that you need to specify the actual 6 character orgId, e.g.:
d:abcdef:mydevicetype:mydevicdeid
Give that a go and let us know how you get on.