Could not deploy Greengrass group

0

Hi,
I have followed the documentation for AWS IoT Greengrass. While deploying the greengrass group, I am getting the following error. I am using Raspberry Pi as Greengrass core.

[2019-02-06T14:35:57.317+01:00][INFO]-Greengrass Root: /greengrass
[2019-02-06T14:35:57.317+01:00][INFO]-Greengrass Write Directory: /greengrass/ggc
[2019-02-06T14:35:57.317+01:00][INFO]-Group File Directory: /greengrass/ggc/deployment/group
[2019-02-06T14:35:57.317+01:00][INFO]-Default Lambda UID: 111 GID: 115
[2019-02-06T14:35:57.318+01:00][INFO]-===========================================
[2019-02-06T14:35:57.322+01:00][INFO]-The current core is using the AWS IoT certificates with fingerprint: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-02-06T14:35:57.323+01:00][WARN]-worker process info: /greengrass/ggc/packages/1.7.0/var/worker/processes
[2019-02-06T14:35:57.324+01:00][WARN]-worker process info: /greengrass/ggc/packages/1.7.0/var/worker/processes
[2019-02-06T14:35:57.329+01:00][INFO]-Reloading registry
[2019-02-06T14:35:57.331+01:00][INFO]-The current core is using the AWS IoT certificates with fingerprint: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-02-06T14:35:57.553+01:00][INFO]-Deployment agent connected to cloud
[2019-02-06T14:35:57.553+01:00][INFO]-Started Deployment Agent and listening for updates
[2019-02-06T14:35:57.553+01:00][INFO]-Started Deployment Agent and listening for updates
[2019-02-06T14:35:57.553+01:00][INFO]-Trying to subscribe to topic $aws/things/SmartFoodGroup_Core-gda/shadow/update/delta
[2019-02-06T14:35:57.58+01:00][INFO]-Subscribed to : $aws/things/SmartFoodGroup_Core-gda/shadow/update/delta
[2019-02-06T14:35:57.58+01:00][INFO]-Trying to subscribe to topic $aws/things/SmartFoodGroup_Core-gda/shadow/get/accepted
[2019-02-06T14:35:57.609+01:00][INFO]-Subscribed to : $aws/things/SmartFoodGroup_Core-gda/shadow/get/accepted
[2019-02-06T14:42:56.194+01:00][INFO]-Start to process new message from the cloud.
[2019-02-06T14:42:56.194+01:00][INFO]-Deployment (Group ID: xxxxxxxxxxxxxxxxxxxxxxxxx, Deployment ID: xxxxxxxxxxxxxxxxx, Deployment Type: NewDeployment) is in pending state.
[2019-02-06T14:42:56.196+01:00][INFO]-Existing group config does not contain a group arn. Skipping check to perform reset due to update in group id
[2019-02-06T14:42:56.196+01:00][INFO]-End processing new message from the cloud.
[2019-02-06T14:42:56.196+01:00][INFO]-Received deploymentId xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx of type NewDeployment for group xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-02-06T14:42:56.196+01:00][INFO]-Updating status to InProgress of deployment xxxxxxxxxxxxxxxxxxxxxxxx for group xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-02-06T14:42:57.905+01:00][INFO]-Executing the group Downloading step
[2019-02-06T14:43:21.401_01:00][ERROR]-Greengrass deployment error: unable to start deployment downloader. Error while downloading. Error while downloading the Group definition file Error while downloading, filename: /tmp/greengrass/gro$[52;1H[2019-02-06T14:43:21.401_01:00][ERROR]-Greengrass deployment error: unable to execute download step in deployment. Error while downloading. Error while downloading the Group definition file Error while downloading, filename: /tmp/greeng$
[2019-02-06T14:43:21.401_01:00][ERROR]-Deployment xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx of type NewDeployment for group xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx failed error: Error while downloading. Error while downloading the Group definit$[2019-02-06T14:43:21.401_01:00][INFO]-Updating status to Failure of deployment xxxxxxxxxxxxxxxxxxxxxxxxxxx for group xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-02-06T14:43:21.46+01:00][INFO]-Updating shadow for deployment: xxxxxxxxxxxxxxxxxxxxxxxxxx of group: xxxxxxxxxxxxxxxxxxxxxxx
[2019-02-06T14:43:21.489+01:00][INFO]-Start to process new message from the cloud.
[2019-02-06T14:43:21.489+01:00][INFO]-End processing new message from the cloud.

Thanks,
Santosh

asked 5 years ago212 views
3 Answers
0

Hi,
I have also added proxy details to the config.json file. But, the deployment is in "In Progress" status for a very long time.
PFB the runtime.log.
[2019-02-07T14:22:38.508+01:00][INFO]-Greengrass Root: /greengrass
[2019-02-07T14:22:38.508+01:00][INFO]-Greengrass Write Directory: /greengrass/ggc
[2019-02-07T14:22:38.508+01:00][INFO]-Group File Directory: /greengrass/ggc/deployment/group
[2019-02-07T14:22:38.508+01:00][INFO]-Default Lambda UID: 111 GID: 115
[2019-02-07T14:22:38.509+01:00][INFO]-===========================================
[2019-02-07T14:22:38.513+01:00][INFO]-The current core is using the AWS IoT certificates with fingerprint: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
[2019-02-07T14:22:38.514+01:00][WARN]-worker process info: /greengrass/ggc/packages/1.7.0/var/worker/processes
[2019-02-07T14:22:38.515+01:00][WARN]-worker process info: /greengrass/ggc/packages/1.7.0/var/worker/processes
[2019-02-07T14:22:38.517+01:00][INFO]-Using proxy http://myproxy.com:80
[2019-02-07T14:22:38.52+01:00][INFO]-Reloading registry
[2019-02-07T14:22:38.523+01:00][INFO]-The current core is using the AWS IoT certificates with fingerprint: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

Thanks,
Santosh

answered 5 years ago
0

Can anyone help me out here?
Every deployment is in "In Progress" state.

The log is same as the previous thread.

Thanks,
Santosh

answered 5 years ago
0

Hi SantoshPanda,

Every deployment shows "In Progress" on the console? Have you ever been able to get a deployment to work? You said you setup a proxy. Do you know if certain ports are restricted on your Internet connection? Even if you setup a proxy Greengrass still uses port 8883.
https://docs.aws.amazon.com/greengrass/latest/developerguide/gg-core.html#alpn-network-proxy

You can test if your ports are restricted by typing:

curl -v https://greengrass.iot.us-west-2.amazonaws.com:8883

You should see:

Connected to greengrass.iot.us-west-2.amazonaws.com (+ip+) port 8883 (#0)

The final message will be that there are bad certificates because none were specified in the command.
Thanks,
Keagen

AWS
KR-AWS
answered 5 years ago

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