1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
0
If you're running Greengrass in a Docker container, be aware that Docker containers often default to UTC, regardless of the host system's time zone. If this is the case, you can set the timezone for your Docker container explicitly.
also, some other services can use UTC by default like Sitewise, SDK + Cron jobs so please check all the relevant services related to your logging and check the default timezones.
https://docs.aws.amazon.com/iot-sitewise/latest/userguide/metrics.html
Contenuto pertinente
AWS UFFICIALEAggiornata 2 anni fa- AWS UFFICIALEAggiornata 3 anni fa
- Perché il ripristino point-in-time della mia istanza di database di Amazon RDS richiede molto tempo?AWS UFFICIALEAggiornata 2 anni fa
We are not using SiteWise, only the core IoT services and Greengrass. We are also not running GG on docker container on the device. How can I set default timezone for Greengrass, if the default timezone and the NTP sync is on the local time. (in our case, Australia/Melbourne)?
I am just a little confused how a process (greengrass / nucleus) that inherits the OS' time settings, has a different time on the logs.
The issue that I am facing (or at least, I think that I may be facing), is:
com.aws.greengrass.deployment.exceptions.AWSIotException: Unable to get response .... .... Caused by: javax.net.ssl.SSLException: Connection reset
and it may be due to the difference in the time.
Greengrass logs are always UTC time, this is not configurable. You can tell it is UTC because the time ends with
Z