Greengrass Secure Tunneling stopped working
I want to remote ssh into my ubuntu edge device using IoT Secure Tunneling. I installed greengrass to my ubuntu edge device and it registered as a core device. Then I deployed the aws.greengrass.SecureTunneling (1.0.16) component to it. I opened a tunnel, logged in with my username and password and successfully ssh'd into my device.
However, as I was using it I was disconnected several times. I would generate new access tokens and reconnect no problem. Until suddenly the Destination connection state started appearing as Disconnected. I can no longer use SecureTunneling into my device.
My edge device is still powered and working, and I can ssh into it via local networking. How can I troubleshoot why it will no longer connect via SecureTunneling?
- Newest
- Most votes
- Most comments
Hey Jason, we received a bug report internally that I think is related to what you have been experiencing here. This is due to an issue where some resources are not being cleaned up when the tunnel handler receives the close tunnel signal. A new version of the component (1.0.17) is being rolled out right now that aims to fix the issue. Please uninstall the previous version and install this new version to see if the issue still persists.
Thanks, Roger Z.
Thank you for your answer! I don't think there's any way to confirm that this was truly my problem, but I'd like to believe it was. Thanks for sharing this information with me.
Hi Jason, you could try to check the log file: https://docs.aws.amazon.com/greengrass/v2/developerguide/secure-tunneling-component.html#secure-tunneling-component-log-file
Thank you for your comment. I've checked the logs but I don't know what to make of this information
/# cat /greengrass/v2/logs/aws.greengrass.SecureTunneling.log 2023-09-22T02:02:54.322Z [INFO] (Copier) aws.greengrass.SecureTunneling: stdout. [INFO ] 2023-09-22 11:02:54.322 [Thread-1] SubscribeResponseHandler - Received new tunnel notification message.. {scriptName=services.aws.greengrass.SecureTunneling.lifecycle.run.script, serviceName=aws.greengrass.SecureTunneling, currentState=RUNNING}There were older logs too but they also contained the same message.
Relevant content
AWS OFFICIALUpdated a year ago- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 3 years ago
- AWS OFFICIALUpdated a year ago
Hi Jason, as Roger suggested I think the issue you saw might be related to the bug we have resolved recently in v1.0.17 of the component. If you still run into this issue again, I would suggest you to raise a support request from this link : https://aws.amazon.com/contact-us/ so that team can establish a more direct communication channel with you and can help resolve the bug faster.