Hello everybody.
Now, I am running node-red on my Raspberry Pi3 to visualize temperature sensors of my solar boilers. There are 4 temperatur sensors (ds18b20) for each boiler (2 boilers). Furthermore I wanted to display date and time. I created all flows and deployed but as I wanted to display on my dashboard nothing happened. My Raspberry PI was dead no reaction on any mouse click what so ever. CPU on my Raspberry was about 30% but I think that should at least permit to start my console.
Node-red version V8.11.3
Since I am a new user I am not allowed to upload my flows. That would make it easier to explain. I am still convinced that Node-red is a super tool but at the moment I have no idea what to do.
All help is much appreciated.
leafboy
If you go to the raspberry pi page in the documents on the node-red website there’s a script you can run to get you onto a standard platform
On the same page there’s details of how to access the log files, if it stops again then look at the logs
Colin
22 June 2018 20:53
3
How do you know what the CPU was if it was not responding?
Dear all.
Thanks a lot for your replay.@colin : Last time before it freezes I checked but this might be due to other processes. I can’t relate this to node-red.
@ukmoose : I run this script serveral times before. There are a few warnings and this error:
node-pre-gyp ERR! Tried to download(404): https://github.com/kelektiv/node.bcrypt.js/releases/download/v1.0.3/bcrypt_lib-v1.0.3-node-v57-linux-arm.tar.gz
I am not sure if this is what the problem causes.
Many thanks in advance for your assistance.
leafboy
Colin
24 June 2018 13:04
5
Those messages are just for information, they do not indicate a problem.
Is the pi completely unresponsive? Any mouse movement? If you have a keyboard plugged in does the caps lock switch the caps lock led on/off?
When it hangs how do you get the pi going again? Do you have to power cycle? If so then note the time, then wait about a minute and then power cycle. Then have a look in the system log file (/var/log/syslog). Paste the last 20 or 30 lines here from before the reboot log. Looking at the time in the log is the end of the log when it hung or when you power cycled (in other words is there anything written to the log after it hung?
Actually I connect remote to my Pi via my linux laptop. The connection gets lost and I have to restart all over again. I noticed as soon I start Node-red a lot of messages appear in the console. I created a date and time flow which updates every second. Maybe this causes the crash. But how can I delete or alter it without starting Node-red?
thanks
I renamed the start file in directory .node-red to startold and ran Node-red again it worked. No crash. It seems as soon as a lot of payloads are created my Pi crashes. Could this be the case and how can I solve that problem?
Thank you very much.
leafboy
read the thread above and paste the logs after nodered has crashed here
sorry - but where can I find the thread?
This thread
post 2 asks for you to look at the logs
post 5 asks you to paste from the logs
Colin
24 June 2018 14:24
11
Paste those messages here.
Sorry - I got it.
Thanks for your patience
the logs should be there after you have restarted your pi- have you checked?
Looking into the log files showed there has been no chance since updating:
make: Verzeichnis »/home/pi/.node-red/node_modules/serialport/build« wird verlassensocket.io @1.7.4 /home/pi/.node-red/node_modules/socket.ioengine.io @1.8.5 /home/pi/.node-red/node_modules/engine.io
Due to restrictions I had to delete the first lines (only 32000 char. are allowed). This is the last line since I update as shown on the raspberry I docs
I managed to create a screen shot of the messages shown in the console. Would this be helpful?
Thanks
Colin
24 June 2018 15:25
16
I thought you were connected via ssh, so the terminal is running on the PC not the pi. Are the messages flashing past very quickly continuously? If so then node red has not crashed it is just that for some reason you are asking it to run something extremely fast. You should be able to see from the messages what it is that is happening so fast.
Yes - I connect to my Pi via SSH and finally I managed to add a screen shot to my posts. These messages seem quite normal but how can I stop it to maintain other settings. As soon as I start node-red I freezes I no access to node-red is possible. Is it not due to lack of memory that it feezes?
tx
Colin
24 June 2018 16:40
18
No, it is most unlikely to be lack of memory.
Sorry for my late and not sufficient answer. I deleted my old flows in the .node-red folder and started all over again. Then I created 10 temp-sensors DS18B20 and injected at every 10s a time stamp. So far it works all fine and the debug messages appear correctly. After adding some nodes to display time and date. Still working fine. But after adding a DHT22 sensor my PI crashed again. No debug messages were given and the connection to my Tablet got lost (connection lost). This is when I have to restart my PI because no further actions were possible after that.
The browser is running on my PI.
The added screenshot above is from my PI before it freezes.
I tried to copy the debug messages but my PI already stopped working only a screenshot of the debug messages was possible. See below.
That does not look as error messages to me. Later on I will try running my browser on the PC.
Hopefully I did answer all your questions. Many thanks for your support it is much appreciated.
tx
What node are you using for the dht22? If it is the node-red-contrib-dht-sensor, did you install the BCM2835 library and node-dht-sensor as it tells you to?
Can you paste in your flow now?
sorry, as I wrote at the beginning I am a total newbee and some kind of lost.
