search

terraform-linters / tflint-ruleset-azurerm

TFLint ruleset for terraform-provider-azurerm
Mozilla Public License 2.0
117 stars 24 forks source link

[ERR] plugin: plugin server: accept unix xxx use of closed network connection #52

Closed s-marchenko closed 4 years ago

s-marchenko commented 4 years ago

I am trying to use Azurerm plugin of TFLint, but always get the that error, it is not working neither om my Mac nor in a Docker container. I use this Docker image - https://hub.docker.com/r/wata727/tflint

The container log looks like that:

2020-08-26T09:38:44.075Z [DEBUG] plugin: starting plugin: path=/root/.tflint.d/plugins/tflint-ruleset-azurerm args=[/root/.tflint.d/plugins/tflint-ruleset-azurerm] 2020-08-26T09:38:44.079Z [DEBUG] plugin: plugin started: path=/root/.tflint.d/plugins/tflint-ruleset-azurerm pid=15 2020-08-26T09:38:44.079Z [DEBUG] plugin: waiting for RPC address: path=/root/.tflint.d/plugins/tflint-ruleset-azurerm 2020-08-26T09:38:44.130Z [DEBUG] plugin: using plugin: version=4 2020-08-26T09:38:44.130Z [DEBUG] plugin.tflint-ruleset-azurerm: plugin address: address=/tmp/plugin025355030 network=unix timestamp=2020-08-26T09:38:44.130Z 09:38:44 provider.go:86: [INFO] Prepare rules

2020-08-26T09:38:44.422Z [DEBUG] plugin.tflint-ruleset-azurerm: 2020/08/26 09:38:44 [ERR] plugin: plugin server: accept unix /tmp/plugin025355030: use of closed network connection 2020-08-26T09:38:44.424Z [DEBUG] plugin: plugin process exited: path=/root/.tflint.d/plugins/tflint-ruleset-azurerm pid=15 2020-08-26T09:38:44.424Z [DEBUG] plugin: plugin exited

I believe the reason is related to hashicorp/go-plugin, when I try to use their basic Example I get the same error. There is an issue on GitHub - https://github.com/hashicorp/go-plugin/issues/72 also, so it looks like there are some people who are experiencing the same problems.

My question is, are there any people who experiencing the same issue? Is there a way to workaround it on Mac/Linux? Meaning to use TFLint with Azure plugin.

Thanks,

wata727 commented 4 years ago

Hmmm, as you say, it seems that this error message is shown when the log level is set to debug.

However, this error doesn't seem to have any particular impact on the behavior of TFLint either (in fact, it can still report the issue correctly in this case). Do you have any problems such as not getting the expected results?

s-marchenko commented 4 years ago

Yes, you're right. TFLint looks working even if that error appears, so I believe we could close the issue.

wata727 commented 4 years ago

OK, Thank you for your feedback. If you have any questions, feel free to reopen the issue or open a new issue.