# ERROR	provider.queue	Failed to enqueue cid: leveldb: closed

**URL:** <https://discuss.ipfs.tech/t/error-provider-queue-failed-to-enqueue-cid-leveldb-closed/11551>\
**Category:** Help\
**Tags:** go-ipfs\
**Created:** [June 18, 2021, 4:05pm UTC](https://discuss.ipfs.tech/t/error-provider-queue-failed-to-enqueue-cid-leveldb-closed/11551 "2021-06-18T16:05:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![chrisijoyah](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/chrisijoyah/32/2538_2.png) [@chrisijoyah](https://discuss.ipfs.tech/u/chrisijoyah)\
**Post date:** [June 18, 2021, 4:05pm UTC](https://discuss.ipfs.tech/t/error-provider-queue-failed-to-enqueue-cid-leveldb-closed/11551/1 "2021-06-18T16:05:43Z")

</div>

I’m getting the following error after initialising the ipfs repository on a virtual Linux server.

`ERROR	provider.queue	Failed to enqueue cid: leveldb: closed`

As the server is part of a datacenter I ran the following command:

```auto
ipfs init --profile server

```

Does anyone know what this means? Also is this just a superficial error as I don’t believe this has affected the overall installation of the node as I am able to run the following successfully:

```auto
ipfs cat /ipfs/[CID]/readme

```

---

<div class="post-metadata">

**Author:** ![hector](https://sea2.discourse-cdn.com/flex020/user_avatar/discuss.ipfs.tech/hector/32/178_2.png) [@hector](https://discuss.ipfs.tech/u/hector)\
**Post date:** [June 21, 2021, 9:03am UTC](https://discuss.ipfs.tech/t/error-provider-queue-failed-to-enqueue-cid-leveldb-closed/11551/2 "2021-06-21T09:03:23Z")

</div>

It is superficial and has no effect on the installation.