I don’t know the details of your infrastructure and settings but if you’ve installed n8n on Docker, I would suggest you to handle logging with the Docker logging options.
I’ve used the below parameter to minimize logging on Docker.
@pb84 please make sure to always fill the question template instead of simply deleting it. We ask those questions for a reason. They do not just make our life easier, they also ensure that we are able to help you properly. Without that information, we have to now do a lot of asking and guessing. What DB are you using, are you running via Docker (if so @samaritan answer could help), …
I now simply assume for now you are using SQLite, in this case, pruning could be the answer. If you look for “prune” in this forum, you should find multiple posts about it. One for example here:
If that does not help, please make sure to provide all the requesting information. Thanks!
Ah, now see that you added that information in your initial message. Did you restart n8n once or twice? Just to be sure that it did delete the data older than 90h + it did then also prune it?
Did you check how large the .n8n folder actually is? Asuming it is in your home folder that would be:
ls -lh ~/.n8n/
You should then see a line like this:
-rw-rw-r-- 1 jan jan 233M Mai 12 20:31 database.sqlite
Original fields from my first post worked - I just didn’t appreciate the size of some files clogging up n8n and erroneously raised this ticket - would be worthwhile creating a new ticket if it doesnt resolve
In addition to configuring the codes in the docker-compose.yml file to manage the size of the n8n SQLite database, it’s also important to remember to clean up old and unused Docker images. This is crucial to prevent disk space from being occupied by old versions of n8n.
To perform this cleanup, you can use the following command:
docker image prune -a
This command will remove all unused images, including old versions of n8n. Make sure to run this command periodically, perhaps as part of an update script, to prevent the accumulation of unnecessary images and keep your server efficient in terms of disk space.