Error: EREMOTEIO: remote I/O error,

General
1

I am a beginner, and I need help.
Node red red won't start. It is saying this:

Starting as a systemd service.
5 Dec 10:30:34 - [info]
Welcome to Node-RED
===================
5 Dec 10:30:34 - [info] Node-RED version: v1.2.5
5 Dec 10:30:34 - [info] Node.js  version: v10.23.0
5 Dec 10:30:34 - [info] Linux 4.19.50-v7l+ arm LE
5 Dec 10:30:35 - [info] Loading palette nodes
5 Dec 10:30:38 - [info] Dashboard version 2.17.1 started at /ui
5 Dec 10:30:38 - [warn] ------------------------------------------------------
5 Dec 10:30:38 - [warn] [node-red-contrib-easybotics-air-quality/sensors] Error: libnode.so.64: cannot open shared object file: No such file or directory
5 Dec 10:30:38 - [warn] [node-red-contrib-easybotics-ina219-sensor/ina] Error: Cannot find module 'ina219' (line:1)
5 Dec 10:30:38 - [warn] [node-red-contrib-easybotics-pca9685/PCA] Error: libnode.so.64: cannot open shared object file: No such file or directory
5 Dec 10:30:38 - [warn] [node-red-contrib-easybotics-vl53l0x/hardware] Error: libnode.so.64: cannot open shared object file: No such file or directory
5 Dec 10:30:38 - [warn] ------------------------------------------------------
5 Dec 10:30:38 - [info] Settings file  : /home/pi/.node-red/settings.js
5 Dec 10:30:38 - [info] Context store  : 'default' [module=memory]
5 Dec 10:30:38 - [info] User directory : /home/pi/.node-red
5 Dec 10:30:38 - [warn] Projects disabled : editorTheme.projects.enabled=false
5 Dec 10:30:38 - [info] Flows file     : /home/pi/.node-red/flows_raspberrypi.json
5 Dec 10:30:38 - [warn]
5 Dec 10:30:38 - [info] Starting flows
5 Dec 10:30:38 - [info] Started flows
5 Dec 10:30:38 - [red] Uncaught Exception:
5 Dec 10:30:38 - Error: EREMOTEIO: remote I/O error, read
    at Object.readSync (fs.js:498:3)
    at Bus.i2cReadSync (/home/pi/.node-red/node_modules/node-red-contrib-oled/node_modules/i2c-bus/i2c-bus.js:546:15)
    at Oled._readI2C (/home/pi/.node-red/node_modules/oled-i2c-bus/oled.js:170:15)
    at tick (/home/pi/.node-red/node_modules/oled-i2c-bus/oled.js:182:10)
    at Timeout._onTimeout (/home/pi/.node-red/node_modules/oled-i2c-bus/oled.js:194:27)
    at ontimeout (timers.js:436:11)
    at tryOnTimeout (timers.js:300:5)
    at listOnTimeout (timers.js:263:5)
    at Timer.processTimers (timers.js:223:10)
nodered.service: Main process exited, code=exited, status=1/FAILURE
nodered.service: Failed with result 'exit-code'.
nodered.service: Service RestartSec=20s expired, scheduling restart.
nodered.service: Scheduled restart job, restart counter is at 24.
Stopped Node-RED graphical event wiring tool.
2

this looks the same as this reported issue Having an oled node deployed while not having an oled screen connected causes crashing of node-red

That was reported in July but Author has not responded. Perhaps the title of that issue is a clue?

If necessary, start node-red in safe mode (node-red --safe) or npm remove that oled module and try another.

1 Like
3

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