Status node produces infinite messages out

Hi, I don't know what is wrong, I've just connected to debug a status node catching all flow's nodes status, and as I deploy I see an infinite messages. Nothing is going on the flow, most of these messages coming from delay nodes. Is it normal? Thank you

Set the catch to only show one of the problem nodes. Add debug nodes showing all inputs and output of the node and check there are no messages. If none then show us the catch output and how you have configured the delay node.

Hi, thanks for reply )
For privacy reasons I would like to not post all flow, I've created a small one and I see it appear, just after deploying, I've this message

msg : Object

object

status: object

source: object

id: "61092148.cfe5d8"

type: "delay"

name: ""

Here is the flow:

[{"id":"bc3e2afd.55df","type":"tab","label":"Flow 2","disabled":false,"info":""},{"id":"9d2a21a6.3ba","type":"inject","z":"bc3e2afd.55df","name":"","props":[{"p":"delay","v":"10","vt":"num"},{"p":"topic","vt":"str"}],"repeat":"","crontab":"","once":false,"onceDelay":0.1,"topic":"ss","x":290,"y":200,"wires":[["91a1e53e.d322c8"]]},{"id":"61092148.cfe5d8","type":"delay","z":"bc3e2afd.55df","name":"","pauseType":"delay","timeout":"5","timeoutUnits":"seconds","rate":"1","nbRateUnits":"1","rateUnits":"second","randomFirst":"1","randomLast":"5","randomUnits":"seconds","drop":false,"x":590,"y":200,"wires":[[]]},{"id":"af1e4664.1031d8","type":"status","z":"bc3e2afd.55df","name":"","scope":null,"x":630,"y":320,"wires":[["ed7382d3.15c4e8"]]},{"id":"ed7382d3.15c4e8","type":"debug","z":"bc3e2afd.55df","name":"","active":true,"tosidebar":true,"console":false,"tostatus":false,"complete":"true","targetType":"full","statusVal":"","statusType":"auto","x":860,"y":320,"wires":[]},{"id":"91a1e53e.d322c8","type":"function","z":"bc3e2afd.55df","name":"","func":"msg=null;\nreturn msg;","outputs":1,"noerr":0,"initialize":"","finalize":"","libs":[],"x":440,"y":200,"wires":[["61092148.cfe5d8"]]}]

I created it to be sure that a null message really makes the output of the function node silent, it is.
On the big flow I've an amazing amount of this delay empty messages, comoing from all delays in the flow and persisting in the time (the debug is filling up really fast) and they come also from nodes which are absolutely isolated from inputs, I mean, they are connected to functions (that anyway are set to null if a wrong message is coming) but this functions are not sollecitated by any event. Why?
Fortunately the cpu is very low so I don't knw if it's a normal behaviour, but I guess not

I am not seeing any debug output from your flow when I deploy or when I hit the Inject.

What are you running node-red on?

Stop node red and then start it in a terminal and post the full startup log here please (including some of the unexpected messages). When posting the log use the </> button above the forum entry window and paste it in. For the future please use that method for posting flows too.

Hi! I?m always use </> button.. exactly I paste the code, then select it and press </>, I don't know what is wrong on my message..
EDIT: probably I used only one apostrof then 3 for multiple lines?


pi@RaspbFranco:~ $ node-red-start

Start Node-RED

Once Node-RED has started, point a browser at http://192.168.1.251:1880
On Pi Node-RED works better with the Firefox or Chrome browser

Use   node-red-stop                          to stop Node-RED
Use   node-red-start                         to start Node-RED again
Use   node-red-log                           to view the recent log output
Use   sudo systemctl enable nodered.service  to autostart Node-RED at every boot
Use   sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.
30 Aug 19:32:35 - [info]
Welcome to Node-RED
===================
30 Aug 19:32:35 - [info] Node-RED version: v1.3.5
30 Aug 19:32:35 - [info] Node.js  version: v14.17.2
30 Aug 19:32:35 - [info] Linux 5.10.48-v7+ arm LE
30 Aug 19:32:37 - [info] Loading palette nodes
Initializing HAP-NodeJS v0.9.4...
30 Aug 19:32:46 - [info] Dashboard version 2.30.0 started at /ui
30 Aug 19:32:47 - [info] Settings file  : /home/pi/.node-red/settings.js
30 Aug 19:32:47 - [info] Context store  : 'default' [module=memory]
30 Aug 19:32:48 - [info] User directory : /home/pi/.node-red
30 Aug 19:32:48 - [warn] Projects disabled : editorTheme.projects.enabled=false
30 Aug 19:32:48 - [info] Flows file     : /home/pi/.node-red/flows_RaspbFranco.json
30 Aug 19:32:48 - [info] Server now running at http://127.0.0.1:1880/
30 Aug 19:32:49 - [warn]
---------------------------------------------------------------------
Your flow credentials file is encrypted using a system-generated key.
If the system-generated key is lost for any reason, your credentials
file will not be recoverable, you will have to delete it and re-enter
your credentials.
You should set your own key using the 'credentialSecret' option in
your settings file. Node-RED will then re-encrypt your credentials
file using your chosen key the next time you deploy a change.
---------------------------------------------------------------------
30 Aug 19:32:49 - [info] Starting flows
      pi : TTY=unknown ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/python -u /home/pi/.node-red/node_modules/node-red-contrib-lcd20x4-i2c/LCD20x4-I2C/lcd20x4_i2c.py writelcd 20x4 2 0x27
pam_unix(sudo:session): session opened for user root by (uid=0)
30 Aug 19:32:49 - [info] [tcp out:Dimmer WiFi Bridge] connecting to 192.168.1.254:8899
30 Aug 19:32:50 - [error] [function:Logica pulsanti Tapparelle] SyntaxError: Unexpected token 'if' (body:line 36)
30 Aug 19:32:50 - [error] [function:Logica Tapparelle Bagno] SyntaxError: Unexpected token 'return' (body:line 32)
30 Aug 19:32:50 - [info] [tcp out:Denon Amplificatore] connecting to 192.168.1.252:23
30 Aug 19:32:50 - [info] Started flows
30 Aug 19:32:50 - [info] [tcp out:Dimmer WiFi Bridge] connected to 192.168.1.254:8899
30 Aug 19:32:50 - [info] [tcp out:Denon Amplificatore] connected to 192.168.1.252:23
30 Aug 19:32:51 - [info] [alexa-remote-account:Alexa-Remote-v2] intialising "Alexa-Remote-v2" with the PROXY method and saved data...
30 Aug 19:32:51 - [info] nora: authenticated, uid: tqYrWJJKUtZRYVdVKDAcVq4GwPf2
30 Aug 19:32:51 - [info] nora: <default> - disconnected
30 Aug 19:32:52 - [info] nora: <default> - connected
30 Aug 19:32:52 - [warn] [alexa-remote-account:Alexa-Remote-v2] failed to load routines: "routines.map is not a function"
Preparing Advertiser for 'Homekit-Franco 28C6' using bonjour-hap backend!
Starting to advertise 'Homekit-Franco 28C6' using bonjour-hap backend!
30 Aug 19:33:00 - [info] nora: <default> - synced 32 device(s)

I have corrected the backticks on your previous post, as you said, you only had single ticks.

I cannot see any of the status node messages in the log you posted, but I do see a number of errors flagged there. I would start by fixing those.

Ok, I will, but it doesn't solve the problem. I don't know why, you need to give me more instruments to debug what is going on.

The usual reason is when people set the debug node connected to the status node to report to its status - so the status node then sees that and reports it again and so creates an infinite loop. Apart from that I would suggest trying to set the status to only report from nodes you know you want to report from to try to narrow down where he messages are coming from.

As I said, the test flow you posted does not output any debug on my system. You could start by updating to the latest node red, though I will be surprised if that shows the problem.

Also, in your test flow set the status node to only show output from the node in the flow as suggested by Nick.