- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
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
Can anyone help me out here?
Every deployment is in "In Progress" state.
The log is same as the previous thread.
Thanks,
Santosh
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
Contenuto pertinente
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa
- AWS UFFICIALEAggiornata un anno fa