- Newest
- Most votes
- Most comments
Greengrass Nucleus is like any other Greengrass component and the current running Nucleus would download another version only if it differs from the one currently running. This normally happen as you specify the Nucleus component explicitly or implicitly in a deployment, but once updated, it should not be necessary to download it again, even across reboots.
Could you share the content of the greengrass.service
file used to start Greengrass, if you use systemd
to manage the Greengrass daemon, or any other relevant detail about how Greengrass is started. It would also be useful to inspect the greengrass.log
for clues about this behaviour.
Hi, is Nucleus reboot due to a deployment? If you make a new deployment but not pin the Nucleus version, it's possible that Nucleus upgrades to latest version which causing Nucleus to reboot. In this case, it's expected for Nucleus to download the latest version from CloudFront link (as we first install Nucleus) which is ~37MBs.
Reference here
Relevant content
- asked a year ago
- Accepted Answerasked 2 years ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 9 months ago
Thanks Massimiliano, this got me to the answer. The image we are using was using a systemctl command to install Nucleus on initial boot. This command was never disabled, resulting in it re-downloading Nucleus (along with a few other things) every time the device rebooted.