v2 Migration: N8N - Application failed to respond
After migrating to v2, I can no longer access my N8N installation. Migration seems to have been completed successfully but I have these errors in the log...
[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 as a child subreaper, or run Tini as PID 1.
› Error: command n8n not found
Solution:Jump to solution
maybe deploy a new n8n template? this one specifically https://railway.app/template/r2SNX_
it is the best n8n template...
11 Replies
Project ID:
52b3de4b-70c9-435d-87eb-7216b04622b752b3de4b-70c9-435d-87eb-7216b04622b7
does your n8n service deploy from a docker image or a repository?
repository
do you have important workflows on n8n?
Not really. I have 2 different deployments. One was just for internal testing. The other was for a client but the only workflow there was for an old process we don't use anymore
Solution
maybe deploy a new n8n template? this one specifically https://railway.app/template/r2SNX_
it is the best n8n template
@Brody thank you! That template was super easy to use.
no problem!
Same problem here. However, I do have important workflows on n8n. How to solve that without deploy a new n8n?
open a thread in #🚚｜db-migration-help please