Closed faisalrazzak closed 1 year ago
@faisalrazzak we've found the most common cause of this error has been a mismatch between the x86/x64 architecture of the vault
binary and that of the vault-pki-monitor
binary. Can you please confirm you are using the Linux amd64 version of Vault Enterprise v1.8.2 with the vault-pki-monitor
binary that has the following SHA256SUM?
977980444b0509e425877f484f234c71de4379781c7cdfc38bc487702a5e714d
I was able to get that combination of binaries to work fine my Ubuntu test system.
@tr1ck3r I was able to resolve the issue for my environment. Everytime, I had used the same version of plugin with checksum 977980444b0509e425877f484f234c71de4379781c7cdfc38bc487702a5e714d
.
This issue does manifest from time to time in different environments. It would be nice to ask HashiCorp to identify all reasons when vault throws: Unrecognized remote plugin message: plugin is either invalid or simply needs to be recompiled
.
Great to hear @faisalrazzak Did you see the extra step if mlock
is enabled that is documented here? Did you execute the setcap command or have disable_mlock
set to true for your Vault (the latter is not recommended for production)?
I believe this is the code responsible for generating that error: https://github.com/hashicorp/go-plugin/blob/d555eeb4b4a65f16bdfd9fb2edc74b7ebd1f7744/client.go#L688-L699
I'm closing this issue as it seems it was originated from user's environment and an error related to the plugin itself.
PROBLEM SUMMARY
I am using Enterprise Vault 1.8 on a Ubuntu 20 system and trying to deploy venafi-pki-monitor plugin. However, I keep getting the following error message for
**vault path-help**
command:STEPS TO REPRODUCE
vault path-help <pki-engine-path>
EXPECTED RESULTS
The command should show help for the path.
ACTUAL RESULTS
ENVIRONMENT DETAILS
COMMENTS/WORKAROUNDS
This error is not limited to these versions. I have observed this behavior with other Vault/Plugin versions as well. All steps outlined in Vault's plugin documentation were also followed.