a year ago
Hello!
My app stop working this morning suddenly. It was working properly for many days. I have important stuff going on there.
Errolog:
License manager not initialized
Last session crashed
n8n ready on 0.0.0.0, port 5678
Basic auth has been deprecated and will be removed in a future version of n8n. For authentication, please consider User Management. To learn more: https://docs.n8n.io/hosting/authentication/user-management-self-hosted
Initializing n8n process
n8n detected that some packages are missing. For more information, visit https://docs.n8n.io/integrations/community-nodes/troubleshooting/
Version: 0.236.0
QueryFailedError: could not extend file "base/16384/875291": No space left on device
at PostgresQueryRunner.query (/usr/local/lib/nodemodules/n8n/nodemodules/typeorm/driver/postgres/PostgresQueryRunner.js:211:19)
at processTicksAndRejections (node:internal/process/task_queues:96:5)
at PostgresQueryRunner.clearTable (/usr/local/lib/nodemodules/n8n/nodemodules/typeorm/driver/postgres/PostgresQueryRunner.js:1570:9)
at EntityManager.clear (/usr/local/lib/nodemodules/n8n/nodemodules/typeorm/entity-manager/EntityManager.js:666:20)
at ActiveWorkflowRunner.init (/usr/local/lib/node_modules/n8n/dist/ActiveWorkflowRunner.js:75:13)
at Start.run (/usr/local/lib/node_modules/n8n/dist/commands/start.js:238:9)
at Start.run (/usr/local/lib/nodemodules/n8n/node_modules/@oclif/command/lib/command.js:43:20)
at Config.runCommand (/usr/local/lib/nodemodules/n8n/nodemodules/@oclif/config/lib/config.js:173:24)
at Main.run (/usr/local/lib/nodemodules/n8n/nodemodules/@oclif/command/lib/main.js:28:9)
at Main.run (/usr/local/lib/nodemodules/n8n/node_modules/@oclif/command/lib/command.js:43:20)
[WARN tini (7)] Tini is not running as PID 1 and isn't registered as a child subreaper.
Zombie processes will not be re-parented to Tini, so zombie reaping won't work.
To fix the problem, use the -s option or set the environment variable TINI_SUBREAPER to register Tini a
ⓘ Deployment information is only viewable by Project members and Railway admins.
9 Replies
a year ago
5gb / 5gb. This should be the problem, right? :/
There is a way for me to increase it?
a year ago
Yep you are definitely out of disk space, Easily fixed by upgrading to Pro, moving your project over to the Pro workspace when prompted, then you can go into the volumes settings and will have an option to grow the volume to 50gb.
Status changed to Solved railway[bot] • about 1 year ago
a year ago
Ok, thank you so much, brody!
Just asking: there is a way for me to access the DB, backup and delete some stuff?
a year ago
Assuming the database hasn't also ran out of disk space, yes, deploy dbgate into your project and use it to connect to the database!
a year ago
Just upgraded to Pro, but still getting error :'(
Now, it seems to be another error. How can I run a backup? So complicated!
2024-03-30 16:25:14.124 UTC [8] LOG: starting PostgreSQL 15.5 (Ubuntu 15.5-1.pgdg22.04+1) on x86_64-pc-linux-gnu, compiled by gcc (Ubuntu 11.4.0-1ubuntu1~22.04) 11.4.0, 64-bit
2024-03-30 16:25:14.124 UTC [8] LOG: listening on IPv4 address "0.0.0.0", port 5432
2024-03-30 16:25:14.124 UTC [8] LOG: listening on IPv6 address "::", port 5432
2024-03-30 16:25:14.129 UTC [8] LOG: listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-03-30 16:25:14.136 UTC [35] LOG: database system was interrupted while in recovery at 2024-03-30 16:24:21 UTC
2024-03-30 16:25:14.136 UTC [35] HINT: This probably means that some data is corrupted and you will have to use the last backup for recovery.
2024-03-30 16:25:14.185 UTC [35] LOG: database system was not properly shut down; automatic recovery in progress
2024-03-30 16:25:14.188 UTC [35] LOG: redo starts at 1/BC5884C8
2024-03-30 16:25:14.474 UTC [35] LOG: redo done at 1/C0FFF790 system usage: CPU: user: 0.09 s, system: 0.19 s, elapsed: 0.28 s
2024-03-30 16:25:14.476 UTC [35] FATAL: could not write to file "pg_wal/xlogtemp.35": No space left on device
2024-03-30 16:25:14.484 UTC [8] LOG: startup process (PID 35) exited with exit code 1
2024-03-30 16:25:14.484 UTC [8] LOG: terminating any other active server processes
2024-03-30 16:25:14.485 UTC [8] LOG: shutting down due to startup process failure
2024-03-30 16:25:14.499 UTC [8] LOG: database system is shut down
a year ago
Finally working. Thanks so much!