[bug] Problem stopping execution – Only running or waiting executions can be stopped and 4733 is currently error

[SolomonChrist]

Problem stopping execution – Only running or waiting executions can be stopped and 4733 is currently error

Anyone else experiencing this?

DigitalOcean VPS

I’m planning to reset everything but wanted to know if there was a reason for this bug?

[SolomonChrist]

I figured it out on my end (hope this helps others):
My DigitalOcean box ran out of space and was giving the error: OSError: [Errno 28] No space left on device

I shut my server down, increased the disk space yet the partition was still 25gb even though I increased it to 50gb.

I ran the following command:
df -h

That showed me that my main drive was 100% taken, so to fix that I did the following commands:

NOTE: BACKUP THINGS VIA A BACKUP IMAGE BEFORE DOING THIS - I WILL NOT BE HELD RESPONSIBLE IF YOU SCREW THINGS UP!
I first ran this command to free up some quick space:
sudo rm -rf /var/lib/apt/lists/*

Then I ran this to clear some system logs:
sudo journalctl --vacuum-time=1d

Once I had some free space I ran the following commands (After INCREASING my disk space to 50GB on DigitalOcean):
sudo apt update
sudo apt install cloud-guest-utils

Then I ran this to expand the partition size to 50GB:
sudo growpart /dev/vda 1
sudo resize2fs /dev/vda1

Then I checked that my partition size had grown using df -h

I restarted docker again:
sudo systemctl restart docker

Then I pruned the Docker stuff to remove excess data:
docker system prune -a --volumes

Finally I setup a cron job to auto-prune docker sundays at 4am:
sudo crontab -e

IF “no crontab for root - using an empty one” then choose 1

Then I put the following at the very bottom:
0 4 * * 0 docker system prune -a --volumes -f && journalctl --vacuum-time=3d

I then hit CTRL + O then Enter and then CTRL + X to exit and restarted my server.

I finally had my disk space back and used Linux commands to free up more space on my Docker for n8n.

I’m going to create a BACKUP video for n8n users next because of this experience!!!

[SolomonChrist]

After diving deeper, here is where all the data was:

Breakdown of Disk Usage in /var/lib/docker:

Folder	Size	What it is
/overlay2	12G	Layers from Docker images & containers
/volumes	8.0G	Data stored by containers (e.g. n8n DB, uploads)
/containers, buildkit, image	Smaller	Support files, logs, metadata

So now I’m trying to figure out how it got so big and what can be done. Any tips or advice @n8n team?

[SolomonChrist]

OMG Okay I was able to reduce the sql database down!! It seems that a lot of dead SQL DB data is sitting in there. From 7.4GB I brought it down to a couple of megs as follows:

inside my docker image for n8n make sure you are logged in as a ROOT user via the following command first:
docker exec -u 0 -it n8n-docker-caddy-n8n-1 /bin/sh

Then navigate to the folder: /home/node/.n8n (This is a hidden folder)

From there install sqlite3 with the following commands:
apk update
apk add sqlite sqlite-libs

Then run the following command (In the /home/node/.n8n/ folder) to clear dead space in your sqlite database file (NOTE: Make sure you backed everything up).
sqlite3 database.sqlite “VACUUM;”

The above worked for me and now I’ve got a clean db again and no bloat!

The Vacuum Command:
The VACUUM command is an essential maintenance tool for stable and optimal database performance. It improves query performance by recovering space occupied by “dead tuples” or dead rows in a table caused by records that have been deleted or updated