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

Greengrass v2/ ubuntu wsl / cannot deploy component / Illegal reflective access by com.google.gson.internal.reflect.ReflectionHelper

0

Hi, I'm new to greengrass so I am following the tutorial: https://docs.aws.amazon.com/greengrass/v2/developerguide/defer-component-updates-tutorial.html

In my ubuntu 20.04 (wsl under windows 11), I managed to install all the tools and created a core device and a component. so I see it listed under Greengrass devices > components > My components > com.example.BatteryAwareHelloWorld

When I click "com.example.BatteryAwareHelloWorld" and "Deploy" in the IoT console the deployment process always fails in few seconds without too much info.

In the Nucleus, (wsl ubuntu) I get the following message: WARNING: An illegal reflective access operation has occurred WARNING: Illegal reflective access by com.google.gson.internal.reflect.ReflectionHelper (file:/greengrass/v2/packages/artifacts-unarchived/aws.greengrass.Nucleus/2.12.0/aws.greengrass.nucleus/lib/Greengrass.jar) to constructor java.util.Collections$EmptyList() WARNING: Please consider reporting this to the maintainers of com.google.gson.internal.reflect.ReflectionHelper WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations WARNING: All illegal access operations will be denied in a future release

Can anyone help me with this issue please?

Topics
Internet of Things (IoT)
Tags
AWS IoT CoreAWS IoT Greengrass
Language
English
asked 2 years ago558 views
1 Answer
0
Accepted Answer

Hi. That's only a warning. It's not the cause of your deployment failure. Your component should have a log file at /greengrass/v2/logs/com.example.BatteryAwareHelloWorld.log. Please check that file for more insight into what's gone wrong.

AWS
EXPERT
answered 2 years ago
  • J
    2 years ago

    Hi, Greg. Thank you for the feedback. However, I did try to check the log file but the log file does not exist so that why I'm bit lost

  • MichaelDombrowski-AWS EXPERT
    2 years ago

    Please review the Greengrass log and the AWS Console. It will tell you why the deployment failed.

    Please note that WSL is not explicitly supported. WSL does not have Systemd so you cannot install Greengrass as a system service in WSL which will limit what GG can do. Greengrass natively supports installing on Windows, so you can do that directly.

  • J
    2 years ago

    Hi. Thanks for the suggestion. I managed to find error in the log as it was failing to get items from s3. I did add "allow/GetObject" but somehow it didnt work. (I added it separately json but maybe I made mistake). I added pretty much the same stuff to existing policy and it started to get items from s3 so the deployment worked. Thank you everyone :)

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.

Relevant content