- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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.
Hello everyone,
I’m currently using the aws.greengrass.SecureTunneling component, version 1.0.19, and I’ve encountered some connectivity issues. Specifically, I often need to restart the device running AWS Greengrass to re-establish a tunnel connection. If I don't have physical access to the device, my workaround is to deploy a new version that removes the component, followed by another deployment to reinstall it.
I noticed similar issues in previous versions of the SecureTunneling component, but I’m not sure if this is a continuation of those earlier problems or something new in v1.0.19.
Has anyone faced similar problems or found a more streamlined solution? Any insights, suggestions, or recommendations would be greatly appreciated!
Thanks in advance!
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
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.