Skip to content
This repository has been archived by the owner on Nov 7, 2023. It is now read-only.

"plugin exited before we could connect" while mount #3

Closed
mlowicki opened this issue Mar 7, 2018 · 3 comments
Closed

"plugin exited before we could connect" while mount #3

mlowicki opened this issue Mar 7, 2018 · 3 comments

Comments

@mlowicki
Copy link

mlowicki commented Mar 7, 2018

> vault mount -path="gen" -plugin-name="secrets-gen" plugin
...
* plugin exited before we could connect

Vault 0.9.1

I've tried:

on Linux 70f3206690e2 4.6.0-0.bpo.1-amd64 #1 SMP Debian 4.6.1-1~bpo8+1 (2016-06-14) x86_64 Linux.

In logs I see only:

2018/03/07 11:25:23.956931 [ERROR] sys: mount failed: path=gen/ error=plugin exited before we could connect

top-level api_address is set (as suggested in #2).

@sethvargo
Copy link
Owner

Hey @mlowicki

I'm unable to reproduce this on my end, but I don't have access to that version of Debian. Can you please try using Vault 0.9.4 (or later) and the latest version of the plugin (v0.0.2)?

@illenseer
Copy link

illenseer commented Mar 8, 2018

I think, we had the same problem. If Vault is using mlock, then the plugin needs the capability, too:
setcap cap_ipc_lock=+ep <path_to_plugin>/vault-secrets-gen solved it for us.

@sethvargo
Copy link
Owner

Closing due to lack of response.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 6, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants