Code=killed, Status=4/ILL

#1

Hi everyone,
just joined de forum and a newbie to node-red and raspbian...

need your help if possible!

I was working on my flow when node-red stopped working (not sure what I did wrong)!
but when I try to start it again I'm getting this (see below) in a infinite loop:

Starting as a systemd service.
Started Node-RED graphical event wiring tool.
31 Mar 09:55:00 - [info]
Welcome to Node-RED

31 Mar 09:55:00 - [info] Node-RED version: v0.20.3
31 Mar 09:55:00 - [info] Node.js version: v10.15.3
31 Mar 09:55:00 - [info] Linux 4.14.98+ arm LE
31 Mar 09:55:04 - [info] Loading palette nodes
nodered.service: Main process exited, code=killed, status=4/ILL
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'signal'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
31 Mar 09:55:32 - [info]
Welcome to Node-RED

31 Mar 09:55:32 - [info] Node-RED version: v0.20.3
31 Mar 09:55:32 - [info] Node.js version: v10.15.3
31 Mar 09:55:32 - [info] Linux 4.14.98+ arm LE
31 Mar 09:55:37 - [info] Loading palette nodes
nodered.service: Main process exited, code=killed, status=4/ILL
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'signal'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
31 Mar 09:56:04 - [info]
Welcome to Node-RED

31 Mar 09:56:04 - [info] Node-RED version: v0.20.3
31 Mar 09:56:04 - [info] Node.js version: v10.15.3
31 Mar 09:56:04 - [info] Linux 4.14.98+ arm LE
31 Mar 09:56:09 - [info] Loading palette nodes

i'm guessing that as to do with palette nodes!!!!
what should I do? any idea?

thanks so much,

Rui Silva

0 Likes

#2

How did you install node-red and what command are you running to get that log?

0 Likes

#3

thanks for the replay.
node-red come by default with raspbian instalation, and then I updated. since then I have installed some nodes but by using node-red UI.
I used the command: node-red-start

0 Likes

#4

You should upgrade using the pi install/upgrade script from the link below. That will ensure you have a consistent set of tools. Also read the rest of that page as other aspects may be of use to you.
https://nodered.org/docs/hardware/raspberrypi

0 Likes

#5

You can stop the auto start using the stop command listed in the page colin linked to.

Then you can start on the command line but Add --safe mode flag to allow starting without flows running. This can be used if a flow is causing Node-RED to crash - starting in safe mode will allow the editor to be used to modify the flow and then deploy the change to take it out of safe mode.

0 Likes

#6

thanks for the quick replay, will have a good reading on the link segested by Colin... and follow your sugestion... will come back to your asap

0 Likes

#7

apologies for taking so much time to replay back with the outcome.

after many tries without any success I have done a fresh new installed os the OS (Raspbian Stretch)
and replicated step by step the instalations of node-red and all the nodes (testing it one by one) and I found the issue:

the node-red-contrib-ttn was casuing this (I don't know why!) but after installing it the same thing happen! I guess it as to do with it somehow.

thanks ,

Rui Silva

0 Likes

#8

Good work tracking it down!
You should open an issue on the nodes github page ( follow a link from the nodes page on flows.nodered.org) in order to notify the nodes author about the problem.

0 Likes