New to Greengrass and have a few general queries related to it.

Have faced the following 3 issues in the past few weeks

-->> My colleague stated that his deployment fails with error stating “Group definition is not valid”? I couldn't find anything in the GG troubleshooting document about the error.

-->> I updated my group definition and added Lambdas to it but I don’t see that reflected on the device. Do the changes take place upon rebooting device ? is the deployment failed ? or the change made on cloud but never made to the device.

-->> In the beginning I couldn't find error logs in my Green grass local machine, neither CloudWatch

Thanks Community, looking forward to exploring GG.

Joan.

vidishataws
vor 2 Jahren
Hi Joan, It looks like you are using Greengrass v1. Greengrass v1 is in maintenance mode. We highly recommend using greengrass v2 Thanks, Vidish
AWS-User-8637566
vor 2 Jahren
Hello @Vidishataws yes we are on track to upgrade to V2 but can you please let us know the cause of the following issues mentioned above ?
vidishataws
vor 2 Jahren
Hi Joan, Can you share the following details:

Greengrass version

Steps your colleague followed to get "Group definition is not valid".

Did you make a deployment with the lambdas?

You should be able to find logs in the <greengrass-root>/var/log directory. If you wish to upload logs to cloudwatch, you will have to configure the logger as shown here

Themen

Internet der Dinge (IoT)

Relevanter Inhalt

Wie behebe ich den Fehler „The specified queue does not exist or you do not have access to it.“, wenn ich einen AWS Glue Job ausführe, um Nachrichten an Amazon SQS in einer anderen Region zu senden?
AWS OFFICIALAktualisiert vor 3 Jahren
Wie behebe ich den Fehler „Unable to validate the following destination configurations“ in AWS CloudFormation?
AWS OFFICIALAktualisiert vor 2 Jahren
Wie vermeide ich den Fehler „Unable to validate the following destination configurations“ bei Lambda-Ereignisbenachrichtigungen in CloudFormation?
AWS OFFICIALAktualisiert vor 3 Jahren
Wie behebe ich den Fehler „The new key policy will not allow you to update the key policy in the future“, wenn ich versuche, mit AWS CloudFormation einen AWS-KMS-Schlüssel zu erstellen?
AWS OFFICIALAktualisiert vor einem Jahr