N8n wont deploy after app update - Truenas Scale

tomernassi · March 17, 2025, 7:22pm

After updating the app, the app won’t deploy anymore. I’m adding the logs from the postgres container and n8n container. It is running as an “app” in truneas scale.

postgres logs:

2025-03-17 18:37:33.573093+00:002025-03-17T18:37:33.573093433Z
2025-03-17 18:37:33.573152+00:00PostgreSQL Database directory appears to contain a database; Skipping initialization
2025-03-17 18:37:33.573173+00:002025-03-17T18:37:33.573173786Z
2025-03-17 18:37:33.647604+00:002025-03-17 11:37:33.647 PDT [1] LOG:  starting PostgreSQL 15.12 (Debian 15.12-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2025-03-17 18:37:33.647786+00:002025-03-17 11:37:33.647 PDT [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2025-03-17 18:37:33.647855+00:002025-03-17 11:37:33.647 PDT [1] LOG:  listening on IPv6 address "::", port 5432
2025-03-17 18:37:33.672404+00:002025-03-17 11:37:33.672 PDT [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2025-03-17 18:37:33.703822+00:002025-03-17 11:37:33.703 PDT [16] LOG:  database system was shut down at 2025-03-17 11:36:18 PDT
2025-03-17 18:37:33.831485+00:002025-03-17 11:37:33.831 PDT [1] LOG:  database system is ready to accept connections

n8n logs:

2025-03-17 18:37:41.252159+00:00Permissions 0644 for n8n settings file /data/.n8n/config are too wide. This is ignored for now, but in the future n8n will attempt to change the permissions automatically. To automatically enforce correct permissions now set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=true (recommended), or turn this check off set N8N_ENFORCE_SETTINGS_FILE_PERMISSIONS=false.
2025-03-17 18:37:41.253831+00:00User settings loaded from: /data/.n8n/config
2025-03-17 18:37:42.566781+00:00Initializing n8n process
2025-03-17 18:37:43.334819+00:00n8n ready on 0.0.0.0, port 30109
2025-03-17 18:37:43.721684+00:002025-03-17T18:37:43.721684499Z
2025-03-17 18:37:43.721761+00:00There is a deprecation related to your environment variables. Please take the recommended actions to update your configuration:
2025-03-17 18:37:43.721786+00:00- N8N_RUNNERS_ENABLED -> 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/
2025-03-17 18:37:43.721841+00:002025-03-17T18:37:43.721841738Z
2025-03-17 18:37:48.616731+00:00Found unfinished executions: 639260, 639254
2025-03-17 18:37:48.616838+00:00This could be due to a crash of an active workflow or a restart of n8n.

n8n web UI error:
Cannot GET /

any ideas what could cause the problem? I’m also very new to everything so be nice.

Information on your n8n setup

n8n version: TRUENAS APP 1.84.0
Database (default: SQLite): all defualt
n8n EXECUTIONS_PROCESS setting (default: own, main): all defualt
Running n8n via (Docker, npm, n8n cloud, desktop app): TRUENAS APP ( DOCKER)
Operating system: Truenas Scale

barn4k · March 17, 2025, 7:24pm

hello @tomernassi

wait for a little (a couple of minutes), n8n won’t run instantly.

There are no errors in the logs

tomernassi · March 17, 2025, 7:34pm

No there are some errors, the app takes seconds to load and not hours/days. anyway, you can see in the logs there are two unfinished executions. and the app wont deploy, when you go to the web UI you get the error: Cannot GET / any ideas :)?

Thank you for your help

barn4k · March 17, 2025, 7:57pm

According to the logs, db and n8n were started.

2025-03-17 18:37:33.831485+00:002025-03-17 11:37:33.831 PDT [1] LOG:  database system is ready to accept connections

2025-03-17 18:37:43.334819+00:00n8n ready on 0.0.0.0, port 30109

Do you have more logs? You can set the ENV N8N_LOG_LEVEL=debug for more detailed logs.

tomernassi · March 17, 2025, 8:07pm

ok I added debug logs here:
but the app still doesnt work even if it looks like it deploys, this is what you get from the web UI:

debug logs:

025-03-17 20:05:05.632743+00:00User settings loaded from: /data/.n8n/config
2025-03-17 20:05:07.015287+00:002025-03-17T20:05:07.014Z | e[32minfoe[39m | e[32mInitializing n8n processe[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.154643+00:002025-03-17T20:05:07.154Z | e[34mdebuge[39m | e[34mLazy-loading nodes and credentials from n8n-nodes-basee[39m {"nodes":469,"credentials":379,"file":"lazy-package-directory-loader.js","function":"loadAll"}
2025-03-17 20:05:07.185466+00:002025-03-17T20:05:07.185Z | e[34mdebuge[39m | e[34mLazy-loading nodes and credentials from @n8n/n8n-nodes-langchaine[39m {"nodes":82,"credentials":17,"file":"lazy-package-directory-loader.js","function":"loadAll"}
2025-03-17 20:05:07.493183+00:002025-03-17T20:05:07.492Z | e[32minfoe[39m | e[32mn8n ready on 0.0.0.0, port 30109e[39m {"file":"abstract-server.js","function":"init"}
2025-03-17 20:05:07.569301+00:002025-03-17T20:05:07.568Z | e[34mdebuge[39m | e[34m[license SDK] initializing for deviceFingerprint 50a9427460b28dff14aad9d0be6fc2781c87881e131332db2295b22fdcfbec15e[39m {"scopes":["license"],"file":"LicenseManager.js","function":"log"}
2025-03-17 20:05:07.574739+00:002025-03-17T20:05:07.574Z | e[34mdebuge[39m | e[34m[license SDK] Skipping renewal on init because cert was issued less than 24 hours ago or not initializede[39m {"scopes":["license"],"file":"LicenseManager.js","function":"log"}
2025-03-17 20:05:07.575274+00:002025-03-17T20:05:07.575Z | e[34mdebuge[39m | e[34mLicense initializede[39m {"scopes":["license"],"file":"license.js","function":"init"}
2025-03-17 20:05:07.575649+00:002025-03-17T20:05:07.575Z | e[34mdebuge[39m | e[34mStarted tracking waiting executionse[39m {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"startTracking"}
2025-03-17 20:05:07.576177+00:002025-03-17T20:05:07.575Z | e[34mdebuge[39m | e[34mQuerying database for waiting executionse[39m {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getWaitingExecutions"}
2025-03-17 20:05:07.578813+00:002025-03-17T20:05:07.578Z | e[34mdebuge[39m | e[34mWait tracker init completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.582218+00:002025-03-17T20:05:07.582Z | e[34mdebuge[39m | e[34mBinary data service init completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.582745+00:002025-03-17T20:05:07.582Z | e[34mdebuge[39m | e[34mData deduplication service init completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.583359+00:002025-03-17T20:05:07.583Z | e[34mdebuge[39m | e[34mExternal hooks init completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.599497+00:002025-03-17T20:05:07.599Z | e[34mdebuge[39m | e[34mExternal secrets init completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.600224+00:002025-03-17T20:05:07.599Z | e[34mdebuge[39m | e[34mWorkflow history init completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:07.608511+00:002025-03-17T20:05:07.608Z | e[34mdebuge[39m | e[34mTest runner cleanup completee[39m {"file":"start.js","function":"init"}
2025-03-17 20:05:08.590194+00:002025-03-17T20:05:08.589Z | e[32minfoe[39m | e[32mn8n Task Broker ready on 127.0.0.1, port 5679e[39m {"file":"task-broker-server.js","function":"setupHttpServer"}
2025-03-17 20:05:09.876712+00:002025-03-17T20:05:09.876Z | e[34mdebuge[39m | e[34mInitializing event bus...e[39m {"file":"message-event-bus.js","function":"initialize"}
2025-03-17 20:05:09.879585+00:002025-03-17T20:05:09.879Z | e[34mdebuge[39m | e[34mInitializing event writere[39m {"file":"message-event-bus.js","function":"initialize"}
2025-03-17 20:05:09.907958+00:002025-03-17T20:05:09.907Z | e[34mdebuge[39m | e[34mChecking for unsent event messagese[39m {"file":"message-event-bus.js","function":"initialize"}
2025-03-17 20:05:09.911043+00:002025-03-17T20:05:09.910Z | e[34mdebuge[39m | e[34mStart logging into /data/.n8n/n8nEventLog.log e[39m {"file":"message-event-bus.js","function":"initialize"}
2025-03-17 20:05:09.921712+00:002025-03-17T20:05:09.921Z | e[33mwarne[39m | e[33mFound unfinished executions: 639260, 639254e[39m {"file":"message-event-bus.js","function":"initialize"}
2025-03-17 20:05:09.921858+00:002025-03-17T20:05:09.921Z | e[32minfoe[39m | e[32mThis could be due to a crash of an active workflow or a restart of n8n.e[39m {"file":"message-event-bus.js","function":"initialize"}
2025-03-17 20:05:10.472225+00:002025-03-17T20:05:10.471Z | e[32minfoe[39m | e[32mRegistered runner "JS Task Runner" (5Kc-9TvyzOCcdqBSR37hz) e[39m {"file":"task-broker-ws-server.js","function":"onMessage"}
2025-03-17 20:06:07.577333+00:002025-03-17T20:06:07.576Z | e[34mdebuge[39m | e[34mQuerying database for waiting executionse[39m {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getWaitingExecutions"}

barn4k · March 17, 2025, 8:26pm

Those are the only logs for the last run…

Can you show the content of the /data/.n8n/n8nEventLog.log?

And can you show the docker config for the n8n?

tomernassi · March 17, 2025, 8:46pm

again its not really config as you think of, its an app on truenas so I can show you the app config

tomernassi · March 18, 2025, 1:59am

Hey all, I still need help. im going to lose all my automation and everything I had in my n8n

tomernassi · March 18, 2025, 2:14am

current logs:

2025-03-18 02:11:42.633460+00:002025-03-18T02:11:42.633Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:12:04.634808+00:002025-03-18T02:12:04.634Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:12:07.637581+00:002025-03-18T02:12:07.637Z | e[34mdebuge[39m | e[34mQuerying database for waiting executionse[39m {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getWaitingExecutions"}
2025-03-18 02:12:26.637069+00:002025-03-18T02:12:26.636Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:12:27.639529+00:002025-03-18T02:12:27.639Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:12:48.638875+00:002025-03-18T02:12:48.638Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:13:07.639093+00:002025-03-18T02:13:07.638Z | e[34mdebuge[39m | e[34mQuerying database for waiting executionse[39m {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getWaitingExecutions"}
2025-03-18 02:13:10.640236+00:002025-03-18T02:13:10.639Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:13:27.642452+00:002025-03-18T02:13:27.641Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:13:32.641883+00:002025-03-18T02:13:32.641Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:13:54.642584+00:002025-03-18T02:13:54.642Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}
2025-03-18 02:14:07.639068+00:002025-03-18T02:14:07.638Z | e[34mdebuge[39m | e[34mQuerying database for waiting executionse[39m {"scopes":["waiting-executions"],"file":"wait-tracker.js","function":"getWaitingExecutions"}
2025-03-18 02:14:16.644183+00:002025-03-18T02:14:16.643Z | e[31merrore[39m | e[31mtimeout exceeded when trying to connecte[39m {"file":"error-reporter.js","function":"defaultReport"}```

barn4k · March 18, 2025, 9:37am

Logs doesn’t show anything useful.

Can’t say what is the issue. Plus I’ve never heard of the Truenas Scale service, so can’t remember any topics related to it.

system · June 16, 2025, 9:38am

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.