Running into an issue where whenever there is a dyn record state refresh or change, it would error out about peer resetting the connection. It seems sporadic, but happens too often and worries me as I have setup up an automated process for terraform. This time I did it manually because of specific issues.
I've reached out to DYN support but they couldnt find anything specific and I wasn't able to give them what calls are actually being made. They've also said it wasn't an api rate limit issue.
Terraform Version
Run terraform -v to show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed.
v0.10.7
Affected Resource(s)
Please list the resources as a list, for example:
Happens during terraform plan and apply.
provider.dyn: Error setting up Dyn client: read tcp :49000->162.88.175.10:443: read: connection reset by peer
Error#5
fastly_service_v1.: Destruction complete after 3s
Error applying plan:
1 error(s) occurred:
provider.dyn: Error setting up Dyn client: read tcp :49162->162.88.175.10:443: read: connection reset by peer
Usually running a 2nd time makes it successful.
Expected Behavior
What should have happened?
Should have worked
Actual Behavior
What actually happened?
Connection reset, by what looks like an IP belonging to DYN
I've reached out to dyn support and they said it's not an api limit issue.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example:
Not really reproducibile. Sometimes it works, sometimes it doesnt. Very hard to pinpoint and also same for Dyn support. Since they said they need to know what calls are being made and I don't know what terraform does during what looks like a state refresh of the dyn records.
Sorry if all this is being very vague. I have very little to go on.
But let me know if there are debug commands I can run to generate more helpful information.
Hi there,
Running into an issue where whenever there is a dyn record state refresh or change, it would error out about peer resetting the connection. It seems sporadic, but happens too often and worries me as I have setup up an automated process for terraform. This time I did it manually because of specific issues.
I've reached out to DYN support but they couldnt find anything specific and I wasn't able to give them what calls are actually being made. They've also said it wasn't an api rate limit issue.
Terraform Version
Run
terraform -vto show the version. If you are not running the latest version of Terraform, please upgrade because your issue may have already been fixed. v0.10.7Affected Resource(s)
Please list the resources as a list, for example: Happens during terraform plan and apply.
Error#1 Error refreshing state: 1 error(s) occurred:
Error#2 dyn_record.: Refreshing state... (ID: 308573916)
dyn_record.: Refreshing state... (ID: 308799407)
Error running plan: 1 error(s) occurred:
Error#3 dyn_record.some_record2: Refreshing state... (ID: 308799407) dyn_record.some_record: Refreshing state... (ID: 308573916) Error running plan: 1 error(s) occurred:
Error#4 dyn_record.some_record: Refreshing state... (ID: 308573916) dyn_record.some_record2: Refreshing state... (ID: 308799407)
Error running plan: 1 error(s) occurred:
Error#5 fastly_service_v1.: Destruction complete after 3s
Error applying plan:
1 error(s) occurred:
Usually running a 2nd time makes it successful.
Expected Behavior
What should have happened? Should have worked
Actual Behavior
What actually happened? Connection reset, by what looks like an IP belonging to DYN I've reached out to dyn support and they said it's not an api limit issue.
Steps to Reproduce
Please list the steps required to reproduce the issue, for example: Not really reproducibile. Sometimes it works, sometimes it doesnt. Very hard to pinpoint and also same for Dyn support. Since they said they need to know what calls are being made and I don't know what terraform does during what looks like a state refresh of the dyn records.
Sorry if all this is being very vague. I have very little to go on.
But let me know if there are debug commands I can run to generate more helpful information.
This is an EC2 instance on amazon.