-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
panic: invalid page type #7471
Comments
Hello fcddk, thank you for reporting this problem! From the stack trace it looks like this is a panic from
I was not able to find a clear solution to the problem, but I found some information that might help. First it seems the issue is related to the filesystem. One report suggested that the mount options that were being used for the filesystem may have been causing the problem. Another few reports suggested the problem was corrupt db files, and that removing the files fixed the problem. If you run I hope that helps. Please do let us know if it worked, and if you have any more questions! |
@dnephin I run consul cluster on kubernetes with version 1.7.1 also meet this probelem like below: |
from https://github.com/boltdb/bolt/releases also found that boltdb doesn't upgrade any more. So if the problem is born of boltdb, who can solve the storage probelm of boltdb |
I'm having a similar issue on my home kubectl cluster:
I think this happened after a power outage (at least that's when I noticed it, but I haven't looked into my Consul setup in a little while, so it may have happened before then), I wonder if the bolt database got corrupted somehow? |
@sarahhodne yes, you have my doubts |
1 similar comment
@sarahhodne yes, you have my doubts |
Hello all! To update this thread - I have created a top level issue to track upgrading BoltDB to bbolt here. Please follow that work as a precursor to the issues mentioned here. Thank you all for your patience! |
bootstrap_expect > 0: expecting 3 servers
The text was updated successfully, but these errors were encountered: