Error: bind EADDRNOTAVAIL 192.168.48.99:50086

#1

Very odd, I just noticed that my Node-RED crashed after running since the 22nd (see attached log) I wasn't even using NR at the time. The last time I did a deploy was about 27 hours before this happened.

192.168.48.99 is the address of my Mac where NR was running. I do a lot of experimenting (and adding in other's flows to see if I can help them) on the Mac.

Any idea's?

===============
Log (shortened)

Welcome to Node-RED
===================

22 Dec 23:50:23 - [info] Node-RED version: v0.19.5
22 Dec 23:50:23 - [info] Node.js  version: v8.9.4
22 Dec 23:50:23 - [info] Darwin 17.7.0 x64 LE
22 Dec 23:50:23 - [info] Loading palette nodes
22 Dec 23:50:24 - [warn] rpi-gpio : Raspberry Pi specific node set inactive
22 Dec 23:50:25 - [warn] [chart request] Deprecated call to RED.runtime.nodes.registerType - node-set name must be provided as first argument
22 Dec 23:50:25 - [warn] [chart response] Deprecated call to RED.runtime.nodes.registerType - node-set name must be provided as first argument
22 Dec 23:50:26 - [info] Dashboard version 2.10.1 started at /ui
22 Dec 23:50:26 - [info] Settings file  : /Users/Paul/.node-red/settings.js
22 Dec 23:50:26 - [info] Context store  : 'default' [module=localfilesystem]
22 Dec 23:50:26 - [info] Context store  : 'memoryOnly' [module=memory]
22 Dec 23:50:26 - [info] User directory : /Users/Paul/.node-red
22 Dec 23:50:26 - [warn] Projects disabled : editorTheme.projects.enabled=false
22 Dec 23:50:26 - [info] Flows file     : /Users/Paul/.node-red/david2.json
22 Dec 23:50:26 - [info] Server now running at http://127.0.0.1:1880/
22 Dec 23:50:26 - [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.
---------------------------------------------------------------------

22 Dec 23:50:26 - [info] Starting flows
22 Dec 23:50:27 - [info] Started flows
22 Dec 23:50:27 - [info] [sqlitedb:c5303ee9.6aadf8] opened /Users/Paul/sqlite_dbs/pmwsqlitedb ok

<...snip...>

26 Dec 05:25:24 - [info] [mqtt-broker:86799c21.0a2a18] Connected to broker: mqtt://192.168.48.100:1883
26 Dec 05:27:37 - [info] [mqtt-broker:a50210ee.e688e8] Disconnected from broker: mqtt://192.168.48.100:1883
26 Dec 05:27:37 - [info] [mqtt-broker:e4b6ece0.98a758] Disconnected from broker: mqtt://plantpi.local:1883
26 Dec 05:27:52 - [info] [mqtt-broker:a50210ee.e688e8] Connected to broker: mqtt://192.168.48.100:1883
26 Dec 05:27:52 - [info] [mqtt-broker:e4b6ece0.98a758] Connected to broker: mqtt://plantpi.local:1883
26 Dec 06:04:00 - [red] Uncaught Exception:
26 Dec 06:04:00 - Error: bind EADDRNOTAVAIL 192.168.48.99:50086
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at _handle.lookup (dgram.js:266:18)
    at _combinedTickCallback (internal/process/next_tick.js:141:11)
    at process._tickCallback (internal/process/next_tick.js:180:9)
Pauls-mini:~ Paul$ 

0 Likes

#2

It could be a temporary port assignment conflict. Has the problem repeated at all?
This link may help.
https://www.toptip.ca/2010/02/linux-eaddrnotavail-address-not.html

0 Likes

#3

Well it has repeated after anotehr two days running and the address is different. It must have something to do with one of the nodes I have running. I'm going to have to disable some flows and let it run and see if it goes away. Boy this is going to take at least untill next year!!! :partying_face:

0 Likes