Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

After update, Node-Red cant start. #1876

Closed
IkaSGC opened this issue Apr 21, 2024 · 3 comments
Closed

After update, Node-Red cant start. #1876

IkaSGC opened this issue Apr 21, 2024 · 3 comments
Labels
stale There has not been activity on this issue or PR for quite some time.

Comments

@IkaSGC
Copy link

IkaSGC commented Apr 21, 2024

Problem/Motivation

Impossible start Node-Red

Expected behavior

Start Node-Red

Actual behavior

Wont start due to error

Steps to reproduce

None

Proposed changes

None

Error:

`Welcome to Node-RED

21 Apr 12:18:43 - [info] Node-RED version: v3.1.9
21 Apr 12:18:43 - [info] Node.js version: v18.20.2
21 Apr 12:18:43 - [info] Linux 6.6.25-haos x64 LE
21 Apr 12:18:44 - [info] Loading palette nodes
21 Apr 12:18:45 - [info] Dashboard version 3.6.5 started at /endpoint/ui
21 Apr 12:18:45 - [warn] ------------------------------------------------------
21 Apr 12:18:45 - [warn] [node-red-hxtx-ftp/ftp] 'ftp in' already registered by module node-red-contrib-ftp-beta
21 Apr 12:18:45 - [warn] ------------------------------------------------------
21 Apr 12:18:45 - [info] Settings file : /etc/node-red/config.js
21 Apr 12:18:45 - [info] Context store : 'default' [module=memory]
21 Apr 12:18:45 - [info] User directory : /config/
21 Apr 12:18:45 - [warn] Projects disabled : editorTheme.projects.enabled=false
21 Apr 12:18:45 - [info] Flows file : /config/flows.json
21 Apr 12:18:45 - [info] Server now running at http://127.0.0.1:46836/
21 Apr 12:18:45 - [info] Starting flows
21 Apr 12:18:45 - [info] Started flows
[12:18:45] INFO: Starting NGinx...
21 Apr 12:18:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connecting to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connected to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connected to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connected to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connected to http://supervisor/core
21 Apr 12:18:50 - [info] [server:Home Assistant] Connected to http://supervisor/core
21 Apr 12:19:05 - [red] Uncaught Exception:
21 Apr 12:19:05 - [error] Error: Timeout while connecting to server
at Timeout._onTimeout (/config/node_modules/ftp/lib/connection.js:304:24)
at listOnTimeout (node:internal/timers:569:17)
at processTimers (node:internal/timers:512:7)
[12:19:05] INFO: Service Node-RED exited with code 1 (by signal 0)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service nginx: stopping
[12:19:05] INFO: Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service init-nginx: stopping
s6-rc: info: service nodered: stopping
s6-rc: info: service init-nginx successfully stopped
s6-rc: info: service nodered successfully stopped
s6-rc: info: service init-nodered: stopping
s6-rc: info: service init-nodered successfully stopped
s6-rc: info: service init-customizations: stopping
s6-rc: info: service init-customizations successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service base-addon-log-level: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service base-addon-log-level successfully stopped
s6-rc: info: service base-addon-banner: stopping
s6-rc: info: service base-addon-banner successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped`

@tjorim
Copy link
Contributor

tjorim commented Apr 21, 2024

Error: Timeout while connecting to server at Timeout._onTimeout (/config/node_modules/ftp/lib/connection.js:304:24) <- Seems to be an issue with the FTP node you set up, thus out of scope for the add-on. Try enabling safe_mode in the add-on config and fix the flow.

@IkaSGC
Copy link
Author

IkaSGC commented Apr 22, 2024

The error was somewhere in HA, but I have no idea where. The whole HA started behaving unstable. Some add-ons could not be started. Node-Red started and was available, but when I clicked on the add-on in settings, it said it was not running and could not be started, but all NR tasks were still running. Other add-ons could not be started at all.
The same thing happened after restoring from a backup. Only restoring from a backup to a new clean installation helped.

Copy link

There hasn't been any activity on this issue recently, so we clean up some of the older and inactive issues.
Please make sure to update to the latest version and check if that solves the issue. Let us know if that works for you by leaving a comment 👍
This issue has now been marked as stale and will be closed if no further activity occurs. Thanks!

@github-actions github-actions bot added the stale There has not been activity on this issue or PR for quite some time. label May 23, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale May 30, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
stale There has not been activity on this issue or PR for quite some time.
Projects
None yet
Development

No branches or pull requests

2 participants