[Bug]: High resource usage on self-hosted install

[CraigBurden]

Error Message and Logs

I have Coolify alone installed on a DigitalOcean VPS in order to manage deploying apps to some other remote servers. This machine is not running anything other than Coolify.

First odd thing was this:

On the 7th there was this massive jump in disk usage, leading to the VPS running out of space. I resized it to 160GB on the 9th and you can see it creeping up dramatically already.

Secondly:

~100% memory usage constantly and some very spiky CPU behaviour. This instance has 8GB of RAM and 4 vCPUs

What can I do to diagnose what is happening here?

Steps to Reproduce

I'm not really sure

Example Repository URL

No response

Coolify Version

4.0.0-beta.462

Are you using Coolify Cloud?

No (self-hosted)

Operating System and Version (self-hosted)

Ubuntu 24.04

Additional Information

No response

[ShadowArcanist]

Hey @CraigBurden could you please run htop on your server and check what’s consuming the CPU?

Also, can you run:

du -h --max-depth=1 / | sort -hr

to see which directories are using the most disk space?

And how many remote servers are currently connected to your Coolify instance?

Include screenshots if possible

[CraigBurden]

@ShadowArcanist Thank you for the quick reply!
I have resized my VPS to allow it to boot again, it was unresponsive for the last few hours.

Running du, I get:

du: cannot access '/proc/14089': No such file or directory
du: cannot access '/proc/14090': No such file or directory
du: cannot access '/proc/14133/task/14133/fd/4': No such file or directory
du: cannot access '/proc/14133/task/14133/fdinfo/4': No such file or directory
du: cannot access '/proc/14133/fd/3': No such file or directory
du: cannot access '/proc/14133/fdinfo/3': No such file or directory
du: cannot access '/proc/14135': No such file or directory
88G     /
86G     /var
2.2G    /usr
120M    /data
119M    /boot
27M     /opt
6.2M    /etc
1.5M    /run
284K    /root
72K     /tmp
16K     /lost+found
8.0K    /snap
8.0K    /dynamic
4.0K    /srv
4.0K    /sbin.usr-is-merged
4.0K    /mnt
4.0K    /media
4.0K    /lib.usr-is-merged
4.0K    /home
4.0K    /bin.usr-is-merged
0       /sys
0       /proc
0       /dev

Here is a screenshot of htop too:

It looks like redis might be to blame?...

Currently this managing only two remote servers

I figured I'd grab docker stats too:

CONTAINER ID   NAME               CPU %     MEM USAGE / LIMIT     MEM %     NET I/O           BLOCK I/O         PIDS 
9d1695f1d5ee   coolify-sentinel   3.49%     97.48MiB / 15.62GiB   0.61%     3.97kB / 32.5kB   111MB / 3.53MB    11 
ddb84b11200d   coolify            22.67%    329.8MiB / 15.62GiB   2.06%     24.1MB / 11MB     0B / 1.86MB       30 
e6b046baa501   coolify-db         4.52%     26.1MiB / 15.62GiB    0.16%     2.04MB / 19.9MB   1.13MB / 2.03MB   7 
7e1fd20955f6   coolify-redis      2.82%     6.367GiB / 15.62GiB   40.77%    7.15MB / 2.17MB   4.82GB / 33.8GB   6 
40f3e60969aa   coolify-realtime   4.49%     49.62MiB / 15.62GiB   0.31%     24kB / 293kB      41kB / 4.1kB      21 
aa74edf870e6   coolify-proxy      0.31%     131.8MiB / 15.62GiB   0.82%     7.4MB / 7.9MB     107MB / 0B        9 

root@coolify:~# docker system df -v
Images space usage:

REPOSITORY                            TAG              IMAGE ID       CREATED         SIZE      SHARED SIZE   UNIQUE SIZE   CONTAINERS
ghcr.io/coollabsio/coolify            4.0.0-beta.463   c640329842d5   2 days ago      389MB     8.442MB       380.5MB       1
redis                                 7-alpine         e08bd8d5a677   2 weeks ago     41.4MB    0B            41.41MB       1
postgres                              15-alpine        bb506a9728d2   2 weeks ago     274MB     8.442MB       265.3MB       1
ghcr.io/coollabsio/coolify            4.0.0-beta.462   fe70332ae7ce   3 weeks ago     387MB     0B            387.4MB       0
<none>                                <none>           36a937f48ac7   7 weeks ago     274MB     0B            273.8MB       0
ghcr.io/coollabsio/coolify-realtime   1.0.10           7339e175bdf5   2 months ago    621MB     0B            620.9MB       1
ghcr.io/coollabsio/coolify-helper     1.0.12           8d4fd652c649   2 months ago    298MB     7.831MB       290.2MB       0
ghcr.io/coollabsio/sentinel           0.0.18           fb0c3479652a   2 months ago    31.3MB    0B            31.28MB       1
<none>                                <none>           13105d2858de   3 months ago    41.4MB    7.831MB       33.58MB       0
traefik                               v3.1             4b7b5054b806   17 months ago   173MB     0B            173.5MB       1

Containers space usage:

CONTAINER ID   IMAGE                                        COMMAND                  LOCAL VOLUMES   SIZE      CREATED          STATUS                    NAMES
9d1695f1d5ee   ghcr.io/coollabsio/sentinel:0.0.18           "/app/sentinel"          0               0B        12 minutes ago   Up 12 minutes (healthy)   coolify-sentinel
ddb84b11200d   ghcr.io/coollabsio/coolify:4.0.0-beta.463    "docker-php-serversi…"   0               1.68MB    16 minutes ago   Up 16 minutes (healthy)   coolify
e6b046baa501   postgres:15-alpine                           "docker-entrypoint.s…"   1               63B       16 minutes ago   Up 16 minutes (healthy)   coolify-db
7e1fd20955f6   redis:7-alpine                               "docker-entrypoint.s…"   1               0B        16 minutes ago   Up 16 minutes (healthy)   coolify-redis
40f3e60969aa   ghcr.io/coollabsio/coolify-realtime:1.0.10   "/bin/sh /soketi-ent…"   0               2B        16 minutes ago   Up 16 minutes (healthy)   coolify-realtime
aa74edf870e6   traefik:v3.1                                 "/entrypoint.sh --pi…"   0               0B        16 months ago    Up 18 minutes (healthy)   coolify-proxy

Local Volumes space usage:

VOLUME NAME     LINKS     SIZE
coolify-db      1         183.2MB
coolify-redis   1         83.9GB

Build cache usage: 0B

CACHE ID   CACHE TYPE   SIZE      CREATED   LAST USED   USAGE     SHARED

[ShadowArcanist]

Yes, it's the damn redis. I have asked one of the team member to check this post (they will be able to guide you to solve this issue)

[ShadowArcanist]

Hey @CraigBurden please do the following:

1. Stop and remove the Coolify Redis container

docker stop coolify-redis

docker stop coolify-redis

2. Completely delete the Redis volume to get rid of the AOF files, temp files

docker volume rm coolify-redis

3. Re-run the Coolify installation script to bring everything back up

curl -fsSL https://cdn.coollabs.io/coolify/install.sh | sudo bash

Note: Not sure why coolify-redis is causing this so if you run into this issue again then please let us know

[CraigBurden]

@ShadowArcanist Thank you very much
I stopped everything, just to be safe, then followed your instructions.

Just a minor note for anyone reading this in the future, the first two commands are meant to be:

docker stop coolify-redis

docker rm coolify-redis

I think that says it all! I have now downsized the VPS again, saving me $48/month, so I'm extra grateful!

Thank you for your help, I'll reopen this issue again if it happens again, just so we keep context for a potential fix. But lets hope it doesn't come to that!