Installing MM2

[Bangee]

ok, and whats inside of this file: /home/pi/MagicMirror/npm-debug.log
Can you share this with us?

[berry]

@Bangee said in Installing MM2:

as I c, you’ve installed your MagicMirror in the /root directory.
I’m not sure if this is working so far.

Try to install everything as pi and not as root in the /home/pi directory and let us know what happend.

try whoami -> pi

update your distribution with sudo apt-get update && sudo apt-get upgrade

then cd /home/pi or only cd

and install again: curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh | bash

worked for me !! thanks

at least i shouldnt tried to install MM2 as root

[Neokamikaze]

Hi Bangee,

Sorry for this late. Find this my npm file.

Thanks

0_1467112984554_npm-debug.log

[Neokamikaze]

Hi,

I restart all installation and now my depencies is OK. But when i start “npm start” i have one erreur. This debug file:

0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'start' ]
2 info using npm@3.9.5
3 info using node@v6.2.2
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.0.0~prestart: magicmirror@2.0.0
6 silly lifecycle magicmirror@2.0.0~prestart: no script for prestart, continuing
7 info lifecycle magicmirror@2.0.0~start: magicmirror@2.0.0
8 verbose lifecycle magicmirror@2.0.0~start: unsafe-perm in lifecycle true
9 verbose lifecycle magicmirror@2.0.0~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/$
10 verbose lifecycle magicmirror@2.0.0~start: CWD: /home/pi/MagicMirror
11 silly lifecycle magicmirror@2.0.0~start: Args: [ '-c', 'electron js/electron.js' ]
12 silly lifecycle magicmirror@2.0.0~start: Returned: code: 1  signal: null
13 info lifecycle magicmirror@2.0.0~start: Failed to exec start script
14 verbose stack Error: magicmirror@2.0.0 start: `electron js/electron.js`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter.<anonymous> (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:245:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:191:7)
14 verbose stack     at ChildProcess.<anonymous> (/usr/lib/node_modules/npm/lib/utils/spawn.js:24:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:191:7)
14 verbose stack     at maybeClose (internal/child_process.js:852:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5)
15 verbose pkgid magicmirror@2.0.0
16 verbose cwd /home/pi/MagicMirror
17 error Linux 4.4.14-v7+
18 error argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
19 error node v6.2.2
20 error npm  v3.9.5
21 error code ELIFECYCLE
22 error magicmirror@2.0.0 start: `electron js/electron.js`
22 error Exit status 1
23 error Failed at the magicmirror@2.0.0 start script 'electron js/electron.js'.
23 error Make sure you have the latest version of node.js and npm installed.
23 error If you do, this is most likely a problem with the magicmirror package,
23 error not with npm itself.
23 error Tell the author that this fails on your system:
23 error     electron js/electron.js
23 error You can get information on how to open an issue for this project with:
23 error     npm bugs magicmirror
23 error Or if that isn't available, you can get their info via:
23 error     npm owner ls magicmirror
23 error There is likely additional logging output above.
24 verbose exit [ 1, true ]

[Neokamikaze]

Hi,

I found my problem. I need start “npm start” directly on my session “pi”.

Thanks all

[Bu52]

@Bangee
first, I’m rather new to the RPi.
Second, I’m having issues installing MM2.

1. started with a 32G sd and installed Raspian.
2. then did sudo apt-get update, followed by sudo apt-get upgrade.
3. cd /home/pi.
4. Then curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh | bash
5. All went well, except the last lines, which were:
   Cloning MagicMirror Done!
   Installing dependencies …
   bash: line 108: npm: command not found
   Unable to install dependencies!
6. the cd ~/MagicMirror followed by npm start
   I get the following error message, “bash: npm: command not found”.
   What am I doing wrong, please.

[KirAsh4]

Missing some info here: Which Raspberry Pi? Which version of Rasbian? Have you tried following the complete installation guide, from unboxing to having MM² up and running?

[Bu52]

@KirAsh4 It is a RPi 3. Raspian is version 1.9.2. I did it all with one exception. I used Noobs to install Raspian instead of installing Raspian directly to my SD Card. All else is the same.

I will try it again without using Noobs.

[KirAsh4]

The NOOBS installation isn’t a complete version of Jessie, unfortunately. It’s a slightly “lighter” version to fit on the card with the other OS versions.

[Bu52]

@KirAsh4 Thank-you. I think I’m making good progress because it is getting past the dependancies. However, when I start ‘npm start’ I get about a list of error lines. If I can figure out how to upload files, I will send a text file of the error responses and the npm-debug.log file.
1_1468859943952_npm-debug.log 0_1468859943950_err.txt

[Bu52]

Hi @KirAsh4 ,
I found the problem. Well, I didn’t. It was under Neokamikaze’s post. I had been using PuTTY in the installation because it made it easier and more accurate to cut and paste directions. The errors were during that PuTTY session. When I key in “npm start” from a command windows directly on the RPi 3, it comes up with the proper screen.

I still have some additional issues, but IT RUNS!! thank-you for your help. I proved I couldn’t have done it myself.

And thank-you, too, Neokamikaze.

[KirAsh4]

Right. If you had followed the guide, you would’ve noticed that nowhere does it talk about using a client to connect and perform the various commands. You need to access it with a keyboard attached anyway to do the initial configuration before you can connect remotely, so rather than introduce another variable (having someone install something else), I opted not to do that.

That said, I’ll make a note in the guide. When connecting remotely, you must run the command as:

$ DISPLAY=:0 npm start