2017-01-22, 06:24 PM
I too had Node-Red crash and not respond. Reboot the Pi, stop and stop Node-Red did not fix. CPU load was around 28%. I did find that I could re-load my Node-Red flow and get it back working for a few hours, then crash with the same symptoms.
I reloaded 0.9.0 on a fresh SD card, rebuilt the Node-Red Flow, still crash.
Tried only building one node in a fresh flow, then seeing if Node-Red crashed in a few hours, kept adding nodes, wait a few hours, adding more nodes. It would crash after I added the 3rd or forth node.
In Node-Red I am reading InsideTemp, OutsideTemp, Lat/Long, Humidity, Pressure, several 1W temperature probes, Switch closures, controlling relays with closures, Magnetic Heading, GPS data...etc.
I tried the above in different combinations to see what and where Node-Red would fail.
I wanted to see if the mixture of OpenPlotter and Node-Red on the same Pi may be the problem.
I loaded up a non OpenPlotter Pi2 running Raspian and rebuilt Node-Red on that Pi and networked to a Pi2 running OpenPlotter 0.9.0 and read the SignalK on port 3000.
Node-Red seam stable on the Node-Red only Pi2. I then built a flow using everything the SignalK server was outputting on the OpenPlotter Pi. Trying to really load down the Node-Red server.
It has been stable for 24 Hours without a crash.
I reloaded 0.9.0 on a fresh SD card, rebuilt the Node-Red Flow, still crash.
Tried only building one node in a fresh flow, then seeing if Node-Red crashed in a few hours, kept adding nodes, wait a few hours, adding more nodes. It would crash after I added the 3rd or forth node.
In Node-Red I am reading InsideTemp, OutsideTemp, Lat/Long, Humidity, Pressure, several 1W temperature probes, Switch closures, controlling relays with closures, Magnetic Heading, GPS data...etc.
I tried the above in different combinations to see what and where Node-Red would fail.
I wanted to see if the mixture of OpenPlotter and Node-Red on the same Pi may be the problem.
I loaded up a non OpenPlotter Pi2 running Raspian and rebuilt Node-Red on that Pi and networked to a Pi2 running OpenPlotter 0.9.0 and read the SignalK on port 3000.
Node-Red seam stable on the Node-Red only Pi2. I then built a flow using everything the SignalK server was outputting on the OpenPlotter Pi. Trying to really load down the Node-Red server.
It has been stable for 24 Hours without a crash.