2 months ago
Hi guys
I have a problem here that I can't solve. Please help me 😕
Yesterday I tried applying cron scheduling to n8n, within the 'with workers' package of 'Jack', but it didn't work as I expected. So, I removed cron and applied redeploy, however this failed and I can no longer access n8n.
I tried to 'restart' the deployment that failed and I also tried to redeploy a previous version of the history, the latter worked but when I entered n8n a message appeared saying that it was not possible to start the application.
With this, the n8n worker module also crashed.
It kept repeating the timeout error until the deployment failed definitively.
Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DBPOSTGRESDBCONNECTION_TIMEOUT' environment variable.
Error: Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DBPOSTGRESDBCONNECTION_TIMEOUT' environment variable.
Here are some prints of the log
Project ID: 76e5c2ab-2d85-42d6-8d15-c66ae8c191b8
0 Replies
2 months ago
Sounds like you’re using a template. Please send a link to the template
2 months ago
may I ask why you have applied a Cron to these services?
i was trying to rerduce de usage, for somehow, even when there were no active worflows the price was getting high lol
i just start making some workflows, and i didn't know wht i was doing actualy 🫠
@Adam let me know if this link is the correct
https://railway.com/new/template/r2SNX_?teamId=b8b29e87-1ed2-43a7-a203-7f0239e3dae7
tha logs ended like this:
Last session crashed
Initializing n8n process
There was an error initializing DB
Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DBPOSTGRESDBCONNECTION_TIMEOUT' environment variable.
Error: Could not establish database connection within the configured timeout of 20,000 ms. Please ensure the database is configured correctly and the server is reachable. You can increase the timeout by setting the 'DBPOSTGRESDBCONNECTION_TIMEOUT' environment variable.
at Object.init (/usr/local/lib/node_modules/n8n/dist/db.js:57:21) at processTicksAndRejections (node:internal/process/task_queues:95:5) at Start.init (/usr/local/lib/node_modules/n8n/dist/commands/base-command.js:98:9) at Start.init (/usr/local/lib/node_modules/n8n/dist/commands/start.js:159:9) at Start._run (/usr/local/lib/node_modules/n8n/node_modules/@oclif/core/lib/command.js:301:13) at Config.runCommand (/usr/local/lib/node_modules/n8n/node_modules/@oclif/core/lib/config/config.js:424:25) at run (/usr/local/lib/node_modules/n8n/node_modules/@oclif/core/lib/main.js:94:16) at /usr/local/lib/node_modules/n8n/bin/n8n:71:2
Connection terminated due to connection timeout
Connection terminated unexpectedly
User settings loaded from: /home/node/.n8n/config
Last session crashed
Stopping Container
2 months ago
I think you are mixing up cron and serverless.
please remove all the Cron config.
well.. strange.. i tried to redeploy now with no changes and it worked.
i dont know why, but i'll leave here de logs. hope i can undestand what happened
Starting Container
Initializing n8n process
n8n ready on ::, port 5678
There are deprecations related to your environment variables. Please take the recommended actions to update your configuration:
N8NRUNNERSENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a future version. Please set
N8N_RUNNERS_ENABLED=true
to enable task runners now and avoid potential issues in the future. Learn more: https://docs.n8n.io/hosting/configuration/task-runners/OFFLOADMANUALEXECUTIONSTOWORKERS -> Running manual executions in the main instance in scaling mode is deprecated. Manual executions will be routed to workers in a future version. Please set
OFFLOAD_MANUAL_EXECUTIONS_TO_WORKERS=true
to offload manual executions to workers and avoid potential issues in the future. Consider increasing memory available to workers and reducing memory available to main.Version: 1.86.1
================================
Start Active Workflows:
================================
"Notificações Mandaê" (ID: 9Yjyb9qH07kbhhBd))
=> Started
"Notifica atrasos fabrica" (ID: 0Up1bk6tvJmjtaDc))
=> Started
"Update Loja Leblon Supabase" (ID: kg9JKYpStl5ucEbW))
=> Started
"Update Supabase" (ID: tI33bZDVPQvThBPj))
=> Started
"Update Loja Leblon Sheets" (ID: uuwRSLepXlFqo9rk))
=> Started
Editor is now accessible via:
2 months ago
looks fine to me now, are you sure you have active deployments on all services now?
all good, i tested one of the workflows ✨
do i have to worry about these recommendations?
There are deprecations related to your environment variables. Please take the recommended actions to update your configuration:
N8NRUNNERSENABLED -> Running n8n without task runners is deprecated. Task runners will be turned on by default in a future version. Please set N8NRUNNERSENABLED=true to enable task runners now and avoid potential issues in the future. Learn more: https://docs.n8n.io/hosting/configuration/task-runners/
OFFLOADMANUALEXECUTIONSTOWORKERS -> Running manual executions in the main instance in scaling mode is deprecated. Manual executions will be routed to workers in a future version. Please set OFFLOADMANUALEXECUTIONSTOWORKERS=true to offload manual executions to workers and avoid potential issues in the future. Consider increasing memory available to workers and reducing memory available to main.
2 months ago
you would need to ask that question in an N8N forum sorry, I don't have any experience with the n8n software.
no problems, i appreciate your help though 🙏🏼
i think it was related to some updates that n8n made
even though, i'll try to reach them
thanks again!
2 months ago
no problem!
2 months ago
!s
Status changed to Solved brody • about 2 months ago