- Newest
- Most votes
- Most comments
Hello François,
Is it failing to even call your lambda function handler?
In V2, the lambda manager logs into greengrass.log
as it is a plugin into the Nucleus.
Can you provide an excerpt from the log showing the error?
If there is an error in your lambda's log file that would also be helpful to investigate.
Edited by: rob-aws on Sep 14, 2021 9:17 AM
Hi Rob,
Thanks for answering.
I no longer have those logs. I reflashed that device.
From the logs I saw, this is what I understand was happening
- The lambda manager picks up a message with a triggering topic
- The lambda manager tries to decode the payload as JSON.
- An exception is raised because the JSON is not correct
- The lambda manager bails out without calling the lambda
- The lambda not being called, the message remains on the queue
- After some timeout, the same message is picked up and the process starts again.
There was an error message about JSON being invalid in the greengrass.log file
Cheers
Relevant content
- asked 2 months ago
- asked 4 months ago
- AWS OFFICIALUpdated 10 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 months ago