Problems with run node red start

Suddenly my node red stopped working, reinstalling does not solve the problem :
logs

i Node-RED works better with the Firefox or Chrome browser

Use node-red-stop to stop Node-RED
Use node-red-start to start Node-RED again
Use node-red-log to view the recent log output
Use sudo systemctl enable nodered.service to autostart Node-RED at every boot
Use sudo systemctl disable nodered.service to disable autostart on boot

To find more nodes and example flows - go to http://flows.nodered.org

Starting as a systemd service.
4 Nov 19:46:01 - [error] [tensorflowCoco:0e076ed9ba64afbc] Error: /home/jacol/.node-red/node_modules/@tensorflow/tfjs-node/lib/napi-v8/tfjs_binding.node: wrong ELF class: ELFCLASS64
4 Nov 19:46:01 - [info] Started flows
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] login -> ***************************wXOVV
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] SEND -> Cmd: LOGIN, Id: 1, len: 32, data: "***************************wXOVV"
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann_CH1234] login -> ***************************sdUIW
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann_CH1234] SEND -> Cmd: LOGIN, Id: 1, len: 32, data: "***************************sdUIW"
(node:8445) Warning: Setting the NODE_TLS_REJECT_UNAUTHORIZED environment variable to '0' makes TLS connections and HTTPS requests insecure by disabling certificate verification.
(Use node --trace-warnings ... to show where the warning was created)
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] RECV <- Cmd: RSP, Id: 1, responseCode: OK
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] Client logged
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] SEND -> Cmd: INTERNAL, Id: 2, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.9|build|2023-01-12"
4 Nov 19:46:02 - [info] [blynk-ws-client:40e46c9aaa2b12b0] Client logged
4 Nov 19:46:02 - [info] [blynk-ws-client:Weather] Client logged
4 Nov 19:46:02 - [info] [blynk-ws-client:Pir_status] Client logged
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann_CH1234] RECV <- Cmd: RSP, Id: 1, responseCode: OK
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann_CH1234] Client logged
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann_CH1234] SEND -> Cmd: INTERNAL, Id: 2, len: 85, data: "ver|0.6.1|h-beat|15|buff-in|32767|dev|node-red|con|Blynk-ws|fw|1.0.9|build|2023-01-12"
4 Nov 19:46:02 - [info] [blynk-ws-client:2953ef1774a8a3b1] Client logged
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] virtualWrite: -> ["vw","35","NaN"]
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] SEND -> Cmd: HW, Id: 3, len: 9, data: "vw|35|NaN"
4 Nov 19:46:02 - [info] [blynk-ws-client:Local] RECV <- Cmd: RSP, Id: 2, responseCode: OK
4 Nov 19:46:02 - [info] [blynk-ws-client:Hormann_CH1234] RECV <- Cmd: RSP, Id: 2, responseCode: OK
4 Nov 19:46:02 - [red] Uncaught Exception:
4 Nov 19:46:02 - [error] SyntaxError: Unexpected token I in JSON at position 0
at JSON.parse ()
at Request._callback (/home/jacol/.node-red/node_modules/node-red-contrib-blynk-api/blynk-api.js:448:27)
at Request.self.callback (/home/jacol/.node-red/node_modules/request/request.js:185:22)
at Request.emit (node:events:513:28)
at Request. (/home/jacol/.node-red/node_modules/request/request.js:1154:10)
at Request.emit (node:events:513:28)
at IncomingMessage. (/home/jacol/.node-red/node_modules/request/request.js:1076:12)
at Object.onceWrapper (node:events:627:28)
at IncomingMessage.emit (node:events:525:35)
at endReadableNT (node:internal/streams/readable:1358:12)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Consumed 13.185s CPU time.

You have a node causing an "Uncaught Exception"

That node is node-red-contrib-blynk-api

To get up and running, uninstall that node usingnpm remove node-red-contrib-blynk-api from /home/jacol/.node-red

Also, report the error to the author by raising an issue on the GitHub repository.

You might want to walk away from node-red-contrib-blynk-api - and try your luck with a different Node.

If you stop node-red then restart using
node-red --safe
it will start up in safe mode, with the editor enabled but no flows running. That should stop the node from crashing node-red and you can try to fix the flow that is causing the problem. When you deploy it will start the flows.

1 Like

Thank you guys, it worked. :slight_smile:

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