# Failed to open BadgerDB object: file does not exist for table

**URL:** <https://discuss.dgraph.io/t/failed-to-open-badgerdb-object-file-does-not-exist-for-table/17878>\
**Category:** Badger\
**Tags:** kind:bug\
**Created:** [October 17, 2022, 8:54pm UTC](https://discuss.dgraph.io/t/failed-to-open-badgerdb-object-file-does-not-exist-for-table/17878 "2022-10-17T20:54:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![jared.davis](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/jared.davis/32/10087_2.png) [@jared.davis](https://discuss.dgraph.io/u/jared.davis)\
**Post date:** [October 17, 2022, 8:54pm UTC](https://discuss.dgraph.io/t/failed-to-open-badgerdb-object-file-does-not-exist-for-table/17878/1 "2022-10-17T20:54:10Z")

</div>

### What version of Go are you using (`go version`)?

go 1.18

### What operating system are you using?

```bash
NAME="Amazon Linux"
VERSION="2"
ID="amzn"
ID_LIKE="centos rhel fedora"
VERSION_ID="2"
PRETTY_NAME="Amazon Linux 2"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2"
HOME_URL="https://amazonlinux.com/"

```

### What version of Badger are you using?

`github.com/dgraph-io/badger/v3 v3.2103.2`

### Does this issue reproduce with the latest master?

N/A

### Steps to Reproduce the issue

Simply restarting our go service with systemctl raises the failure

### What Badger options were set?

default

### What did you do?

Start our service, which uses BadgerDB as a local cache.

### What did you expect to see?

Service startup

### What did you see instead?

In systemctl logs: `time="17-10-2022 20:51:49" level=error msg="Failed to open BadgerDB object: file does not exist for table 26018"`

---

<div class="post-metadata">

**Author:** ![jared.davis](https://yyz1.discourse-cdn.com/flex007/user_avatar/discuss.dgraph.io/jared.davis/32/10087_2.png) [@jared.davis](https://discuss.dgraph.io/u/jared.davis)\
**Post date:** [October 17, 2022, 9:05pm UTC](https://discuss.dgraph.io/t/failed-to-open-badgerdb-object-file-does-not-exist-for-table/17878/2 "2022-10-17T21:05:44Z")

</div>

I also see quite a few messages in the logs like this before the system started failing

```auto
WARNING: While running doCompact: MANIFEST removes non-existing table 95612

```