- 최신
- 최다 투표
- 가장 많은 댓글
Hi, have you authorized ggc_user to use the greengrass-cli? You need to do that as described here https://docs.aws.amazon.com/greengrass/v2/developerguide/install-gg-cli.html and https://docs.aws.amazon.com/greengrass/v2/developerguide/greengrass-cli-component.html#greengrass-cli-component-configuration i.e. add the ggc_user to a group and set that group as the AuthorizedPosixGroups in component configuration for aws.greengrass.Cli component through a deployment from your AWS account. Let us know if you face any issues with that or still can't get it to work
Hello,
Yes, ggc_user's profile should be enough to run greengrass-cli component restart in another component's lifecycle.
However, please note that greengrass-cli component restart only works on a non-broken component.
When ComponentA errors, greengrass will retry its lifecycle 3 times and transition it to broken state if all retries fail. After ComponentA is in a broken state, running greengrass-cli component restart -n ComponentA cannot restart the component. The only way to resurrect it is via deployment.
Thank you but this makes no sense to me. When GreenGrass-cli is installed as a component, it defaults to gcc_user to use that user, also the user greengrass is being managed is say 'myadmin'. Manually I can execute greengrass-cli using sudo and that 'myadmin' account. When my software runs it shells using sudo -u myadmin -S etc so it has exactly the same context and security as when manually. ggc_user is already member of ggc_group and the 'myadmin' is member of ggc_group.
So, greengrass_cli is by default not executed by ggc_user?
Correct,
ggc_useris intended for running components. If you want to be able to run thegreengrass_cliwithggc_useryou should authorize it as described above. This exists becausegreengrass-clihas more capabilities than components such as deployments and starting/restarting/removing components
I'm having a similar issue where I'm not able to use the Greengrass cli. Every time I get a:
Caused by: java.io.IOException: Not able to find auth information in directory: /greengrass/v2/cli_ipc_info. Please run CLI as authorized user or group.
I've been looking everywhere but I can't seem to find a feasible answer for this issue. I tried doing the following:
- Set the GGC_ROOT_PATH environment variable to /greengrass/v2.
- Add the --ggcRootPath /greengrass/v2 argument to your command as shown in the following example.
As recommended by AWS documentation (https://docs.aws.amazon.com/greengrass/v2/developerguide/gg-cli-reference.html) but I get nowhere.
Any help would be appreciated!
The component is not dead, it responds to SIGTERM. Also, manually running component restart works, but from code, using a a shell from ANOTHER componet, the gcc_user context, does not help. It does nothing, no error, just the log fact that it 'ran'.