Node Red. Gone cyclic after loading a Hue Node

I have just loaded a Hue Node into NR.
Since I have done this NR is unavailable.
The logs seem to be indicating that it is trying to run but cannot.
I have tried a oll-node-red --stop / start to no avail.
Here are the logs.
Any ideas how to get out of MY mess. I was thinking of doing a restore of a backup but thought I would ask here first.
BTW I have updated to the latest update that was released. Not sure if this updated NR or not.

Logs

login as: oh-la
[email protected]’s password:
Linux Collective-Core 5.16.0 #1 SMP PREEMPT Tue Jan 18 16:29:35 UTC 2022 aarch64
█▀▀ █▀█ █░░ █░░ █▀▀ █▀▀ ▀█▀ █ █░█ █▀▀ █▀▀ █▀█ █▀█ █▀▀
█▄▄ █▄█ █▄▄ █▄▄ ██▄ █▄▄ ░█░ █ ▀▄▀ ██▄ █▄▄ █▄█ █▀▄ ██▄

𝗯𝘆 𝗢𝗵-𝗟𝗮 𝗟𝗮𝗯𝘀

Marjebian is based on Debian with full support for the official Debian APT sources!
Image version: v1.8.2.0727
Booted from eMMC!
For additional help, run “oll-help --help”.
Last login: Sat Aug 20 17:45:49 2022 from 192.168.0.10
[email protected]:~$ sudo oll-node-red --logs
[sudo] password for oh-la:
INFO: Running command: logs
INFO: Running: journalctl -u podman-oll-node-red.service -f -n 100
INFO: Displaying the last 100 lines and following the logs for podman-oll-node-red.service:
– Journal begins at Mon 2022-08-15 10:30:00 BST. –
Aug 20 17:58:08 Collective-Core oll-node-red[2025064]: time=“2022-08-20T17:58:08+01:00” level=info msg=“Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument”
Aug 20 17:58:08 Collective-Core oll-node-red[2025064]: time=“2022-08-20T17:58:08+01:00” level=info msg=“Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument”
Aug 20 17:58:08 Collective-Core oll-node-red[2025064]: time=“2022-08-20T17:58:08+01:00” level=info msg=“Setting parallel job count to 13”
Aug 20 17:58:09 Collective-Core podman[2025064]: 2022-08-20 17:58:09.089602233 +0100 BST m=+0.299230992 container create 4294d1b821b11b55006477634ba646ae46e2c534ad5a46bb4a0614968d9bb1e5 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.url=https://nodered.org, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.name=Node-RED, org.label-schema.version=, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.arch=arm64v8, org.label-schema.license=Apache-2.0, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.vcs-ref=, org.label-schema.vcs-type=Git)
Aug 20 17:58:09 Collective-Core oll-node-red[2025064]: time=“2022-08-20T17:58:09+01:00” level=info msg=“Got Conmon PID as 2025105”
Aug 20 17:58:09 Collective-Core podman[2025064]: 2022-08-20 17:58:09.627632271 +0100 BST m=+0.837261071 container init 4294d1b821b11b55006477634ba646ae46e2c534ad5a46bb4a0614968d9bb1e5 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.arch=arm64v8, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.url=https://nodered.org, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.license=Apache-2.0, org.label-schema.vcs-ref=, org.label-schema.version=, org.label-schema.vcs-type=Git, org.label-schema.name=Node-RED)
Aug 20 17:58:09 Collective-Core podman[2025064]: 2022-08-20 17:58:09.645367643 +0100 BST m=+0.854996402 container start 4294d1b821b11b55006477634ba646ae46e2c534ad5a46bb4a0614968d9bb1e5 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.version=, org.label-schema.vcs-type=Git, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.license=Apache-2.0, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.arch=arm64v8, org.label-schema.url=https://nodered.org, org.label-schema.vcs-ref=, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.name=Node-RED, org.label-schema.description=Low-code programming for event-driven applications.)
Aug 20 17:58:09 Collective-Core oll-node-red[2025064]: 4294d1b821b11b55006477634ba646ae46e2c534ad5a46bb4a0614968d9bb1e5
Aug 20 17:58:09 Collective-Core systemd[1]: Started Node-RED in Podman (CORE).
Aug 20 17:58:09 Collective-Core conmon[2025105]: Unsafe permissions (740), run “chmod go-rwx /data/configure_oll-node-red.sh”
Aug 20 17:58:11 Collective-Core conmon[2025105]:
Aug 20 17:58:11 Collective-Core conmon[2025105]: > [email protected] start /usr/src/node-red
Aug 20 17:58:11 Collective-Core conmon[2025105]: > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS “–userDir” “/data/node-red”
Aug 20 17:58:11 Collective-Core conmon[2025105]:
Aug 20 17:58:14 Collective-Core conmon[2025105]: 20 Aug 17:58:14 - [info]
Aug 20 17:58:14 Collective-Core conmon[2025105]:
Aug 20 17:58:14 Collective-Core conmon[2025105]: Welcome to Node-RED
Aug 20 17:58:14 Collective-Core conmon[2025105]: ===================
Aug 20 17:58:14 Collective-Core conmon[2025105]:
Aug 20 17:58:14 Collective-Core conmon[2025105]: 20 Aug 17:58:14 - [info] Node-RED version: v2.2.3
Aug 20 17:58:14 Collective-Core conmon[2025105]: 20 Aug 17:58:14 - [info] Node.js version: v14.19.1
Aug 20 17:58:14 Collective-Core conmon[2025105]: 20 Aug 17:58:14 - [info] Linux 5.16.0 arm64 LE
Aug 20 17:58:15 Collective-Core conmon[2025105]: 20 Aug 17:58:15 - [info] Loading palette nodes
Aug 20 17:58:21 Collective-Core conmon[2025105]: 20 Aug 17:58:21 - [info] Settings file : /data/node-red/settings.js
Aug 20 17:58:21 Collective-Core conmon[2025105]: 20 Aug 17:58:21 - [info] Context store : ‘ram’ [module=memory]
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] Context store : ‘file’ [module=localfilesystem]
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] User directory : /data/node-red
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [warn] Projects disabled : editorTheme.projects.enabled=false
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] Flows file : /data/node-red/flows.json
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] Server now running at http://127.0.0.1:1880/
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [warn]
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: ---------------------------------------------------------------------
Aug 20 17:58:22 Collective-Core conmon[2025105]: Your flow credentials file is encrypted using a system-generated key.
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: If the system-generated key is lost for any reason, your credentials
Aug 20 17:58:22 Collective-Core conmon[2025105]: file will not be recoverable, you will have to delete it and re-enter
Aug 20 17:58:22 Collective-Core conmon[2025105]: your credentials.
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: You should set your own key using the ‘credentialSecret’ option in
Aug 20 17:58:22 Collective-Core conmon[2025105]: your settings file. Node-RED will then re-encrypt your credentials
Aug 20 17:58:22 Collective-Core conmon[2025105]: file using your chosen key the next time you deploy a change.
Aug 20 17:58:22 Collective-Core conmon[2025105]: ---------------------------------------------------------------------
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] Starting flows
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] Started flows
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] [zigbee2mqtt-server:CORE] MQTT Connected
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] [zigbee2mqtt-server:CORE] Refreshing devices
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] [hubitat config:#1 C7] Websocket connected
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] [zigbee2mqtt-server:CORE] MQTT Subscribed to: “zigbee2mqtt/#
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [info] [zigbee2mqtt-server:CORE] Refreshing devices
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [red] Uncaught Exception:
Aug 20 17:58:22 Collective-Core conmon[2025105]: 20 Aug 17:58:22 - [error] Api Error: Unexpected response status; 404
Aug 20 17:58:22 Collective-Core conmon[2025105]: at requireStatusCode200 (/data/node-red/node_modules/node-hue-api/hue-api/httpPromise.js:100:15)
Aug 20 17:58:22 Collective-Core conmon[2025105]: at _fulfilled (/data/node-red/node_modules/q/q.js:787:54)
Aug 20 17:58:22 Collective-Core conmon[2025105]: at /data/node-red/node_modules/q/q.js:816:30
Aug 20 17:58:22 Collective-Core conmon[2025105]: at Promise.promise.promiseDispatch (/data/node-red/node_modules/q/q.js:749:13)
Aug 20 17:58:22 Collective-Core conmon[2025105]: at /data/node-red/node_modules/q/q.js:557:44
Aug 20 17:58:22 Collective-Core conmon[2025105]: at flush (/data/node-red/node_modules/q/q.js:108:17)
Aug 20 17:58:22 Collective-Core conmon[2025105]: at processTicksAndRejections (internal/process/task_queues.js:77:11)
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: code ELIFECYCLE
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]: errno
Aug 20 17:58:22 Collective-Core conmon[2025105]: 1
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR! [email protected] start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data/node-red"
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]: Exit status 1
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]: Failed at the [email protected] start script.
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]: This is probably not a problem with npm. There is likely additional logging output above.
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]:
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]: A complete log of this run can be found in:
Aug 20 17:58:22 Collective-Core conmon[2025105]: npm
Aug 20 17:58:22 Collective-Core conmon[2025105]: ERR!
Aug 20 17:58:22 Collective-Core conmon[2025105]: /data/node-red/.npm/_logs/2022-08-20T16_58_22_742Z-debug.log
Aug 20 17:58:22 Collective-Core podman[2025148]: 2022-08-20 17:58:22.962111655 +0100 BST m=+0.149745910 container died 4294d1b821b11b55006477634ba646ae46e2c534ad5a46bb4a0614968d9bb1e5 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red)
Aug 20 17:58:23 Collective-Core podman[2025148]: 2022-08-20 17:58:23.121495023 +0100 BST m=+0.309129237 container remove 4294d1b821b11b55006477634ba646ae46e2c534ad5a46bb4a0614968d9bb1e5 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.vcs-ref=, org.label-schema.vcs-type=Git, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.arch=arm64v8, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.name=Node-RED, org.label-schema.url=https://nodered.org, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.license=Apache-2.0, org.label-schema.version=)
Aug 20 17:58:23 Collective-Core systemd[1]: podman-oll-node-red.service: Main process exited, code=exited, status=1/FAILURE
Aug 20 17:58:23 Collective-Core oll-node-red[2025164]: Error: no arguments are needed with --latest or --cidfile
Aug 20 17:58:23 Collective-Core systemd[1]: podman-oll-node-red.service: Control process exited, code=exited, status=125/n/a
Aug 20 17:58:23 Collective-Core systemd[1]: podman-oll-node-red.service: Failed with result ‘exit-code’.
Aug 20 17:58:23 Collective-Core systemd[1]: podman-oll-node-red.service: Consumed 7.391s CPU time.
Aug 20 17:58:53 Collective-Core systemd[1]: podman-oll-node-red.service: Scheduled restart job, restart counter is at 16.
Aug 20 17:58:53 Collective-Core systemd[1]: Stopped Node-RED in Podman (CORE).
Aug 20 17:58:53 Collective-Core systemd[1]: podman-oll-node-red.service: Consumed 7.391s CPU time.
Aug 20 17:58:53 Collective-Core systemd[1]: Starting Node-RED in Podman (CORE)…
Aug 20 17:58:53 Collective-Core oll-node-red[2025232]: INFO: Running command: update
Aug 20 17:58:53 Collective-Core oll-node-red[2025232]: INFO: Done!
Aug 20 17:58:53 Collective-Core oll-node-red[2025232]: INFO: We are root, becoming the core-services user instead…
Aug 20 17:58:53 Collective-Core oll-node-red[2025232]: INFO: Running “oll-node-red --update” as user core-services
Aug 20 17:58:53 Collective-Core su[2025257]: (to core-services) root on none
Aug 20 17:58:53 Collective-Core su[2025257]: pam_unix(su-l:session): session opened for user core-services(uid=1000) by (uid=0)
Aug 20 17:58:53 Collective-Core oll-node-red[2025257]: INFO: Running command: update
Aug 20 17:58:53 Collective-Core oll-node-red[2025257]: INFO: Running as required user core-services
Aug 20 17:58:54 Collective-Core oll-node-red[2025257]: INFO: Updating the Node-RED container…
Aug 20 17:58:54 Collective-Core oll-node-red[2025257]: Trying to pull container.oh-lalabs.com/oh-lalabs/node-red:stable
Aug 20 17:58:55 Collective-Core oll-node-red[2025330]: INFO: Running command: prepare
Aug 20 17:58:55 Collective-Core oll-node-red[2025330]: INFO: Executing the first part of prepare as root
Aug 20 17:58:55 Collective-Core oll-node-red[2025330]: INFO: podman has the correct capabilities set
Aug 20 17:58:57 Collective-Core oll-node-red[2025330]: INFO: Done!
Aug 20 17:58:57 Collective-Core oll-node-red[2025330]: INFO: We are root, becoming the core-services user instead…
Aug 20 17:58:57 Collective-Core oll-node-red[2025330]: INFO: Running “oll-node-red --prepare” as user core-services
Aug 20 17:58:57 Collective-Core su[2025384]: (to core-services) root on none
Aug 20 17:58:57 Collective-Core su[2025384]: pam_unix(su-l:session): session opened for user core-services(uid=1000) by (uid=0)
Aug 20 17:58:57 Collective-Core oll-node-red[2025384]: INFO: Running command: prepare
Aug 20 17:58:57 Collective-Core oll-node-red[2025384]: INFO: Running as required user core-services
Aug 20 17:58:57 Collective-Core oll-node-red[2025384]: INFO: Finalizing preparing for the Node-RED container as the podman user…
Aug 20 17:58:57 Collective-Core oll-node-red[2025384]: Container oll-node-red was not removed since it didn’t exist anwyay! All is well…
Aug 20 17:59:03 Collective-Core oll-node-red[2025764]: INFO: Running command: defaults
Aug 20 17:59:03 Collective-Core oll-node-red[2025764]: INFO: Running as required user core-services
Aug 20 17:59:03 Collective-Core oll-node-red[2025787]: INFO: Running command: run
Aug 20 17:59:03 Collective-Core oll-node-red[2025787]: INFO: Running as required user core-services
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Running the Node-RED container… Should ONLY be run through a systemd service!
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Exporting all serial devices to the container
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Mapping ports: 127.0.0.1:1880:1880
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Mapping ports: 10.10.2.1:1880:1880
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Mapping folders: /home/core-services/data:/data
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Mapping folders: /etc/ssl/certs:/etc/ssl/certs:ro
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Mapping folders: /usr/local/share/ca-certificates:/usr/local/share/ca-certificates:ro
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: INFO: Mapping enviroment var: NODE_EXTRA_CA_CERTS=/etc/ssl/certs/ca-certificates.crt
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: time=“2022-08-20T17:59:04+01:00” level=info msg=”/usr/bin/podman filtering at log level info"
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: time=“2022-08-20T17:59:04+01:00” level=info msg=“Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument”
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: time=“2022-08-20T17:59:04+01:00” level=info msg=“Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument”
Aug 20 17:59:04 Collective-Core oll-node-red[2025787]: time=“2022-08-20T17:59:04+01:00” level=info msg=“Setting parallel job count to 13”
Aug 20 17:59:04 Collective-Core oll-node-red[2025865]: time=“2022-08-20T17:59:04+01:00” level=info msg=“/usr/bin/podman filtering at log level info”
Aug 20 17:59:04 Collective-Core oll-node-red[2025865]: time=“2022-08-20T17:59:04+01:00” level=info msg=“Error initializing configured OCI runtime runc: no valid executable found for OCI runtime runc: invalid argument”
Aug 20 17:59:04 Collective-Core oll-node-red[2025865]: time=“2022-08-20T17:59:04+01:00” level=info msg=“Error initializing configured OCI runtime kata: no valid executable found for OCI runtime kata: invalid argument”
Aug 20 17:59:04 Collective-Core oll-node-red[2025865]: time=“2022-08-20T17:59:04+01:00” level=info msg=“Setting parallel job count to 13”
Aug 20 17:59:05 Collective-Core podman[2025865]: 2022-08-20 17:59:05.015238004 +0100 BST m=+0.357268651 container create 09563ca8e56baad1d877c1c9a99f88cd6f3f10705d061ca5d8a59b70da382ae1 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.vcs-ref=, org.label-schema.license=Apache-2.0, org.label-schema.name=Node-RED, org.label-schema.vcs-type=Git, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.arch=arm64v8, org.label-schema.version=, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.url=https://nodered.org, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.description=Low-code programming for event-driven applications., PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service)
Aug 20 17:59:05 Collective-Core oll-node-red[2025865]: time=“2022-08-20T17:59:05+01:00” level=info msg=“Got Conmon PID as 2025905”
Aug 20 17:59:05 Collective-Core podman[2025865]: 2022-08-20 17:59:05.560412341 +0100 BST m=+0.902442988 container init 09563ca8e56baad1d877c1c9a99f88cd6f3f10705d061ca5d8a59b70da382ae1 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.url=https://nodered.org, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.name=Node-RED, org.label-schema.vcs-type=Git, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.arch=arm64v8, org.label-schema.vcs-ref=, org.label-schema.license=Apache-2.0, org.label-schema.version=, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related)
Aug 20 17:59:05 Collective-Core podman[2025865]: 2022-08-20 17:59:05.577499513 +0100 BST m=+0.919530160 container start 09563ca8e56baad1d877c1c9a99f88cd6f3f10705d061ca5d8a59b70da382ae1 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.name=Node-RED, org.label-schema.url=https://nodered.org, org.label-schema.version=, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.arch=arm64v8, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.vcs-ref=, org.label-schema.license=Apache-2.0, org.label-schema.vcs-type=Git, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.build-date=2022-08-15T17:21:38Z)
Aug 20 17:59:05 Collective-Core oll-node-red[2025865]: 09563ca8e56baad1d877c1c9a99f88cd6f3f10705d061ca5d8a59b70da382ae1
Aug 20 17:59:05 Collective-Core systemd[1]: Started Node-RED in Podman (CORE).
Aug 20 17:59:05 Collective-Core conmon[2025905]: Unsafe permissions (740), run “chmod go-rwx /data/configure_oll-node-red.sh”
Aug 20 17:59:07 Collective-Core conmon[2025905]:
Aug 20 17:59:07 Collective-Core conmon[2025905]: > [email protected] start /usr/src/node-red
Aug 20 17:59:07 Collective-Core conmon[2025905]: > node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS “–userDir” “/data/node-red”
Aug 20 17:59:07 Collective-Core conmon[2025905]:
Aug 20 17:59:10 Collective-Core conmon[2025905]: 20 Aug 17:59:10 - [info]
Aug 20 17:59:10 Collective-Core conmon[2025905]:
Aug 20 17:59:10 Collective-Core conmon[2025905]: Welcome to Node-RED
Aug 20 17:59:10 Collective-Core conmon[2025905]: ===================
Aug 20 17:59:10 Collective-Core conmon[2025905]:
Aug 20 17:59:10 Collective-Core conmon[2025905]: 20 Aug 17:59:10 - [info] Node-RED version: v2.2.3
Aug 20 17:59:10 Collective-Core conmon[2025905]: 20 Aug 17:59:10 - [info] Node.js version: v14.19.1
Aug 20 17:59:10 Collective-Core conmon[2025905]: 20 Aug 17:59:10 - [info] Linux 5.16.0 arm64 LE
Aug 20 17:59:11 Collective-Core conmon[2025905]: 20 Aug 17:59:11 - [info] Loading palette nodes
Aug 20 17:59:17 Collective-Core conmon[2025905]: 20 Aug 17:59:17 - [info] Settings file : /data/node-red/settings.js
Aug 20 17:59:17 Collective-Core conmon[2025905]: 20 Aug 17:59:17 - [info] Context store : ‘ram’ [module=memory]
Aug 20 17:59:17 Collective-Core conmon[2025905]: 20 Aug 17:59:17 - [info] Context store : ‘file’ [module=localfilesystem]
Aug 20 17:59:17 Collective-Core conmon[2025905]: 20 Aug 17:59:17 - [info] User directory : /data/node-red
Aug 20 17:59:17 Collective-Core conmon[2025905]: 20 Aug 17:59:17 - [warn] Projects disabled : editorTheme.projects.enabled=false
Aug 20 17:59:17 Collective-Core conmon[2025905]: 20 Aug 17:59:17 - [info] Flows file : /data/node-red/flows.json
Aug 20 17:59:18 Collective-Core conmon[2025905]: 20 Aug 17:59:18 - [info] Server now running at http://127.0.0.1:1880/
Aug 20 17:59:18 Collective-Core conmon[2025905]: 20 Aug 17:59:18 - [warn]
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: ---------------------------------------------------------------------
Aug 20 17:59:18 Collective-Core conmon[2025905]: Your flow credentials file is encrypted using a system-generated key.
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: If the system-generated key is lost for any reason, your credentials
Aug 20 17:59:18 Collective-Core conmon[2025905]: file will not be recoverable, you will have to delete it and re-enter
Aug 20 17:59:18 Collective-Core conmon[2025905]: your credentials.
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: You should set your own key using the ‘credentialSecret’ option in
Aug 20 17:59:18 Collective-Core conmon[2025905]: your settings file. Node-RED will then re-encrypt your credentials
Aug 20 17:59:18 Collective-Core conmon[2025905]: file using your chosen key the next time you deploy a change.
Aug 20 17:59:18 Collective-Core conmon[2025905]: ---------------------------------------------------------------------
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: 20 Aug 17:59:18 - [info] Starting flows
Aug 20 17:59:18 Collective-Core conmon[2025905]: 20 Aug 17:59:18 - [info] Started flows
Aug 20 17:59:18 Collective-Core conmon[2025905]: 20 Aug 17:59:18 - [red] Uncaught Exception:
Aug 20 17:59:18 Collective-Core conmon[2025905]: 20 Aug 17:59:18 - [error] Api Error: Unexpected response status; 404
Aug 20 17:59:18 Collective-Core conmon[2025905]: at requireStatusCode200 (/data/node-red/node_modules/node-hue-api/hue-api/httpPromise.js:100:15)
Aug 20 17:59:18 Collective-Core conmon[2025905]: at _fulfilled (/data/node-red/node_modules/q/q.js:787:54)
Aug 20 17:59:18 Collective-Core conmon[2025905]: at /data/node-red/node_modules/q/q.js:816:30
Aug 20 17:59:18 Collective-Core conmon[2025905]: at Promise.promise.promiseDispatch (/data/node-red/node_modules/q/q.js:749:13)
Aug 20 17:59:18 Collective-Core conmon[2025905]: at /data/node-red/node_modules/q/q.js:557:44
Aug 20 17:59:18 Collective-Core conmon[2025905]: at flush (/data/node-red/node_modules/q/q.js:108:17)
Aug 20 17:59:18 Collective-Core conmon[2025905]: at processTicksAndRejections (internal/process/task_queues.js:77:11)
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR!
Aug 20 17:59:18 Collective-Core conmon[2025905]: code ELIFECYCLE
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR!
Aug 20 17:59:18 Collective-Core conmon[2025905]: errno
Aug 20 17:59:18 Collective-Core conmon[2025905]: 1
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR! [email protected] start: node $NODE_OPTIONS node_modules/node-red/red.js $FLOWS "--userDir" "/data/node-red"
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR!
Aug 20 17:59:18 Collective-Core conmon[2025905]: Exit status 1
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR!
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR!
Aug 20 17:59:18 Collective-Core conmon[2025905]: Failed at the [email protected] start script.
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR!
Aug 20 17:59:18 Collective-Core conmon[2025905]: This is probably not a problem with npm. There is likely additional logging output above.
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]:
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR! A complete log of this run can be found in:
Aug 20 17:59:18 Collective-Core conmon[2025905]: npm
Aug 20 17:59:18 Collective-Core conmon[2025905]: ERR! /data/node-red/.npm/_logs/2022-08-20T16_59_18_729Z-debug.log
Aug 20 17:59:18 Collective-Core podman[2025949]: 2022-08-20 17:59:18.940077221 +0100 BST m=+0.157555441 container died 09563ca8e56baad1d877c1c9a99f88cd6f3f10705d061ca5d8a59b70da382ae1 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red)
Aug 20 17:59:19 Collective-Core podman[2025949]: 2022-08-20 17:59:19.098504204 +0100 BST m=+0.315982383 container remove 09563ca8e56baad1d877c1c9a99f88cd6f3f10705d061ca5d8a59b70da382ae1 (image=container.oh-lalabs.com/oh-lalabs/node-red:stable, name=oll-node-red, org.label-schema.url=https://nodered.org, org.label-schema.vcs-ref=, PODMAN_SYSTEMD_UNIT=podman-oll-node-red.service, org.label-schema.license=Apache-2.0, org.label-schema.vcs-url=GitHub - node-red/node-red-docker: Repository for all things Node-RED and Docker related, org.label-schema.arch=arm64v8, org.label-schema.name=Node-RED, org.label-schema.version=, org.label-schema.docker.dockerfile=.docker/Dockerfile.marjebian, org.label-schema.build-date=2022-08-15T17:21:38Z, org.label-schema.description=Low-code programming for event-driven applications., org.label-schema.vcs-type=Git)
Aug 20 17:59:19 Collective-Core systemd[1]: podman-oll-node-red.service: Main process exited, code=exited, status=1/FAILURE
Aug 20 17:59:19 Collective-Core oll-node-red[2025965]: Error: no arguments are needed with --latest or --cidfile
Aug 20 17:59:19 Collective-Core systemd[1]: podman-oll-node-red.service: Control process exited, code=exited, status=125/n/a
Aug 20 17:59:19 Collective-Core systemd[1]: podman-oll-node-red.service: Failed with result ‘exit-code’.
Aug 20 17:59:19 Collective-Core systemd[1]: podman-oll-node-red.service: Consumed 7.446s CPU time.

Alright here we go :wink:

cd /home/core-services/data/node-red
sudo npm remove node-hue-api <-node-hue-api can be replaced with any module that needs removing but may cause issues if used on a default included node. USE AT YOUR OWN RISK
sudo oll-node-red --restart

Should uninstall it for you and start node red back up

1 Like

Am I right in thinking HA would be the way to go, given they have implemented the push notification API?

1 Like

Tip: Whenever referring to a contributed node (not part of the NR application as released and almost always has “contrib” in it’s name) it is important to say which one you installed as there is usually more than one. In this case I would assume you’re talking about node-red-contrib-huemagic but there are others.

2 Likes

Phew. Well there’s a lesson learned.

“Stop playing or I will chop your fingers off” as my dear old Mum used to say.

3 Likes

Wow… You must have been a well behaved child… if you’re still able to type in Node RED plugin names… :slight_smile:

3 Likes

Not sure my Mother would agree. :slight_smile:

3 Likes