AWS GreenGrass connectivity issues - amazon-web-services

greengrass v1.8.1 log
[2019-08-02T03:30:28.743-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:49567->127.0.$
[2019-08-02T03:30:28.743-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:30:39.74-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:30:39.74-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "nVwA", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:30:59.742-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:49845->127.0.$
[2019-08-02T03:30:59.742-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:31:10.741-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:31:10.741-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "BAxL", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:31:30.742-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:39151->127.0.$
[2019-08-02T03:31:30.742-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:31:41.741-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:31:41.741-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "mQbd", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:32:03.742-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:46991->127.0.$
[2019-08-02T03:32:03.742-04:00][WARN]-MQTT[client] Failed to connect to a broker
[2019-08-02T03:32:14.741-04:00][WARN]-MQTT[store] Trying to close memory store, but not open
[2019-08-02T03:32:14.741-04:00][WARN]-MQTT connection attempt failed and will be retried. {"attemptId": "UDaF", "clientId": "YoungsoftIoTGroup_Core", "errorStrin$
[2019-08-02T03:32:41.743-04:00][WARN]-MQTT[client] dial tcp: lookup a1ijl5s1n8kf6a-ats.iot.us-east-1.amazonaws.com on 127.0.0.53:53: read udp 127.0.0.1:56790->127.0.$
My OS is Ubuntu 18.04. I used AWS IoT greengrass v1.8.1.
I followed the README.md in each package to setup up and install step by step. All lambdas were failed to connect AWS greengrass group I created.
This is all was working and all of a sudden encountered this issue.

Related

Random terraform dial tcp: lookup no such host errors

When I run terraform apply, I get random "terraform dial tcp: lookup no such host errors". Sometimes they go away when I run apply again. Here are a some examples:
Post "https://iam.amazonaws.com/": dial tcp: lookup iam.amazonaws.com on [2001:8a0:6f38:7c00::1]:53: no such host
Post "https://firehose.eu-west-1.amazonaws.com/": dial tcp: lookup firehose.eu-west-1.amazonaws.com on [2001:8a0:6f38:7c00::1]:53: no such host
Post "https://events.eu-west-1.amazonaws.com/": dial tcp: lookup events.eu-west-1.amazonaws.com on [2001:8a0:6f38:7c00::1]:53: no such host
I can't find any problem with my network and definitely not a problem looking up names.
I sometimes also get this with terraform destroy

Google Cloud Fusion: Failed to explore connection. Error: "Failed to create connection to database via connection string:

I am trying to set up a connection to a postgres DB from Cloud Fusion. I have what I think is the appropriate JDBC driver. I am going through the Wrangler UI. I keep getting this error message: Failed to explore connection. Error: "Failed to create connection to database via connection string: jdbc:postgresql://XX.XXX.X.XX:PORT/TABLE_NAME and arguments: {user=USERNAME}. Error: SocketTimeoutException: connect timed out."
It appears my password is being sent. Is this a jdbc issues or something else? All help appreciated.
Thanks!

getsockopt: connection refused : Transferring logs from Filebeat to Logstash on other host

I'm trying to transfer logs from Filebeat to Logstash
Both are running on different EC2 instances in the same network.
Apparently the socks5 protocol is used instead of http.
This is my filebeat.yml config file
filebeat.prospectors:
- type: log
paths:
- /camel-logs/app.log
output.logstash:
hosts: ["remote-host:5044"]
proxy_url: socks5://10.0.0.10:5044
filebeat.inputs:
- type: log
paths:
- /camel-logs/app.log
Honestly, I don't really know whether I should use prospectors, inputs, or both here. Neither works for now.
I'm positive that TCP port 5044 between the two hosts is open and accessible, but I don't know if socks5 is even possible over TCP? My knowledge about this stuff is quite limited.
I'm getting this error:
pipeline/output.go:74 Failed to connect: dial tcp 10.0.0.10:5044: getsockopt: connection refused
This could also be interesting:
log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":20,"time":24},"total":{"ticks":40,"time":52,"value":40},"user":{"ticks":20,"time":28}},"info":{"ephemeral_id":"192acef7-0adb-4fbb-adfe-90cade7a5498","uptime":{"ms":30011}},"memstats":{"gc_next":4194304,"memory_alloc":2166616,"memory_total":4100568,"rss":21409792}},"filebeat":{"events":{"active":334,"added":335,"done":1},"harvester":{"open_files":1,"running":1,"started":1}},"libbeat":{"config":{"module":{"running":0}},"output":{"type":"logstash"},"pipeline":{"clients":1,"events":{"active":318,"filtered":17,"published":318,"retry":852,"total":335}}},"registrar":{"states":{"current":1,"update":1},"writes":2},"system":{"cpu":{"cores":2},"load":{"1":3.22,"15":0.47,"5":1.23,"norm":{"1":1.61,"15":0.235,"5":0.615}}}}}}

C++ Send Return SOCKET_ERROR

In my C++ application I'm using network connection (TCP).
when I'm identify a network connection error I'm trying to connect to another interface.
in the reconnection the connect function has passed with no error but on send function it return an SOCKET_ERROR and WSGetLastError return 10054.
do you know what is the meaning of this error and what should I do to resolve it?
10x

10054 means connection reset by peer -- the remote endpoint replied with an RST packet to tell you that the connection isn't open. Reconnect with connect() instead of trying to simply change interfaces on your local end.

10054 (connection reset by peer) after successfull connect() means that the server accepts incoming connection but after that it closes the accepted socket without waiting for incoming information. The only way to resolve this is to check the server application logic.

error while verifying sql server database in coldfusion administrator

Connection verification failed for data source: HEMJOBS03
java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: localhost:90. Reason: Connection refused: connect
The root cause was that: java.sql.SQLNonTransientConnectionException: [Macromedia][SQLServer JDBC Driver]Error establishing socket to host and port: localhost:90. Reason: Connection refused: connect

Looks like datasource configuration uses port 90 to connect, which is closed. See this chunk of your error Error establishing socket to host and port: localhost:90.
So, obvious question: have you changed the connection port manually? If yes, are you sure it is correct port?