Local device cannot connect to Greengrass Core
zhangzz0413 opened this issue · 6 comments
Running the greengrade local auth demo cannot connect to the greengrade core. The logs of the greengrass core are continuously printed in a loop:
2023-04-20T11:43:38.636Z [INFO] (nioEventLoopGroup-7-23) io.moquette.broker.metrics.MQTTMessageLogger: Channel Inactive. {}
2023-04-20T11:43:41.511Z [INFO] (nioEventLoopGroup-7-24) io.moquette.broker.MoquetteIdleTimeoutHandler: Firing channel inactive event. MqttClientId = null.. {}
The SDK demo keeps printing error:
[ERROR] [Transport_OpenSSL_Sockets] [openssl_posix.c:302] SSL_ connect failed to perform TLS handshake.
[ERROR] [Transport_OpenSSL_Sockets] [openssl_posix.c:721] Failed to establish a TLS connection.
[ERROR] [DEMO] [greengrass_demo_local_auth.c:370] Connection to the broker failed, all attempts exhausted.
[ERROR] [DEMO] [greengrass_demo_local_auth.c:906] Failed to connect to MQTT broker 10.0.78.18.
My steps are as follows:
- Created a thing on the IoTCore and download the certificate and private key: Device_Certificate.crt, Device.key.
- Set up core devices and deploy components on them:
aws.greengrass.clientdevices.Auth
aws.greengrass.clientdevices.mqtt.Moquette
aws.greengrass.clientdevices.mqtt.Bridge
aws.greengrass.clientdevices.IPDetector - Configure cloud discovery and used greengrass_auth_conf.json to set auth component, and set the correct 'certificateAuthority'.
- Create the costomerCA on greengrass core:
openssl genrsa -out ca.key 2048
openssl req -x509 -new -nodes -key ca.key -sha256 -days 1826 -out ca.crt - Running demo:
cmake -S . -Bbuild -DGREENGRASS_ADDRESS="10.0.78.18"
-DROOT_CA_CERT_PATH="/home/zzz/cert/ca.crt"
-DCLIENT_CERT_PATH="/home/zzz/cert/Device_Certificate.crt"
-DCLIENT_PRIVATE_KEY_PATH="/home/zzz/cert/Device.key"
-DTHING_NAME="test_gg_sub_thing"
cmake -S . -Bbuild && cd build && make greengrass_demo_local_auth
Hi, we are looking into this issue. Thanks for your patience.
Hi @zhangzz0413
Just posting update. I'll be looking into the issue, but need some time to get and set up a personal green grass core.
Hi @dachalco
What is the status of this issue? Are there any updates?
Hello @zhangzz0413,
Apologies for the delayed response, unfortunately dave is no longer able to work on the ticket. I'll be taking over this ticket and will provide updates as soon as possible.
Hello @zhangzz0413,
I'm trying to reproduce your problem locally. Just to make sure do you have a greengrass nucleus running at a different terminal?
As there was no response I am closing out the issue, please feel free to open again if the problem is not resloved