Closed abwiggins closed 2 years ago
For anyone else barking up this tree --> AWS_ERROR_FILE_INVALID_PATH.
It's probably due to a poorly configured provisioning setup.
I found that my config.yaml file when installing greengrass
was incorrect... a field was not meeting the syntax rules for device attributes and causing it to fail
Hi,
I've been debugging this issue for a while now and can't seem to pin point the cause. I keep getting this error when trying to "connect" using the ipc client.
I am running:
I am able to connect using the certificates on my device in other ways, so I don't believe it's a credentials issue.
Here is my output:
The item that I'm not understanding is here --
service.init: stderr. RuntimeError: 44 (AWS_ERROR_FILE_INVALID_PATH): Invalid file path..
What file path is invalid?I can confirm the NUCLEUS_SOCKET environmental variable is set:
Also, here is my greengrass deployment with its necessary dependencies:
I'm wondering if it is an awsiotsdk & awscrt version issue? This component installation just recently started failing to install.
This is the best output I could get - any debugging tips would be very helpful.
Thanks!