Read the statement by Michael Teeuw here.
Starting MagicMirror v2 beta
-
Which version of Rasbian are you using?
-
@00conman This will not help, since there seems to be an issue with electron.
-
Oh… okay. Sorry for the mislead I’m still learning the workings.
-
@00conman No worries! PM2 is just a tool to keep the process running. If the MM fails/quits, PM2 will restart it.
-
@MichMich
Hi , version of m’y raspbian using lsb_release -a:Distributor ID: Raspbian
Description: Raspbian GNU/Linux 8.0 (jessie)
Release: 8.0
Codename: jessie -
Could you give the electron quick start a try?
https://github.com/electron/electron-quick-startIf that one doesn’t work either, its an Electron issue.
-
results is:
> electron-quick-start@1.0.0 start /home/pi/MagicMirror/electron-quick-start > electron main.js npm ERR! Linux 4.1.19-v7+ npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" npm ERR! node v6.1.0 npm ERR! npm v3.8.6 npm ERR! code ELIFECYCLE npm ERR! electron-quick-start@1.0.0 start: `electron main.js` npm ERR! Exit status 1 npm ERR! npm ERR! Failed at the electron-quick-start@1.0.0 start script 'electron main.js'. npm ERR! Make sure you have the latest version of node.js and npm installed. npm ERR! If you do, this is most likely a problem with the electron-quick-start package, npm ERR! not with npm itself. npm ERR! Tell the author that this fails on your system: npm ERR! electron main.js npm ERR! You can get information on how to open an issue for this project with: npm ERR! npm bugs electron-quick-start npm ERR! Or if that isn't available, you can get their info via: npm ERR! npm owner ls electron-quick-start npm ERR! There is likely additional logging output above. npm ERR! Please include the following file with any support request: npm ERR! /home/pi/MagicMirror/electron-quick-start/npm-debug.log pi@mirror2:~/MagicMirror/electron-quick-start $ cat /home/pi/MagicMirror/electron-quick-start/npm-debug.log 0 info it worked if it ends with ok 1 verbose cli [ '/usr/local/bin/node', '/usr/local/bin/npm', 'start' ] 2 info using npm@3.8.6 3 info using node@v6.1.0 4 verbose run-script [ 'prestart', 'start', 'poststart' ] 5 info lifecycle electron-quick-start@1.0.0~prestart: electron-quick-start@1.0.0 6 silly lifecycle electron-quick-start@1.0.0~prestart: no script for prestart, continuing 7 info lifecycle electron-quick-start@1.0.0~start: electron-quick-start@1.0.0 8 verbose lifecycle electron-quick-start@1.0.0~start: unsafe-perm in lifecycle true 9 verbose lifecycle electron-quick-start@1.0.0~start: PATH: /usr/local/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/electron-quick-start/node_modules/.bin:/usr/local/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games 10 verbose lifecycle electron-quick-start@1.0.0~start: CWD: /home/pi/MagicMirror/electron-quick-start 11 silly lifecycle electron-quick-start@1.0.0~start: Args: [ '-c', 'electron main.js' ] 12 silly lifecycle electron-quick-start@1.0.0~start: Returned: code: 1 signal: null 13 info lifecycle electron-quick-start@1.0.0~start: Failed to exec start script 14 verbose stack Error: electron-quick-start@1.0.0 start: `electron main.js` 14 verbose stack Exit status 1 14 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/lib/utils/lifecycle.js:239: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/local/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:850:16) 14 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:215:5) 15 verbose pkgid electron-quick-start@1.0.0 16 verbose cwd /home/pi/MagicMirror/electron-quick-start 17 error Linux 4.1.19-v7+ 18 error argv "/usr/local/bin/node" "/usr/local/bin/npm" "start" 19 error node v6.1.0 20 error npm v3.8.6 21 error code ELIFECYCLE 22 error electron-quick-start@1.0.0 start: `electron main.js` 22 error Exit status 1 23 error Failed at the electron-quick-start@1.0.0 start script 'electron main.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 electron-quick-start package, 23 error not with npm itself. 23 error Tell the author that this fails on your system: 23 error electron main.js 23 error You can get information on how to open an issue for this project with: 23 error npm bugs electron-quick-start 23 error Or if that isn't available, you can get their info via: 23 error npm owner ls electron-quick-start 23 error There is likely additional logging output above. 24 verbose exit [ 1, true ] -
There seems to be an issue with electron on your RPi. Are you sure you are running it on a Pi 2? (And not a B+, they look very much alike…)
If so, I suggest you open an issue in the electron repository.
-
-
I raised a ticket for m’y issue with electron-quick-start… hope it will be quick…
-
Still don’t have any news… from electron-quick-start, so still can’t use MagicMirror v2-beta :'(
-
While You’re waiting, You could start the app using ‘node serveronly’ in this case you’ll have to use an other browser.
-
Hi there,
got it running using the serveronly feature… on my laptop, not with my “old” RPI1… (display is weired)
But on my laptop, got some NULL lines…I got also issues with calendar and news while Mirror v2-beta was using wifi connection, since i moved it to a wired connection, i got calendar and news… if that helps…
-
Got the same problem.
Had MMv1 running for some months, now wanted to update to v2.Yesterday i installed it manually and it worked from the beginning.
After that i thought about a clean Jessie Install because of the autostarting stuff from MMv1.
Today i installed Jessie and MMv2 manually again, but now i got the same error msg :(
I already tried the electron-quick-start and it worked.
-
Have you tried using the automatic installer? A week ago I cleared my Pi model b 3 and used the auto starter. Note: you need to copy the config sample to js.
-
WoW. after i deinstalled all node stuff with this
apt-get --purge remove node apt-get --purge remove nodejs apt-get autoremove rebootreinstalling node 4.0.0 with this
wget https://nodejs.org/dist/v4.0.0/node-v4.0.0-linux-armv7l.tar.gz tar -xvf node-v4.0.0-linux-armv7l.tar.gz cd node-v4.0.0-linux-armv7l sudo cp -R * /usr/local/and THEN installing it with the autoinstaller, it works.
Thanks :D
Note from forum staff: Please use Markdown on your code/shell snippets so your post is better readable! :)
-
I think skipping the node 4 part would have worked as well. Since the installer installs node for you.
-
i tried this first, but didnt work for me either.
i even tried reinstalling jessie image + using installer and it didn’t worked. :D
-
@feuerball That’s weird. That’s how I did it. And it worked.
-
I can also verify this as I just setup a brand new rPi yesterday. Downloaded a fresh copy of jessie, booted up the rPi, did the setup for it, made sure all apps were up to date (with
'sudo apt-get update ; sudo apt-get upgrade'then installed MM as per the wiki’s instructions. Done.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login