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

Add LMDB corruption FAQ #4298

Merged
merged 1 commit into from
Aug 23, 2022
Merged

Add LMDB corruption FAQ #4298

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions app/_data/docs_nav_gateway_3.0.x.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -579,3 +579,5 @@ items:
url: /reference/performance-testing-framework
- text: Router Operators
url: /reference/router-operators
- text: FAQ
url: /reference/faq
16 changes: 16 additions & 0 deletions src/gateway/reference/faq.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
---
title: FAQ
---

Can't find what you're looking for on this page? Let us know at team-docs@konghq.com.

### Kong crashes on start (MDB_CORRUPTED)

**Q:** I receive the following error when starting Kong:
```
2022/04/11 12:01:07 [crit] 32790#0: *7 [lua] init.lua:648: init_worker(): worker initialization error: failed to create and open LMDB database: MDB_CORRUPTED: Located page was wrong type; this node must be restarted, context: init_worker_by_lua*
```

**A:** Your local configuration cache is corrupted. Remove your LMDB cache (located at `<prefix>/dbless.lmdb`, which is usually `/usr/local/kong/dbless.lmdb`) and start Kong again. This will force your Kong node to pull configuration from the control plane rather than using the cache.

---