Skip to content
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

On Windows 10, plugins unreachable without additional settings #6587

Closed
tyrannosaurus-becks opened this issue Apr 15, 2019 · 1 comment
Closed
Assignees

Comments

@tyrannosaurus-becks
Copy link
Contributor

This issue came in through the vault-tool forum here.

On Windows 10 (this is not duplicate-able on Ubuntu), with Vault 1.1.0, following our docs for configuration, plugins are failing to be addressable unless the PLUGIN_MIN_PORT and PLUGIN_MAX_PORT is set for github.com/hashicorp/go-plugin to use. Otherwise they fail with output like:

2019-04-12T14:23:47.075+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi: starting

 plugin: metadata=true path=C:\Users\ar\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe args=[C

:\Users\ar\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe]

2019-04-12T14:23:47.083+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi: plugin s

tarted: metadata=true path=C:\Users\ar\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe pid=5524



2019-04-12T14:23:47.083+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi: waiting

for RPC address: metadata=true path=C:\Users\ar\Documents\vault\bin\go_build_github_com_Venafi_vault_pki_backend_venafi.exe



2019-04-12T14:23:47.154+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi: using pl

ugin: metadata=true version=4

2019-04-12T14:23:47.154+0300 [DEBUG] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi.go_build_

github_com_Venafi_vault_pki_backend_venafi.exe: plugin address: metadata=true address=127.0.0.1:10002 network=tcp timestamp=2019-04-12T14:

23:47.112+0300

2019-04-12T14:23:47.154+0300 [TRACE] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi: setup: t

ransport=gRPC status=started

2019-04-12 14:23:47.157400 I | [ERR] plugin: plugin acceptAndServe error: strconv.ParseInt: parsing "": invalid syntax

2019-04-12T14:23:52.161+0300 [TRACE] secrets.vault-pki-backend-venafi.vault-pki-backend-venafi_83e6e933.vault-pki-backend-venafi: setup: t

ransport=gRPC status=finished err="rpc error: code = Unknown desc = timeout waiting for connection info" took=5.0072557s

2019-04-12T14:23:52.161+0300 [ERROR] secrets.system.system_84e204b1: mount failed: path=venafi-pki/ error="rpc error: code = Unknown desc

= timeout waiting for connection info"

2019-04-12T14:24:03.169+0300 [DEBUG] rollback: attempting rollback: path=auth/token/

2019-04-12T14:24:03.169+0300 [DEBUG] rollback: attempting rollback: path=identity/

2019-04-12T14:24:03.169+0300 [DEBUG] rollback: attempting rollback: path=sys/

2019-04-12T14:24:03.169+0300 [DEBUG] rollback: attempting rollback: path=cubbyhole/

2019-04-12T14:24:03.169+0300 [DEBUG] rollback: attempting rollback: path=secret/

We should probably document this, or perhaps set these automatically to be the same value as the Vault port, or perhaps address the issue in the go-plugin repo.

@michelvocks
Copy link
Contributor

Closing this since hashicorp/go-plugin#111 has been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants