Can't start MM as kiosk only server

bhepler

For starters, please use the markdown features when posting code & logs.
Secondly, did you take the error message’s advice and run npm rebuild in the MMM-AssistantMk2 folder? Did it help?

Warmyster

Hi thanks.
I’ve done npm rebuild and audit fix same error come up. The application launch but only a black screen and I have to Kill the process.

lavolp3

@warmyster said in Can't start MM as kiosk only server:

App threw an error during load
Error: Failed to load gRPC binary module because it was not installed for the current system
Expected directory: electron-v2.0-linux-arm-glibc
Found: [electron-v4.0-linux-arm-glibc, node-v67-linux-arm-glibc]

It seems that some module inside MMM-AssistantMk2 is compiled against electron v2.0. If above suggestion does not work I would recommend installing the whole module again. Delete the folder, do a git clone, git pull and npm install again.

lavolp3

@warmyster Or try disabling MMM-AssistantMk2 and run MM again.

Warmyster

@lavolp3 It works when I don’t include the module. Ill try re installing it again

Warmyster

@lavolp3
I’ve done a reinstall (deleted the directory and did git clone) and this is what I got after install but still getting the same error

pi@raspi:~/MagicMirror/modules/MMM-AssistantMk2 $ npm install

grpc@1.18.0 install /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc
node-pre-gyp install --fallback-to-build --library=static_library

node-pre-gyp WARN Using request for node-pre-gyp https download
[grpc] Success: “/home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/grpc/src/node/extension_binary/node-v67-linux-arm-glibc/grpc_node.node” is installed via remote

protobufjs@6.8.8 postinstall /home/pi/MagicMirror/modules/MMM-AssistantMk2/node_modules/protobufjs
node scripts/postinstall

npm notice created a lockfile as package-lock.json. You should commit this file.
added 273 packages from 186 contributors and audited 635 packages in 64.238s
found 0 vulnerabilities

lavolp3

well… looks good doesn’t it? Should work now.

Warmyster

@lavolp3
NO its giving the same error

lavolp3

@warmyster if it is still about this module, maybe @Sean can help since it’s his module

Warmyster

@lavolp3
Thanks I got hold of @Sean and he helped me sort if out. Turns out I didnt rebuild the packages correctly :(