By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Greengrass v2 + effectiveConfig.yaml got changed on device reboot

0

We are using Greengrass V2 for one of our IoT project. We have faced one issue on one of our device, where greengrass components were running. We have provision this device with --setup-system-service true . We have faced the issue like this device was rebooted multiple time, and at one particular instance effectiveConfig.yaml file of greengrass/v2/config got blank, like as below.

system: certificateFilePath: "" privateKeyPath: "" rootCaPath: "" rootpath: "" thingName: ""

Could you please explain what could be the reason for the same ?? Moreover, while troubleshoot one thing we have observe, that effectiveConfig.yaml file's timestamp got changed whenever device got restart.

Topics
Internet of Things (IoT)
Tags
AWS IoT GreengrassAWS IoT Core
Language
English
rePost-User-7846458
asked 10 months ago226 views
1 Answer
1

The effectiveConfig file is only updated when Greengrass starts and shuts down. It is not an accurate realtime reflection of the real configuration.

It sounds like you may be experiencing some file corruption, in which case, you absolutely must make sure that you are using the latest versions of Greengrass. Please use Greengrass Nucleus 2.11.0. What version of Greengrass are you currently using?

Cheers,

Michael

AWS
EXPERT
MichaelDombrowski-AWS
answered 10 months ago
profile pictureAWS
EXPERT
Greg_B
reviewed 6 months ago
  • rePost-User-7846458
    10 months ago

    Michael,

    Ok we will update Nucleus with version 2.11..0. Right now, we are using Nucleus 2.7.0.

    So, when greengrass service got restart, it creates the "effectiveConfig.yml". While creating this file, does greengrass reads the values for thingname, thinggroup from "config.tlog" ??

  • MichaelDombrowski-AWS EXPERT
    10 months ago

    2.7.0 is quite old and has known issues. You really need to upgrade to 2.11.0 to get the issues resolved.

    When Greengrass starts, it reads the config from config.tlog and then dumps it into the effectiveConfig to be more easily readable by a human.

  • rePost-User-7846458
    10 months ago

    Thanks for the response Michael. We take this on top priority to update the nucleus with 2.11.0.

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.

Guidelines for Answering Questions

Relevant content