Node-red Error . Does not start

General
1

After installing new nodes node-red crashed and does not start. I´m running it on Raspberry.
Please any advice to fix ?

tarting as a systemd service.
Started Node-RED graphical event wiring tool.
8 Sep 11:34:01 - [info]
Welcome to Node-RED
===================
8 Sep 11:34:01 - [info] Node-RED version: v0.20.8
8 Sep 11:34:01 - [info] Node.js version: v10.15.3
8 Sep 11:34:01 - [info] Linux 4.14.98-v7+ arm LE
8 Sep 11:34:02 - [info] Loading palette nodes
8 Sep 11:34:08 - [info] Dashboard version 2.13.2 started at /ui
8 Sep 11:34:09 - [warn] ------------------------------------------------------
8 Sep 11:34:09 - [warn] [node-red-contrib-modbustcp-no-pooling/modbus tcp] Error: Cannot find module '/usr/lib/node_modules/node-red/red/red' (line:46)
8 Sep 11:34:09 - [warn] ------------------------------------------------------
8 Sep 11:34:09 - [info] Settings file : /home/pi/.node-red/settings.js
8 Sep 11:34:09 - [info] Context store : 'default' [module=memory]
8 Sep 11:34:09 - [info] User directory : /home/pi/.node-red
8 Sep 11:34:10 - [info] Server now running at http://127.0.0.1:1880/
8 Sep 11:34:10 - [info] Active project : Amorim
8 Sep 11:34:10 - [info] Flows file : /home/pi/.node-red/projects/Amorim/flows_localhost.json
8 Sep 11:34:10 - [info] Starting flows
8 Sep 11:34:10 - [info] [mosca in:2f73359.33167ca] Binding mosca mqtt server on port: 1883
2019-09-08 10:34:10: Connecting to modbustcp slave at 192.168.1.23:502 unit_id: 255
8 Sep 11:34:10 - [error] [eth-ip in:Test] Missing configuration
8 Sep 11:34:10 - [info] Started flows
8 Sep 11:34:10 - [info] [mqtt-broker:80a21c84.84208] Connection failed to broker: mqtt://127.0.0.1:1883
2019-09-08 10:34:10: [object Object]
8 Sep 11:34:10 - [error] [modbustcp-read:8e1f5b3.0a8baa8] ModbusTCPClient: {"err":"ModbusException","response":{"_id":1,"_protocol":0,"_bodyLength":3,"_unitId":255,"_body":{"_fc":2,"_code":2}}}
8 Sep 11:34:10 - [error] [modbustcp-server:Micro820] socket error: undefined: Locally emitted error
{ err: 'ModbusException',
** response:**
** ModbusTCPResponse {**
** _id: 1,**
** _protocol: 0,**
** _bodyLength: 3,**
** _unitId: 255,**
** _body: ExceptionResponseBody { _fc: 2, _code: 2 } } }**
2019-09-08 10:34:10: was disconnected or was unable to connect
8 Sep 11:34:11 - [info] [debug:f1c98384.3a809] 0
8 Sep 11:34:11 - [info] [debug:643da5ce.27149c] 0
8 Sep 11:34:11 - [red] Uncaught Exception:
8 Sep 11:34:11 - ReferenceError: outputlog is not defined
** at NodeS7.readResponse (/home/pi/.node-red/node_modules/nodes7/nodeS7.js:1427:4)**
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool.
8 Sep 11:34:13 - [info]
Welcome to Node-RED
===================
8 Sep 11:34:13 - [info] Node-RED version: v0.20.8
8 Sep 11:34:13 - [info] Node.js version: v10.15.3
8 Sep 11:34:13 - [info] Linux 4.14.98-v7+ arm LE
8 Sep 11:34:14 - [info] Loading palette nodes

2

Start it in safe mode first.

3

The following node is having issues:

node-red-contrib-modbustcp-no-pooling/modbus tcp

Which already appears to have been logged, with potential solution if you are prepared to modify the code.

Unfortunately as the author hasn't responded to include that change it doesn't look good for the long term viability of that node

4

Thank you all for the quilck answers . I will try the SAFE mode later. I´ll let you know about the result.

MD

5

After removing node-red-contrib-modbustcp-no-pooling/modbus tcp , node-red still crashes.

Any ideas to fix ? How to "reset" node-red ?

I aslo have updated the node the " node-red-contrib-s7 " this node has been updated two weeks ago. Coudl the problem come from it ? When i don´t use the mentioned nodes , node-red seems to not crash!
Would be nive to install the previous version of this node " node-red-contrib-s7 ", is this possible ?

8 Sep 17:30:17 - [error] [eth-ip in:Test] Missing configuration
8 Sep 17:30:17 - [info] Started flows
8 Sep 17:30:17 - [info] [mqtt-broker:80a21c84.84208] Connection failed to broker: mqtt://127.0.0.1:1883
8 Sep 17:30:18 - [info] [debug:f1c98384.3a809] 0
8 Sep 17:30:18 - [info] [debug:643da5ce.27149c] 0
8 Sep 17:30:18 - [red] Uncaught Exception:
8 Sep 17:30:18 - ReferenceError: outputlog is not defined
at NodeS7.readResponse (/home/pi/.node-red/node_modules/nodes7/nodeS7.js:1427:4)
at NodeS7.onResponse (/home/pi/.node-red/node_modules/nodes7/nodeS7.js:1229:9)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Unit entered failed state.
nodered.service: Failed with result 'exit-code'.
nodered.service: Service hold-off time over, scheduling restart.
Stopped Node-RED graphical event wiring tool.
Started Node-RED graphical event wiring tool

6

You can install a specific version of a node on the command line

See https://60devs.com/npm-install-specific-version.html

7

:+1:

Node-red is running again. Thank you very much for your tip.

PS: Should we make an alert to the authors about this issue ?

1 Like
8

yes please!