Version 2.33.0/node v22.21.0 - Error: write EFAULT

Mr.Sponti

Here my System Information (started with: node --run start:wayland):

[2025-11-22 10:47:48.003] [LOG]   Sockets connected & modules started ...
[2025-11-22 10:47:49.223] [ERROR] Error: write EFAULT
    at afterWriteDispatched (node:internal/stream_base_commons:159:15)
    at writeGeneric (node:internal/stream_base_commons:150:3)
    at Socket._writeGeneric (node:net:966:11)
    at Socket._write (node:net:978:8)
    at writeOrBuffer (node:internal/streams/writable:572:12)
    at _write (node:internal/streams/writable:501:10)
    at Writable.write (node:internal/streams/writable:510:10)
    at execSync (node:child_process:999:20)
    at node:electron/js2c/node_init:2:17346
    at /home/pi/MagicMirror/node_modules/systeminformation/lib/system.js:175:28
    at ChildProcess.exithandler (node:child_process:410:7)
    at ChildProcess.emit (node:events:519:28)
    at maybeClose (node:internal/child_process:1101:16)
    at Socket.<anonymous> (node:internal/child_process:456:11)
    at Socket.emit (node:events:519:28)
    at Pipe.<anonymous> (node:net:346:12)
[2025-11-22 10:47:49.224] [LOG]   Node NOT Exiting...
[2025-11-22 10:47:49.395] [LOG]   Launching application.
[2025-11-22 10:47:56.485] [INFO]
####  System Information  ####
- SYSTEM:   manufacturer: Raspberry Pi Foundation; model: Raspberry Pi 4 Model B Rev 1.1; virtual: false; MM: 2.33.0
- OS:       platform: linux; distro: Debian GNU/Linux; release: 13; arch: arm64; kernel: 6.12.47+rpt-rpi-v8
- VERSIONS: electron: 38.1.2; used node: 22.19.0; installed node: 22.21.0; npm: 10.9.4; pm2: 6.0.13
- ENV:      XDG_SESSION_TYPE: tty; MM_CONFIG_FILE: undefined
            WAYLAND_DISPLAY:  wayland-0; DISPLAY: :0; ELECTRON_ENABLE_GPU: undefined
- RAM:      total: 906.64 MB; free: 449.86 MB; used: 456.78 MB
- OTHERS:   uptime: 21 minutes; timeZone: Europe/Berlin

Mr.Sponti

So, after further investigations I found the issue in the module: ./MagicMirror/node_modules/systeminformation/lib/system.js:175:28

I’m not a nodejs expert, but it seems that execSync returns a invalid or corrupted raw buffer. The encoding option solved the issue, as in my case execSync returns now an empty string.

const stdout = execSync('dmesg 2>/dev/null | grep -iE "virtual|hypervisor" | grep -iE "vmware|qemu|kvm|xen" | grep -viE "Nested Virtualization|/virtual/"', {encoding: 'utf-8'});

sdetweil

@Mr.Sponti if you take the contents of the execSync() and run it at the command line does it work?

Mr.Sponti

Yes, without any error, but also without any output!

sdetweil

@Mr.Sponti how about the 1st command

dmesg

In the line in the execSync it throws away any errors