-
Notifications
You must be signed in to change notification settings - Fork 22
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
debugging backup? #14
Comments
I haven't seen that issue before. Let me setup some test cases here locally and see if I can reproduce the issue. |
@vijaybandari could you please provide your consul agent configuration? |
@leprechau
|
Could you also see what a call here returns ...
You should see something like this ... [
{
"LockIndex": 0,
"Key": "testKey",
"Flags": 0,
"Value": "dGVzdEtleSB2YWx1ZQ==",
"CreateIndex": 58,
"ModifyIndex": 58
},
{
"LockIndex": 0,
"Key": "testKey2",
"Flags": 0,
"Value": "dGVzdEtleSB2YWx1ZTI=",
"CreateIndex": 63,
"ModifyIndex": 63
}
] |
@leprechau I didn't get you. Something missing in your previous comment? |
I think I see the issue ... the
|
@vijaybandari This appears to be a bug in the upstream I've filed hashicorp/consul#2403 ... I'll update this as soon as I hear back from upstream. |
I've filed hashicorp/consul#2403 ... I'll update this as soon as I hear back from the upstream package. |
Thanks @leprechau |
Please test the latest master if you can. I'll publish a new release if this resolves your issue. I've rolled back the upstream API to the 0.6.4 version. |
Thank @leprechau quick response. v 1.3 works fine 👍 |
I can see data in my consul through http api but this tool returns with 0 keys.
How do I debug the issue?
The text was updated successfully, but these errors were encountered: