Node-red crash how to solve it

[chris....@gmail.com]

I am a novice on node-red. Just try to import flow chart to understand it.... then delete all.  At last, node-red crash and cannot running. @_@......

[Nick O'Leary]

Hi,

that appears to be a bug with the node-red-contrib-modbus node - it should be catching and handling this error. It would be worth raising an issue against the node and include the text of that output: https://github.com/biancode/node-red-contrib-modbus

In the meantime, as it looks like its crashing node-red on startup, the quick solution is to rename your current flow file so that node-red starts with a blank set of flows. You can see the flow file it is using in the log output you've shared. You can then import nodes from the old flow file if you need to recover anything you had in there.

Nick

On 26 September 2017 at 09:14, <chris....@gmail.com> wrote:

I am a novice on node-red. Just try to import flow chart to understand it.... then delete all.  At last, node-red crash and cannot running. @_@......

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.
To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/2782414e-a0d6-4d44-9505-e94f8cd6f899%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Waqas Aslam]

Hi Nick

I happened to get into one of these circumstances where I was unable to start node-red due to exceptions.

Don't you think there should be a better support in node-red for managing such scenarios? I mean it should still be able to load the existing flow file, but in the creator-site it should notify which nodes are causing exceptions - just like when you use a custom node but it's not included in the pallet.

regards

-Waqas

On Tuesday, September 26, 2017 at 10:41:29 AM UTC+2, Nick O'Leary wrote:

Hi,

that appears to be a bug with the node-red-contrib-modbus node - it should be catching and handling this error. It would be worth raising an issue against the node and include the text of that output: https://github.com/biancode/node-red-contrib-modbus

In the meantime, as it looks like its crashing node-red on startup, the quick solution is to rename your current flow file so that node-red starts with a blank set of flows. You can see the flow file it is using in the log output you've shared. You can then import nodes from the old flow file if you need to recover anything you had in there.

Nick

On 26 September 2017 at 09:14, <chris....@gmail.com> wrote:

I am a novice on node-red. Just try to import flow chart to understand it.... then delete all.  At last, node-red crash and cannot running. @_@......

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Nick O'Leary]

The problem is an uncaught exception could be absolutely anything. They happen asynchronously to us starting node-red and the fact they are uncaught means we don't know where they have come from and we don't know if we can safely continue in any capacity at all.

It is possible to do some detective work based on the stack trace to make a guess as to where it has come from; and it occurred to me earlier we should do some of that and print out an additional message pointing at the likely culprit.

Nick

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.

To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/6772cfb7-d977-4d48-b610-8a3b1c8dccc2%40googlegroups.com.

[chris....@gmail.com]

Thanks Nick. The problem is solved.

Chris

在 2017年9月26日星期二 UTC+8下午4:41:29，Nick O'Leary写道：

Hi,

that appears to be a bug with the node-red-contrib-modbus node - it should be catching and handling this error. It would be worth raising an issue against the node and include the text of that output: https://github.com/biancode/node-red-contrib-modbus

In the meantime, as it looks like its crashing node-red on startup, the quick solution is to rename your current flow file so that node-red starts with a blank set of flows. You can see the flow file it is using in the log output you've shared. You can then import nodes from the old flow file if you need to recover anything you had in there.

Nick

On 26 September 2017 at 09:14, <chris....@gmail.com> wrote:

I am a novice on node-red. Just try to import flow chart to understand it.... then delete all.  At last, node-red crash and cannot running. @_@......

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.

To unsubscribe from this group and stop receiving emails from it, send an email to node-red+u...@googlegroups.com.

[Julian Knight]

Wouldn't that mean that you would have to "catch" the "uncaught" exception!?

Not sure if that is a good or not so good thing.

[Nick O'Leary]

We do catch uncaught exceptions. They trigger a shutdown hook and lets us log the error before node.js exits. My comment is we may be able to log additional information about the error beyond what we currently do.

https://github.com/node-red/node-red/blob/master/red.js#L310

Nick

--
http://nodered.org
 
Join us on Slack to continue the conversation: http://nodered.org/slack
---
You received this message because you are subscribed to the Google Groups "Node-RED" group.
To unsubscribe from this group and stop receiving emails from it, send an email to node-red+unsubscribe@googlegroups.com.
To post to this group, send email to node...@googlegroups.com.
Visit this group at https://groups.google.com/group/node-red.

To view this discussion on the web, visit https://groups.google.com/d/msgid/node-red/78cbe58c-59a5-4abb-99e0-37e18e62166d%40googlegroups.com.