Getting the SQL Lite error: `SQLITE_FULL: database or disk is full` on render.com

[dalandanstudio]

Describe the problem/error/question

my self-hosting service (render) is not restarting properly after I added
EXECUTIONS_DATA_PRUNE=true
DB_SQLITE_VACUUM_ON_STARTUP = true

to my render ‘Environments’ section. I did it because it was a suggestion i saw here: Why is my database so big?, since I started to get the SQLITE_FULL error when i was running executions

What is the error message (if any)?

SQLITE_FULL: database or disk is full
as well as:

Please share your workflow

don’t necessarily think my workflow is important but i have been using elevenlabs API for audio lately and I think this is why this happened

Information on your n8n setup

• n8n version: 1.41.0
• Database (default: SQLite): since i’m getting this SQLite error, it’s probably the default.
• n8n EXECUTIONS_PROCESS setting (default: own, main): own
• Running n8n via (Docker, npm, n8n cloud, desktop app): render.com
• Operating system: mac

[ria]

Hi @dalandanstudio

did you add it with the spaces? It should be without, like so: DB_SQLITE_VACUUM_ON_STARTUP=true

Can you share what other variables you have set?
What errors are you getting in the service logs?

[dalandanstudio]

this is what my environment on render looks like:

i’ve noticed that when I added the EXECUTIONS_DATA_PRUNE and
DB_SQLITE_VACUUM_ON_STARTUP environment variables it starts to chuck errors in the log, and when I delete them it starts to work again.

on the other hand though i need to do something like that because my workflow’s won’t execute anyway with the SQLite error

[dalandanstudio]

oook fixed it!

I had to stop my service in order for the environment variables to work so I had to go to the dashboard of the project > Settings > scroll to the very bottom and find Suspend Web Service

basically any form of database pruning or vacuuming won’t really happen until the service is restarted, so I suspended the web service and turned it back on after adding the following variables:
EXECUTIONS_DATA_MAX_AGE
EXECUTIONS_DATA_PRUNE

EXECUTIONS_DATA_PRUNE to the value of true and EXECUTIONS_DATA_MAX_AGE to some number (I used 72 - the number represents hours) seemed to do the trick for me