-
Notifications
You must be signed in to change notification settings - Fork 8.9k
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
[Bug]: (logging) fatal error: out of memory
(Error: Plugin did not respond
)
#29153
Comments
Community NoteVoting for Prioritization
Volunteering to Work on This Issue
|
Off the top of my head, the provider is running out of memory because it is attempting to log the binary contents of the Lambda function's ZIP file. |
fatal error: out of memory
fatal error: out of memory
fatal error: out of memory
(Error: Plugin did not respond
)
I suspect that I can reproduce the issue 100% in situations where the plugin returns an error. Whether you get In case it is helpful, here is a complete (~4100 line) trace: https://gist.github.com/YakDriver/66b508dab3342da50b2da75f4b17a73a |
@PratteekB, how large is the Zip file that you're sending? I'd like to test with something comparable |
Hi @PratteekB, the latest version of the provider now truncates the log entries. This may address the out of memory error. If you are still seeing this error, please open a new issue and let us know the size of the Zip file that you're sending. |
I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Previously titled: "The plugin encountered an error, and failed to respond to the plugin.(*GRPCProvider).ApplyResourceChange call."
Changing the name because at this stage I believe it is misleading since any (?) error may cause this crash.
See also #29236
Terraform Core Version
1.3.4
AWS Provider Version
4.52.0
Affected Resource(s)
unclear from the error message however the 2 plugins which errored were:
aws_rds_cluster_instance
aws_lambda_function
Expected Behavior
the main.tf file was meant to execute as it has been and provision several AWS resources:
Actual Behavior
Relevant Error/Panic Output Snippet
Terraform Configuration Files
Steps to Reproduce
run 'terraform apply -auto-approve'
Debug Output
No response
Panic Output
No response
Important Factoids
No response
References
fatal error: concurrent map writes
(Error: Plugin did not respond
) #29236Would you like to implement a fix?
None
The text was updated successfully, but these errors were encountered: