- Newest
- Most votes
- Most comments
As mentioned by @shagupta-aws the reason while your deployment fails is due to the component failing to correctly execute one of the lifecycle scripts. Check the logs generated by that component to understand the reason. The logs can be found in /greengrass/v2/logs
.
The package folder is empty on the device where the deployment fails because you have selected Rollback
as failure handling policy for the deployment. If you want Greengrass to retain the artifact of the component being deployed, select Don't rollback
in the deployment policies section.
Hi, the log you shared indicates that the component for which this log is, is failing to run. A lifecycle script for the component from its recipe is failing to execute, leading to it getting into broken state and the deployment failing. In order to understand why it fails, you should check the component's log file and observe any logs your component spits out or other information such as what script failed and with what exit code, etc. The other two things you mentioned will need more information in order for us to investigate and help you troubleshoot -
-
why the deployment succeeds when you redeploy from the console without any change. Since we do not have the full greengrass log or component logs here on this post, we cannot identify the cause of these things. Is it possible for you to open a support case and attach all relevant logs and config files, etc to it?
-
Artifact directory being empty at first and being populated later. It depends on when you observe it, initially on installation the directory will be empty and a deployment will download any artifacts for components as applicable so this should be as expected.
Relevant content
- asked 3 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated a year ago
Ahh this was it, because it was rolling back, I didn't get a chance to see what was actually failing. Thank you!