Read the statement by Michael Teeuw here.
After 2.8 I'm having tons of issues. What are the steps from square 1 to get this working?
-
@Gomalley there was a dot at the end, it was important
-
Sorry, I missed that.
This is what happenedpi@raspberrypi:~ $ cd ~ pi@raspberrypi:~ $ sudo chown -R pi . pi@raspberrypi:~ $
It just went to the next line. Not sure why
-
@Gomalley it doesn’t say anything, it just changes ownership of everything in the home folder and down to the user pi.
Now, back to what u were doing before
-
@sdetweil
I tried to excute some of the commands you gave mepi@raspberrypi:~ $ pm2 logs [PM2] Spawning PM2 daemon with pm2_home=/home/pi/.pm2 internal/modules/cjs/loader.js:583 throw err; ^ Error: Cannot find module 'shelljs' at Function.Module._resolveFilename (internal/modules/cjs/loader.js:581:15) at Function.Module._load (internal/modules/cjs/loader.js:507:25) at Module.require (internal/modules/cjs/loader.js:637:17) at require (/usr/local/lib/node_modules/pm2/node_modules/v8-compile-cache/v8-compile-cache.js:161:20) at module.exports.Client.launchDaemon (/usr/local/lib/node_modules/pm2/lib/Client.js:244:7) at /usr/local/lib/node_modules/pm2/lib/Client.js:103:10 at /usr/local/lib/node_modules/pm2/lib/Client.js:311:14 at process._tickCallback (internal/process/next_tick.js:61:11) pi@raspberrypi:~ $ npm i -g npm npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules/npm npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules/npm/node_modules npm WARN checkPermissions Missing write access to /usr/local/lib/node_modules npm ERR! path /usr/local/lib/node_modules/npm npm ERR! code EACCES npm ERR! errno -13 npm ERR! syscall access npm ERR! Error: EACCES: permission denied, access '/usr/local/lib/node_modules/npm' npm ERR! { [Error: EACCES: permission denied, access '/usr/local/lib/node_modules/npm'] npm ERR! stack: npm ERR! 'Error: EACCES: permission denied, access \'/usr/local/lib/node_modules/npm\'', npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access', npm ERR! path: '/usr/local/lib/node_modules/npm' } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator (though this is not recommended). npm ERR! A complete log of this run can be found in: npm ERR! /home/pi/.npm/_logs/2019-08-06T18_59_40_902Z-debug.log pi@raspberrypi:~ $
I ran “pm2 logs” and “npm i -g npm”
Looks like I got similar results. Should I donpm install
In the MagicMirror folder now?
-
-
@sdetweil Sweet I think that worked
pi@raspberrypi:~ $ sudo npm i -g npm /usr/local/bin/npm -> /usr/local/lib/node_modules/npm/bin/npm-cli.js /usr/local/bin/npx -> /usr/local/lib/node_modules/npm/bin/npx-cli.js + npm@6.10.3 updated 3 packages in 128.39s pi@raspberrypi:~ $
Now that I have done that, Should I run
npm install
and then:
cd ~/MagicMirror npm install
-
@Gomalley only
cd ~/MagicMirror npm install
-
pi@raspberrypi:~/MagicMirror $ npm install > magicmirror@2.8.0 install /home/pi/MagicMirror > cd vendor && npm install npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@1.2.4 (node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@1.2.4: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) audited 220 packages in 21.352s found 5 vulnerabilities (4 low, 1 high) run `npm audit fix` to fix them, or `npm audit` for details > magicmirror@2.8.0 postinstall /home/pi/MagicMirror > sh installers/postinstall/postinstall.sh && npm run install-fonts MagicMirror installation successful! > magicmirror@2.8.0 install-fonts /home/pi/MagicMirror > cd fonts && npm install audited 1 package in 1.151s found 0 vulnerabilities audited 3592 packages in 97.711s found 0 vulnerabilities pi@raspberrypi:~/MagicMirror $
Looks good. What should I do next?, Try to start the mirror?
-
@Gomalley yes, start it up
-
@sdetweil I was able to start up he mirror by doing
cd ~ /MagicMirror npm start
The mirror started up like usual but it didn’t restart after I exited out of it.