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.

Sign up for GitHub

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

Jump to bottom

Panic from S3 Backend #2779

Closed
deverton opened this issue May 29, 2017 · 2 comments
Closed

Panic from S3 Backend #2779

deverton opened this issue May 29, 2017 · 2 comments
Milestone
0.7.3

Comments

@deverton
Copy link
Contributor

Not sure exactly what triggered this but the leader in our 0.7.2 Vault cluster just crashed. Please see https://gist.github.com/deverton/adb37b4bb5491bd5b03bed4f7000713a for full stack trace.

Our setup is three nodes in a cluster with Consul for the HA backend and S3 for the storage. It looks like the node that had the panic was the leader at the time. Another node took over as leader within 30 seconds so that worked.
@jefferai
Copy link
Member

It looks like the S3 library from the official AWS SDK is either giving us a page that doesn't exist or giving us a key that doesn't exist. It's unclear whether the issue is with our code or the lib, but we should be able to avoid panicking here.

@jefferai jefferai added this to the 0.7.3 milestone May 29, 2017
@vishalnayak vishalnayak mentioned this issue May 31, 2017
Merged
@jefferai
Copy link
Member

jefferai commented Jun 5, 2017

Should be fixed by 2785

@jefferai jefferai closed this as completed Jun 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
0.7.3
Development

No branches or pull requests
2 participants
@jefferai @deverton