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.
Related
Using the AWS IoT Device SDK from GitHub, I'm testing from my local machine using the basic_discovery.py script I can see that it returns the IP address and port from my Raspberry PI running as a Greengrass device, however, I see that I'm getting invalid return codes from the subsequent request when it is attempting to connect with the PI device. The error messages I am getting are as follows:
Trying core arn:aws:iot:us-east-1:111111111111:thing/GreengrassPI at host 192.168.1.176 port 8883
[ERROR] [2022-07-20T20:42:02Z] [00007000017de000] [mqtt-client] - id=0x7fd8b24b4b60: invalid connect return code 4, disconnecting
[ERROR] [2022-07-20T20:42:02Z] [00007000017de000] [tls-handler] - id=0x7fd89242aba0: error reported during SSLRead. OSStatus code -9805
Connection failed with exception AWS_ERROR_MQTT_PROTOCOL_ERROR: Protocol error occurred.
All connection attempts failed
[ERROR] [2022-07-20T20:42:02Z] [0000000116728e00] [mqtt-client] - id=0x7fd8b24b4b60: Connection is not open, and may not be closed
Any suggestions as to what to check? I did not see anything on this in the troubleshooting guide.
[SOLVED] So what I found was that the device name I was using in the test script was not listed in the client device associations for the Greengrass core device. Adding the association resolved the problem. For anyone else that runs into something similar refer to this for information on associating devices. In summary what happened is that the script was able to look up the Greengrass core device but when it attempted to send an MQTT message to it, the Greengrass core device refused it because the device was not associated to it.
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:
Setup
We are using K6 tool for Load testing our API.
Locally scripts work perfectly fine with virtual users up to 50
problem statement
While running the same script in Azure devops using K6 task and virtual user 15 for duration 60s most of the request (almost 90%) is failing because of timeout and following is the error :
level=warning msg="Request Failed" error="Get "https://xxxxx": dial tcp xxxx: 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."
Not sure
a) What is causing the timeout?
b) What are the other options?
PS: Api is behind Api Management Service in Azure and load test works locally fine even on 10 times higher load
we are getting ORA-12570: Network Session: Unexpected packet read error from our webapi written in .Net core 2.2. The API is hosted in Alpine Docker OS 3.11 in GCP using kubernetes. We are using Oracle.ManagedDataAccess.Core version 2.19.60.
The intrenal error message we get is
Oracle.ManagedDataAccess.Client.OracleException (0x80004005): ORA-12570: Network Session: Unexpected packet read error ---> OracleInternal.Network.NetworkException (0x80004005): ORA-12570: Network Session: Unexpected packet read error ---> System.Net.Sockets.SocketException (110): Operation timed out.
Per the website http://www.dba-oracle.com/t_ora_12570_tns_packet_reader_failure.htm, ORA-12570 occur due to listener configuration. IS that true? Also Let us know how if tracing works in linux for ODP.Net core.
Thanks
This is a generic error; it is not necessarily related to the Oracle Listener. The key here is "System.Net.Sockets.SocketException (110): Operation timed out." This could be a lot of things; you really need to do Oracle Net tracing to determine what's going on. Could be that your client can't see the network at all, or that network latency or packet routing are not what they should be, or several other things.
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.