By now my node-red application is fairly complex. I have 19 tabs each with many nodes and all with some form of unique function coding, many that are extensive. While it seems to run as expected for lengthy periods (days, weeks), at some point something, somewhere, gets to a point where it drives NR…

Could a simple shell pipe solve this temporary issue? If you set console log level to trace and then start with node-red | tee /path/to/logfile.log?

If you have another always on machine - maybe send logs to it instead ? Either remote syslog to cutdown writes on the Pi or rsync on a frequent basis Or an NFS or SMB mounted drive Craig

[image] craigcurtin: Or an NFS or SMB mounted drive Why wouldn't the USB drive suffice? If it happens to be a singe part/node causing the issues that can be fixed, a temporary solution like that might be easier to setup.

It would - but what i suggested is pretty quick and easy (as long as you have other machines) and means you can watch the logs in realtime (if you wish) Craig

Agree that it has that advantage as well.

the other benefit is that you could monitor much more than just node-red traffic to see if it a Pi OS issue (for example) with Zombies, RAM, CPU etc Craig

With 19 heavily loaded tabs, there must be a fair bit going on. Are there any places where a loop could exist? E.g. do you use MQTT and subscribe to wildcards & publish to a topic upon some value change in this subscription? Or perhaps loop back to a dashboard node to update it's status & have pa…

Thanks for the feedback, each of you. I do have a Synology NAS that I could stream the file to, I might do that. I have been able to run TOP using Termius and it is absolutely node red that is unhappy. It shows memory use of over 180% with high CPU. Often the node-red-stop command will not work at …

The next time it happens use another client to subscribe to '#' on the MQTT broker and see if there is an MQTT loop. Alternatively stop the MQTT broker and see if that fixes it. However if node-red-stop has problems that sounds more like a tight loop somewhere so it is not able to respond to the c…

Colin I have the console log up in a window always. I see now the problem is the pi is running out of memory causing NR to terminate. I have no idea what is causing the RAM problems but I am slowly disabling each flow until I find the culprit. Here is the latest log capture I grabbed on the most …

Node-RED

Node-RED Forum

Node-red-log to file

General

dceejay 22 June 2020 21:50 15

as always I'm going to suspect the chart... how many data points do you have across those 300 screen pixels ?

Topic		Replies	Views
Node red stopped working General	14	2031	7 April 2024
Crashing Every Few Minutes - How Do I Debug? General	14	362	7 August 2023
Node-red-out-log (large file) General	14	1975	14 May 2020
Unplanned Restart / Reboot? General	44	3355	27 February 2020
Node Red crashes every 30 minutes General	24	708	17 January 2023

Copyright OpenJS Foundation and Node-RED contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them.

Node-red-log to file

Related topics