New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(nucleus): issues with init-config flag when installing greengrass #876
Comments
What is the config file which you are using? It must not have setup the thing name and so on. Additionally, the quotes around your template variables seems wrong. Please remove the quotes. |
This is the config generated by ansible in the GreengrassCore directory (which is supplied to the installer using the --init-config flag);
The quotes are removed once ansible evaluates the variables and prints out the config. |
What is in the effective config yaml file under the config directory in the greengrass root directory? Please provide the full log output from the setup Java command. |
This is the full output from the installer:
And the corresponding log:
|
Please remove the quotes and ensure that the config file does exist. It is working for me using
Where t.yaml is
My logs show the line "2021-02-27T00:01:43.469Z [INFO] (main) com.aws.greengrass.config.Configuration: config-loading. Read configuration from a file path. {path=t.yaml}" So you can see that it is reading from the t.yaml file. I see no such line in your logs which tells me that it was not able to find the file at the path that you provided. Either due to the quotes or due to the path not existing. |
I see you thumbed up my last comment; if that works for you, please let us know and close the issue. |
I am trying ur suggestions, I will update the ticket once it works. Thanks for the help :) |
@MikeDombo it works! The actual issue was that my config file had the yml file extension and not yaml. Once I changed it to yaml (I saw in ur example u have the yaml extension), it worked, and I can see the core device registered in the console. It's a bit weird that yml is not supported as an extension. What's even more weird is that I did not see that error when running remotely in ansible, but saw the error when running locally on the edge device. However, that's an ansible issue, and not greengrass. Thanks for the tip! |
OK, I'm glad to hear that worked. I'll add a task in our backlog to recognize yml as well. |
Describe the bug
I am using terraform to create the AWS resources required by greengrass beforehand (The ones outlined in the manual installation page: https://docs.aws.amazon.com/greengrass/v2/developerguide/manual-installation.html).
After that I use ansible to
/greengrass/v2
),~/GreengrassCore/config.yml
)and run the command:
I get a message that:
However, when I check the
effectiveConfig.yaml
file, I see that the thing name, iot end point etc. are allempty. Checking the greengrass logs, I see the warning:
To Reproduce
See above.
Expected behavior
Installation is successful and core device is created in the greengrass console
Actual behavior
Core device is not created
Environment
openjdk version "1.8.0_282"
Additional context
If I use the provision flag, and specify the thing name and other parameters as outlined in the quick install, it does work. But creates a new certificate, and attaches it to the thing. But there are 2 issues with it:
For quick install (which was successful), I see that the greengrass client was successfully created:
So may be there are some other arguments that need to be passed for the manual step to work?
The text was updated successfully, but these errors were encountered: