-
Notifications
You must be signed in to change notification settings - Fork 98
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
Backing up binary data (Written by Hashicorp Vault) fails #71
Comments
Looks like I'm striking the same issue after pointing vault to our consul store:
Let me know if you'd like more info. |
Can you provide a sample consul DB dir for me to try and backup? |
Apologies for the delay - Consul DB containing Vault data attached. |
@ben-nz - also, in case it wasn't obvious to you (as it wasn't to me), seems like you'd not use the So, -b for backup, and no -b for restore. |
@alexku-o Thanks mate I'll give that a try. |
@alexku-o On my side I had to use |
@tyx thanks. I actually tried restore with edit: In case it came across that way, my comment here was certainly not in any way to discredit the incredible work that's been done on consulate. I appreciate a great deal of the work here, and am thankful. |
I'm hitting the same error. Value is binary data populated by consul-template for deduplication purposes, residing under
|
Getting the same error as @isavcic when using |
In the meantime, I created a dockerized solution for backing up Consul's datastore that works with Vault: Consulidator Backup: CONSUL_ADDRESS=10.0.1.2
CONSUL_PORT=8500
BACKUP_FILE=my_backup
docker run --rm \
djenriquez/consulidator:v0.1.0 \
--backup \
--port $CONSUL_PORT $CONSUL_ADDRESS > $BACKUP_FILE Restore: CONSUL_ADDRESS=10.0.1.2
CONSUL_PORT=8500
BACKUP_FILE=my_backup
docker run --rm \
-v `pwd`:/restore \
djenriquez/consulidator:v0.1.0 \
--restore $BACKUP_FILE \
--port $CONSUL_PORT $CONSUL_ADDRESS |
I'm getting the following when attempting to run a consulate backup on my consul cluster:
Looks like #41
Python 2.7.10
Consulate 0.6.0 (Both pip and master)
We've tracked the issue to Hashicorp Vault writing binary data.
Using python3.5 we instead get the error:
If there's any other information we can provide please let us know!
The text was updated successfully, but these errors were encountered: