Node-red crash after mistake in modbus server

Hi, yesterday in a test with modbus server, I lost connection with node-red server.
Now I'm not able to make any change because node-red crash after a start.
How can I solve it?

See attached log:

Welcome to Node-RED

7 Oct 05:34:08 - [info] Node-RED version: v2.0.6
7 Oct 05:34:08 - [info] Node.js  version: v14.17.6
7 Oct 05:34:08 - [info] Linux 5.10.60-v7l+ arm LE
7 Oct 05:34:09 - [info] Loading palette nodes
7 Oct 05:34:12 - [info] Dashboard version 2.29.3 started at /ui
7 Oct 05:34:13 - [info] Settings file  : /home/pi/.node-red/settings.js
7 Oct 05:34:13 - [info] Context store  : 'default' [module=localfilesystem]
7 Oct 05:34:13 - [info] User directory : /home/pi/.node-red
7 Oct 05:34:13 - [warn] Projects disabled : editorTheme.projects.enabled=false
7 Oct 05:34:13 - [warn] Flows file name not set. Generating name using hostname.
7 Oct 05:34:13 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
7 Oct 05:34:13 - [info] Server now running at
7 Oct 05:34:13 - [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.

7 Oct 05:34:13 - [info] Starting flows
7 Oct 05:34:13 - [info] Started flows
7 Oct 05:34:15 - [red] Uncaught Exception:
7 Oct 05:34:15 - RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds
    at boundsError (internal/buffer.js:81:11)
    at Buffer.readUInt8 (internal/buffer.js:249:5)
    at ModbusServerResponseHandler._handleWriteSingleCoil (/home/pi/.node-red/node_modules/jsmodbus/dist/modbus-server-response-handler.js:133:45)
    at ModbusServerResponseHandler.handle (/home/pi/.node-red/node_modules/jsmodbus/dist/modbus-server-response-handler.js:40:33)
    at ModbusServerClient._onData (/home/pi/.node-red/node_modules/jsmodbus/dist/modbus-server-client.js:33:35)
    at Socket.emit (events.js:400:28)
    at addChunk (internal/streams/readable.js:290:12)
    at readableAddChunk (internal/streams/readable.js:265:9)
    at Socket.Readable.push (internal/streams/readable.js:204:10)
    at TCP.onStreamRead (internal/stream_base_commons.js:188:23)

Stop, start in safe mode (node-red --safe), fix issue, restart

1 Like

Having fixed it as suggested, which modbus node and which version are you using? node-red-contrib-something probably. The crash should be reported as an issue as no mis-configuration should cause node-red to crash.

1 Like

Hi Colin,

I'm using this version:

I'm going to update to 5.14.1


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