Crashing infinite loop [@flowfuse/nr-project-nodes/project-link] Error: Project Link nodes cannot be loaded

Support
1

Hi all, I was doing some tests on my instance, and randomly it crashed. I say randomly because that only thing that I’ve changed was add a http endpoint block. Also, I’ve restarted using safe mode and removed this block to see if it’s been the issue source. Even so it keeps restarting and crashing.

1/03/2024 11:39:27 am  [info]    Welcome to Node-RED
===================

1/03/2024 11:39:27 am  [info]    Node-RED version: v3.1.3
1/03/2024 11:39:27 am  [info]    Node.js  version: v18.19.0
1/03/2024 11:39:27 am  [info]    Linux 5.10.205-195.804.amzn2.aarch64 arm64 LE
1/03/2024 11:39:32 am  [info]    Loading palette nodes
1/03/2024 11:39:34 am  [system]  Node-RED health check failed: RequestError: connect ECONNREFUSED 127.0.0.1:1880 (http://127.0.0.1:1880/)
1/03/2024 11:39:34 am  [info]    FlowFuse HTTP Authentication Plugin loaded
1/03/2024 11:39:34 am  [info]    FlowFuse Team Library Plugin loaded
1/03/2024 11:39:34 am  [info]    FlowFuse Light Theme Plugin loaded
1/03/2024 11:39:34 am  [info]    FlowFuse Dark Theme Plugin loaded
1/03/2024 11:39:35 am  [info]    FlowFuse Metrics Plugin loaded
1/03/2024 11:39:41 am  [system]  Node-RED health check failed: RequestError: connect ECONNREFUSED 127.0.0.1:1880 (http://127.0.0.1:1880/)
1/03/2024 11:39:43 am  [warn]    ------------------------------------------------------
1/03/2024 11:39:43 am  [warn]    [@flowfuse/nr-project-nodes/project-link] Error: Project Link nodes cannot be loaded outside of an FlowFuse EE environment (line:6)
1/03/2024 11:39:43 am  [warn]    ------------------------------------------------------
1/03/2024 11:39:43 am  [info]    Settings file  : /data/settings.js
1/03/2024 11:39:43 am  [info]    Context store  : 'memory' [module=memory]
1/03/2024 11:39:43 am  [info]    Context store  : 'persistent' [module=custom]
1/03/2024 11:39:44 am  [info]    Server now running at http://127.0.0.1:1880/
1/03/2024 11:39:44 am  [info]    *****************************************************************
1/03/2024 11:39:44 am  [info]    Flows stopped in safe mode. Deploy to start.
1/03/2024 11:39:44 am  [info]    *****************************************************************
1/03/2024 11:43:34 am  [info]    Stopping flows
1/03/2024 11:43:34 am  [info]    Stopped flows
1/03/2024 11:43:34 am  [info]    Updated flows
1/03/2024 11:43:35 am  [info]    Starting flows
1/03/2024 11:43:35 am  []        SFTP - Using key file
1/03/2024 11:43:49 am  [system]  Node-RED health check failed: TimeoutError: Timeout awaiting 'request' for 6999ms (http://127.0.0.1:1880/)
1/03/2024 11:43:56 am  [system]  Node-RED health check failed: TimeoutError: Timeout awaiting 'request' for 6999ms (http://127.0.0.1:1880/)
1/03/2024 11:44:03 am  [system]  Node-RED health check failed: TimeoutError: Timeout awaiting 'request' for 6999ms (http://127.0.0.1:1880/)
1/03/2024 11:44:03 am  [system]  Node-RED hang detected.
1/03/2024 11:44:03 am  [system]  Stopping Node-RED
1/03/2024 11:44:09 am  [system]  Node-RED exited rc=null signal=SIGKILL
1/03/2024 11:44:09 am  [system]  Node-RED unexpectedly stopped after: 291s
1/03/2024 11:44:09 am  [system]  Starting Node-RED
1/03/2024 11:44:17 am  [system]  Node-RED health check failed: RequestError: connect ECONNREFUSED 127.0.0.1:1880 (http://127.0.0.1:1880/)
1/03/2024 11:44:18 am  [info]    Welcome to Node-RED
===================

1/03/2024 11:44:18 am  [info]    Node-RED version: v3.1.3
1/03/2024 11:44:18 am  [info]    Node.js  version: v18.19.0
1/03/2024 11:44:18 am  [info]    Linux 5.10.205-195.804.amzn2.aarch64 arm64 LE
1/03/2024 11:44:23 am  [info]    Loading palette nodes
1/03/2024 11:44:24 am  [system]  Node-RED health check failed: RequestError: connect ECONNREFUSED 127.0.0.1:1880 (http://127.0.0.1:1880/)
1/03/2024 11:44:25 am  [info]    FlowFuse HTTP Authentication Plugin loaded
1/03/2024 11:44:25 am  [info]    FlowFuse Team Library Plugin loaded
1/03/2024 11:44:25 am  [info]    FlowFuse Light Theme Plugin loaded
1/03/2024 11:44:25 am  [info]    FlowFuse Dark Theme Plugin loaded
1/03/2024 11:44:26 am  [info]    FlowFuse Metrics Plugin loaded
1/03/2024 11:44:32 am  [system]  Node-RED health check failed: RequestError: connect ECONNREFUSED 127.0.0.1:1880 (http://127.0.0.1:1880/)
1/03/2024 11:44:34 am  [warn]    ------------------------------------------------------
1/03/2024 11:44:34 am  [warn]    [@flowfuse/nr-project-nodes/project-link] Error: Project Link nodes cannot be loaded outside of an FlowFuse EE environment (line:6)
1/03/2024 11:44:34 am  [warn]    ------------------------------------------------------
1/03/2024 11:44:34 am  [info]    Settings file  : /data/settings.js
1/03/2024 11:44:34 am  [info]    Context store  : 'memory' [module=memory]
1/03/2024 11:44:34 am  [info]    Context store  : 'persistent' [module=custom]
1/03/2024 11:44:34 am  [info]    Server now running at http://127.0.0.1:1880/
1/03/2024 11:44:35 am  [info]    *****************************************************************
1/03/2024 11:44:35 am  [info]    Flows stopped in safe mode. Deploy to start.
1/03/2024 11:44:35 am  [info]    *****************************************************************
2

You’ll need a licensed edition of FlowFuse to use the Project Link nodes, or be on the “team” tier of FlowFuse Cloud: Pricing • FlowFuse

3

@zj What’s a Project link node ? I guess I’m not using it.

4

The message about the Project Link nodes is to be expected if you are on the starter tier as they are paid for feature. It can be ignored.

Your instance is being killed because it is not responding to http requests and we allow 3 failures of the health check http request (which are 7 seconds apart meaning it has not responded for 21 seconds) before killing and restarting the instance.

The usual reason for this is that you have a tight loop somewhere either in a node you are using or more likely in a function node that is not yielding.

There are 2 possible options

  1. Use safe mode to work out what is causing the tight loop and fix it
  2. Upgrade to a large Instance size which will get more CPU time and may be able to process the load and reply to the HTTP requests.
5

I understand @Ben. As I said, was working fine. To do a test I’ve disconnected all of the data sources to stop this probable loop. Still not working.

6

Something in your flow is still generating load.

How have you “disconnected” the datasources? just removing the wire from say a MQTT in node will not stop it receiving messages, it will just stop it being fed into the rest of the flow. A large enough back log of messages would still cause the system to stall the event loop and not respond to HTTP requests.

Without a knowledge of your flow we can only speculate

7

I understand. But my data source was providing one small json each 15 minutes. Also, I deleted the data source(node).

8

How would be the best approach, export my flow and send the Json here? or a screenshot? Also do you think that if I disable all of my flows this crashing should stop ?

9

I’d start by disabling them half at a time in a binary search approach, or you could go with all and then turn them back on one at a time I suppose.

Just dumping the flows here probably won’t help as we’d have to import them somewhere and wouldn’t have any of the credentials for any remote sources.

10

I found the problematic Flow. I was not even working on this flow, it was kind of inactivated, no data landing. Even so I’ve removed the http nodes from it. Still making my instance crash.

11

I did find the problem, there was a subflowA node inside of the subflowA. I’ve no idea how it ended up there. But it’s the problem source. Thanks @Ben and @zj for the quick reply.

12

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.