2 Answers
- Newest
- Most votes
- Most comments
1
It seems like the StreamManager metadata-store was corrupted.
- Could you elaborate on how you performed this upgrade? Did you perform OTA update?
- What was the exact GGC version before the upgrade?
- Was the OTA update job successful? Did the StreamManager system lambda start successfully after the upgrade?
- Could you also add the device specs: OS, CPU architecture?
- Were there any abrupt device-shutdowns while your lambda was exporting messages with StreamManager or during the upgrade?
- aws-greengrass-stream-manager-sdk-python is compatible with StreamManager running on GGC v1.11 and above. What version of StreamManager SDK were you using before the upgrade?
answered 2 years ago
Relevant content
- asked a year ago
- asked 3 years ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 8 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
Hi there thanks for your response. I will retry the upgrade again with diff device.
Thanks. Replicating the the same setup, I upgraded GGC from 1.10.5 to 1.11.5 with OTA update from console. I see no issues with my lambda using StreamManager after the upgrade. Please let us know in case you see this issue again on your retry.