Node-red crashes after "Started flows". Uncaught Exception : EADDRNOTAVAIL port 502

General
1

I am unable to run node-red on my computer. This throws an error while starting NR. I uninstalled node.js and npm both and reinstalled again but the problem persists. Please tell me how to overcome this so that my node-red can run smoothly. Thanks in advance.
11 May 17:35:12 - [info] Node-RED version: v1.0.6
11 May 17:35:12 - [info] Node.js version: v12.16.3
11 May 17:35:12 - [info] Windows_NT 10.0.18362 ia32 LE
11 May 17:35:13 - [info] Loading palette nodes
11 May 17:35:14 - [info] Settings file : \Users\Win10.node-red\settings.js
11 May 17:35:14 - [info] Context store : 'default' [module=memory]
11 May 17:35:14 - [info] User directory : \Users\Win10.node-red
11 May 17:35:14 - [warn] Projects disabled : editorTheme.projects.enabled=false
11 May 17:35:14 - [info] Flows file : \Users\Win10.node-red\flows_Win10-PC.json
11 May 17:35:14 - [info] Server now running at http://127.0.0.1:1880/
11 May 17:35:14 - [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.

11 May 17:35:14 - [info] Starting flows
11 May 17:35:14 - [info] Started flows
11 May 17:35:14 - [red] Uncaught Exception:
11 May 17:35:14 - Error: listen EADDRNOTAVAIL: address not available 10.8.0.10:502
at Server.setupListenHandle [as _listen2] (net.js:1296:21)
at listenInCluster (net.js:1361:12)
at doListen (net.js:1500:7)
at processTicksAndRejections (internal/process/task_queues.js:85:21)

2

You have a node in your flow that is trying to access 10.8.0.10, port 502. But it isn't accessible for some reason. It could be a permissions issue, or it could just be wrong.

Whatever the node is, it should be handling this error and not letting go uncaught.

What nodes have you got in your flow?

As an aside, please make sure you give your posts a title that reflects the issue. Every post to the forum is someone asking for help, so a title of 'please suggest how to solve this problem' doesn't give any information.

3

My guess is you have modbus TCP node installed? (port 502 is notmally modbus TCP)

You could start in safe mode and edit it or remove it.

If I am correct, can you tell us which one it is from this list?

4

"Address not available" suggests you try to bind to an interface with IP "10.8.0.10", but none has been found for that address on your system. This is a standard socket error.

Could you check your available network interfaces and assigned IP addresses?

5

I agree with what you say but NO contrib node should crash node-red.

It seems "a node" is NOT handling (Uncaught Exception)

So I'd like the OP to identify the node so he / I can check its raised as an issue on the repo (for the good of the community)

PS, @kumarsemal I'm going to update that title - its not descriptive enough and is not going to attract the right attention.

6

No, of course they shouldn't crash the runtime. :sweat_smile:

Is the OP by any chance using the node-red-contrib-modbus nodes?
We tried them a while back at work in an R&D project and had similar troubles (mainly crashing, blocked ports, ...). The error handling and resource management was a bit erratic, at least back then. :thinking:
Unfortunately, we didn't have the resources to improve them (our team is rather small, now even more so).

7

I'm sure when I played with modbus some time back it was the same thing as you describe.

There are a number of closed issues very similar.

Hopefully the op will respond.