Hi all,
I am using the Hassio Node-Red add-on and it keeps stopping at random times. Usually, it then takes a number of attempts to start it before it finally stays started for a bit. I have tried uninstalling and re-installing it without success. This is the only add-on that I am having trouble with. Here are the logs.
System log:
19-10-19 13:03:45 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/rs1932/ring-alarm-hassio-addon repository
19-10-19 13:03:45 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/home-assistant/hassio-addons repository
19-10-19 13:03:45 INFO (MainThread) [hassio.store.git] Update add-on https://github.com/hassio-addons/repository repository
19-10-19 13:03:48 INFO (MainThread) [hassio.store] Load add-ons from store: 61 all - 0 new - 0 remove
19-10-19 13:06:49 INFO (SyncWorker_3) [hassio.docker.interface] Clean addon_a0d7b954_nodered application
19-10-19 13:06:51 WARNING (SyncWorker_9) [hassio.docker.interface] Can't grep logs from hassioaddons/node-red-armv7: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-10-19 13:06:53 WARNING (SyncWorker_19) [hassio.docker.interface] Can't grep logs from hassioaddons/node-red-armv7: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-10-19 13:06:54 WARNING (SyncWorker_0) [hassio.docker.interface] Can't grep logs from hassioaddons/node-red-armv7: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-10-19 13:06:54 WARNING (SyncWorker_10) [hassio.docker.interface] Can't grep logs from hassioaddons/node-red-armv7: 409 Client Error: Conflict ("can not get logs from container which is dead or marked for removal")
19-10-19 13:07:38 INFO (SyncWorker_3) [hassio.docker.addon] Start Docker add-on hassioaddons/node-red-armv7 with version 5.0.0
19-10-19 13:07:57 INFO (MainThread) [hassio.api.security] /host/info access from a0d7b954_nodered
19-10-19 13:08:01 INFO (MainThread) [hassio.api.security] /dns/info access from a0d7b954_nodered
19-10-19 13:08:09 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64673 ssl:None [Connection refused]
19-10-19 13:08:12 ERROR (MainThread) [hassio.api.ingress] Ingress error: Cannot connect to host 172.30.32.1:64673 ssl:None [Connection refused]
19-10-19 13:17:05 INFO (MainThread) [hassio.host.info] Update local host information
19-10-19 13:17:05 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/hostname1
19-10-19 13:17:12 INFO (MainThread) [hassio.host.services] Update service information
19-10-19 13:17:12 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.systemd1.Manager.ListUnits on /org/freedesktop/systemd1
19-10-19 13:17:12 INFO (MainThread) [hassio.host.network] Update local network DNS information
19-10-19 13:17:12 INFO (MainThread) [hassio.utils.gdbus] Call org.freedesktop.DBus.Properties.GetAll on /org/freedesktop/NetworkManager/DnsManager
Node-Red add-on log files:
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing...
-----------------------------------------------------------
Hass.io Add-on: Node-RED
Flow-based programming for the Internet of Things
-----------------------------------------------------------
Add-on version: 5.0.0
You are running the latest version of this add-on.
System: HassOS 3.3 (armv7 / raspberrypi4)
Home Assistant version: 0.100.2
Supervisor version: 189
-----------------------------------------------------------
Please, share the above information when looking for help
or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing...
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing...
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] node-red.sh: executing...
patching file nodes/ui_base.html
Hunk #1 succeeded at 1243 (offset 712 lines).
audited 218 packages in 23.054s
found 0 vulnerabilities
[cont-init.d] node-red.sh: exited 0.
[cont-init.d] user.sh: executing...
[cont-init.d] user.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[09:10:58] INFO: Starting Node-RED...
> hassio-addon-node-red@ start /opt
> node $NODE_OPTIONS node_modules/node-red/red.js "--settings" "/etc/node-red/config.js"
19 Oct 09:12:19 - [info]
Welcome to Node-RED
===================
19 Oct 09:12:20 - [info] Node-RED version: v1.0.2
19 Oct 09:12:20 - [info] Node.js version: v10.16.3
19 Oct 09:12:20 - [info] Linux 4.19.58-v7l arm LE
19 Oct 09:12:21 - [info] Loading palette nodes
Terminated
[cont-finish.d] executing container finish scripts...
[cont-finish.d] 99-message.sh: executing...
[cont-finish.d] 99-message.sh: exited 0.
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
Any insight and help would be greatly appreciated.
