# Openvidu storage space

**URL:** <https://openvidu.discourse.group/t/openvidu-storage-space/3776>\
**Category:** How to implement?\
**Tags:** v2\
**Created:** [February 27, 2022, 1:52am UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776 "2022-02-27T01:52:45Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![OgtayTasinov](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/ogtaytasinov/32/1192_2.png) [@OgtayTasinov](https://openvidu.discourse.group/u/OgtayTasinov)\
**Post date:** [February 27, 2022, 1:52am UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/1 "2022-02-27T01:52:45Z")

</div>

Hi @cruizba @micael.gallego, what is the solution to free up disk space when storage usage is %90 ?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [February 28, 2022, 2:22pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/2 "2022-02-28T14:22:55Z")

</div>

What OpenVidu Edition do you have deployed?: CE, PRO or ENTERPRISE  
What version are you using?

What is the directory with more space occupied? You can take a look with this command:

```auto
du -hs /opt/openvidu/* | sort -n -r | head -n 10

```

Can you also check the space of your docker logs? (From versions \<=2.16.0 docker logs was not limitted so coturn generates too much logs and sometimes fill the disk.).

```auto
du -shc /var/lib/docker/containers/*/*-json.log | tail -n1

```

With those commands you can tell me what is the directory that is filling your disk.

Regards.

---

<div class="post-metadata">

**Author:** ![OgtayTasinov](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/ogtaytasinov/32/1192_2.png) [@OgtayTasinov](https://openvidu.discourse.group/u/OgtayTasinov)\
**Post date:** [February 28, 2022, 3:30pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/3 "2022-02-28T15:30:03Z")

</div>

I am using 2.15.1 pro ( [OpenVidu Docs](https://docs.openvidu.io/en/2.15.0/openvidu-pro/deployment/aws/))  
26G /opt/openvidu/elasticsearch  
du: cannot access ‘/var/lib/docker/containers/_/_-json.log’: No such file or directory (above command could not find, I ran with sudo)  
I found below:

27G containers/138ab8116a97edd19ffa7f8146840b4a33755120c3fa8c17c4cd4e6d0de9d300/138ab8116a97edd19ffa7f8146840b4a33755120c3fa8c17c4cd4e6d0de9d300-json.log

11G containers/1cd6b434a5be9e9efadc6c08bececd64665851a5338ac0b86e96907d2f22e285/1cd6b434a5be9e9efadc6c08bececd64665851a5338ac0b86e96907d2f22e285-json.log

7.0G containers/bf207d36aaa2fe03e436a511c3c00c9ffffeb0cfc9f75e84dc95b5f4d0dd5e9b/bf207d36aaa2fe03e436a511c3c00c9ffffeb0cfc9f75e84dc95b5f4d0dd5e9b-json.log

267M containers/2379fc3ea97fc695540360d479b5c8f001bad7b35fb83990ce97b96526303b4d/2379fc3ea97fc695540360d479b5c8f001bad7b35fb83990ce97b96526303b4d-json.log

11M containers/4337284194f958b338d25b8f92f31a2c667d2fa1a9b6425f605a7c7fcabe5679/4337284194f958b338d25b8f92f31a2c667d2fa1a9b6425f605a7c7fcabe5679-json.log

266M containers/b26ab802c75e558f054a5742f28bb59eca71a1c68b970b629894a239bdb85b32/b26ab802c75e558f054a5742f28bb59eca71a1c68b970b629894a239bdb85b32-json.log

Is it ok if I delete those logs?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [February 28, 2022, 3:42pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/4 "2022-02-28T15:42:10Z")

</div>

Yes, you can remove that logs with no problem.

I recommend you to update to a newer version (latest is 2.20.0) as soon as possible.

Regards

---

<div class="post-metadata">

**Author:** ![OgtayTasinov](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/ogtaytasinov/32/1192_2.png) [@OgtayTasinov](https://openvidu.discourse.group/u/OgtayTasinov)\
**Post date:** [February 28, 2022, 3:53pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/5 "2022-02-28T15:53:31Z")

</div>

> [@cruizba](#):
>
> I recommend you to update to a newer version (latest is 2.20.0) as soon as possible.

Is 2.15 going to be deprecated?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [February 28, 2022, 4:01pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/6 "2022-02-28T16:01:56Z")

</div>

Not deprecated itself, but we can offer better support for newer versions.

Regards

---

<div class="post-metadata">

**Author:** ![OgtayTasinov](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/ogtaytasinov/32/1192_2.png) [@OgtayTasinov](https://openvidu.discourse.group/u/OgtayTasinov)\
**Post date:** [February 28, 2022, 10:35pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/7 "2022-02-28T22:35:30Z")

</div>

> [@OgtayTasinov](#):
>
> containers/138ab8116a97edd19ffa7f8146840b4a33755120c3fa8c17c4cd4e6d0de9d300/

@cruizba I have deleted all above log files but it still shows disk usage the same. Should I reboot or what to do?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [March 2, 2022, 4:58pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/8 "2022-03-02T16:58:29Z")

</div>

It should be updated eventually. Did you checked again?

What free space shows…:

```auto
df -h

```

---

<div class="post-metadata">

**Author:** ![OgtayTasinov](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/ogtaytasinov/32/1192_2.png) [@OgtayTasinov](https://openvidu.discourse.group/u/OgtayTasinov)\
**Post date:** [March 2, 2022, 5:13pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/9 "2022-03-02T17:13:12Z")

</div>

/dev/xvda1 97G 83G 15G 85% / - I have deleted about \>45GB log

---

<div class="post-metadata">

**Author:** ![micael.gallego](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/micael.gallego/32/2_2.png) [@micael.gallego](https://openvidu.discourse.group/u/micael.gallego)\
**Post date:** [March 2, 2022, 5:26pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/10 "2022-03-02T17:26:20Z")

</div>

We recomend to a newer versions as a regular basic.

The new versions are mostly backward compatible and you do not have to change anything in your application (only minor things that maybe affect to you). Please take a look to breaking changes section in releases pages:

[https://docs.openvidu.io/en/stable/releases/](https://docs.openvidu.io/en/stable/releases/)

Regards

---

<div class="post-metadata">

**Author:** ![OgtayTasinov](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/ogtaytasinov/32/1192_2.png) [@OgtayTasinov](https://openvidu.discourse.group/u/OgtayTasinov)\
**Post date:** [March 3, 2022, 3:58pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/11 "2022-03-03T15:58:08Z")

</div>

Have you encountered this kind of disk space issue before?

---

<div class="post-metadata">

**Author:** ![cruizba](https://yyz2.discourse-cdn.com/free1/user_avatar/openvidu.discourse.group/cruizba/32/18_2.png) [@cruizba](https://openvidu.discourse.group/u/cruizba)\
**Post date:** [March 3, 2022, 6:46pm UTC](https://openvidu.discourse.group/t/openvidu-storage-space/3776/12 "2022-03-03T18:46:53Z")

</div>

Yes, mostly in versions \<= 2.15.1 where no log policy was taken in place.

After that we’ve added this policy for docker logging in all containers:

> <https://github.com/OpenVidu/openvidu/blob/v2.16.0/openvidu-server/deployments/pro/docker-compose/openvidu-server-pro/docker-compose.yml#L76-L78>

Did you tried to restart the infra? Are you still having problems with space? Maybe logs was not deleted correctly