I would like to know why the log files and Docker images are really big in my Open edX installation, I am using JUNIPER and the latest version of Tutor.
all.log >> +15GB
tracking.log >> 800MB
Also, a couple of Docker images are really big 12GB and 90GB.
May I know If I need to configure something in Tutor to reduce the increase of these files?
Or I need to make a maitenance in the files and image, if so, what´s commands can I use
Thanks for your support
These log files are large because, well, you’ve had a lot of traffic for a long time The LMS and CMS store all logs to
all.log, and tracking logs, which are then used for analytics, are stored in
tracking.log. If you have no use for these files you can simply delete them.
I find this surprising. Are you talking about Docker images or containers? Which ones? How did you discover that? The largest Docker image in Tutor is “openedx” which should not exceed ~824 MB (Docker Hub).
Btw @herwingrodriguez if you are running Juniper then it means that you are definitely not running the latest version of Tutor. After Juniper, Tutor was upgraded to Koa (December 2020) and Lilac (June 2021).
Thanks for your quick response.
I cleaned the logs from tutor but the issue with the containers still persists.
This is the status of my server.
Filesystem Size Used Avail Use% Mounted on
udev 12G 0 12G 0% /dev
tmpfs 2.4G 247M 2.2G 11% /run
/dev/mapper/edump--vg-root 156G 144G 4.3G 98% /
tmpfs 12G 4.0M 12G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 12G 0 12G 0% /sys/fs/cgroup
/dev/loop2 43M 43M 0 100% /snap/certbot/1150
/dev/loop1 62M 62M 0 100% /snap/core20/1026
/dev/loop0 43M 43M 0 100% /snap/certbot/1201
/dev/loop4 33M 33M 0 100% /snap/snapd/12159
/dev/loop5 62M 62M 0 100% /snap/core20/975
/dev/sda1 720M 110M 574M 17% /boot
/dev/loop6 33M 33M 0 100% /snap/snapd/12398
tmpfs 2.4G 0 2.4G 0% /run/user/1001
c32d1dc6d8e1 overhangio/openedx:11.2.5 "docker-entrypoint..." 4 weeks ago Up 8 minutes 8000/tcp tutor_local_lms_1
If you can see we have a container of 95GB.
May I know if we can run the following command?
docker system prune -f
If we run it, the Open edX will be working?, If I can not use it, may I know the commands that I need to execute too release the space of the disk.
Thanks for your support.
I believe running
docker system prune -f should be safe, since you will not prune volumes. But it’s not going to resolve you main issue, which is that you have a single container using up a lot of space.
I cannot help you further because you did not indicate what command you used to print the space used by the containers. Is it the space used by the Docker log files? Is it the container itself? If the container generates a lot of data inside of itself, then we have a problem. We are not supposed to accumulate a lot of data like this. If it’s simply the Docker process which is collecting container logs in the file system, then the problem will go away by restarting the lms container.
Thanks for your answer
I used this command:
du -sh * on /var/lib/docker/containers
I consider that the issue is with the container because the size of the original image is around 2GB
overhangio/openedx 11.2.5 e4f91c380688 3 months ago 2.55GB
About the volumes the folder is empty
Thanks for your support
Can you please find out which file(s) are taking up the most space in
Thanks for your support, this is the file that is takin most space.
This is the log file generated by Docker that includes all the logs emitted by the container since it started. Just restart the container (
tutor local restart lms) and it should go away.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.