-
Notifications
You must be signed in to change notification settings - Fork 51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error #3
Comments
@raakey - did you setup the permissions did you follow steps here https://www.webdigi.co.uk/blog/2017/aws-instance-automated-ami-creation-deletion-system/ to create this permissions https://github.com/webdigi/AWS-AMI-Automated-Creation-Deletion/blob/master/roles/roles.json and then add that permission to Lambda? It just looks like a permission issue. |
Yes i followed the same. AMI got deleted but Snapshots are still exist. |
how many EBS volumes were attached to the instances? |
Only One. |
can you please try another AMI. Looks like https://github.com/webdigi/AWS-AMI-Automated-Creation-Deletion/blob/master/lambda/deleteAMI.js line 79 is not set. Please paste the log lines above and below the ones you sent earlier also. We have multiple instances and they all work well as expected. |
Ok i will let u know that, thanks |
Logs Logs Time (UTC +00:00) |
ok, did you try the create and delete again? Have you made any changes to the code? |
except region, haven't changed any thing, i just copy and pasted |
thanks, we could not replicate this issue at all. Very odd.
|
Ok, im going to try on another instance. i will send the logs again. Thanks for the reply |
TypeError: Cannot read property 'SnapshotId' of undefined at null._onTimeout (/var/task/index.js:76:73) at Timer.listOnTimeout (timers.js:92:15) I tried on another Instances, Getting same problem, |
I have tried on another instance just now, with adding same tags to that, that was working fine and clearing all AMI's with snapshots, and which i created earlier (above screen shot). that was not working properly. it showing timeout error (earlier error code.). |
so did you fix it with a change? I assume you mentioned it worked? |
was that applied to both the create and delete lambda function? |
Thanks for that. It looks like a timeout. In the lambda script can you please check configuration and the timeout is set to 5 minutes? Related to issue #4. |
Yes 5 minutes, still getting problem.
…On Wed, Jun 14, 2017 at 10:31 AM, Webdigi - Web Development < ***@***.***> wrote:
Thanks for that. It looks like a timeout. In the lambda script can you
please check configuration and the timeout is set to 5 minutes? Related to
issue #4
<#4>.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#3 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AXkVnKvT1VPNJu-AQjCWu5P8lPxjIOU2ks5sD2lCgaJpZM4NTiXx>
.
--
S Rakesh
+91-8105209463
|
I set timeout to 5 minutes. And again i getting that problem.snapshots deletion problem. |
I am also facing same issue. Any solutions to fix this issue. |
found another solution here "#4". I have updated my code and lets see how my job will go on sunday. |
@Joshuapaul There's been new commits from Dec 2018, and it addressed this issue for me. |
Hi, iam very new to the Lambda, but when i execute your scripts in lambda, here iam getting the Error , please find below
2017-05-07T23:00:14.702Z e6ba23fe-3378-11e7-b141-6384f3daab93 TypeError: Cannot read property 'SnapshotId' of undefined
at null._onTimeout (/var/task/index.js:76:73)
at Timer.listOnTimeout (timers.js:92:15)
The text was updated successfully, but these errors were encountered: