Read the statement by Michael Teeuw here.
updated installer script available for testing
-
@bhepler thanks… i got some new sd cards today, so I will test too.
-
@sdetweil - Brand new Buster installation on a RPi 3B+. Installation script worked as expected.
I had trouble with pm2 on my existing mirror too. I ended up upgrading to the latest pm2 in order to get it to remember to start on boot.
At this point, I think your script is handling it properly. Thanks for the quick replies!
-
@bhepler oh, there is a script for just pm2 as well.
Thx for feedback.
-
Hey sam (@sdetweil ),
Thanks for this, made my life a lot easier.
So, I just did a new build with Buster on a RPI Zero W. All looked good and I have configured mm2 to start on reboot of the Pi. I am start/stop/restart and check the status of mm2 and is looks to be working, the mm2 logs are also good with no error logs.
The problem I am facing is that the magicMirror page via chromium seems to try and load (white screen which changes to a pure black screen) however seems to fail/crash and go back to the Raspbian desktop.
This happens when I reboot the pi and also when I manually try to start/restart the mm2 service.
Anything you think I am missing?
Thanks
-
@NathTheDude if u start the chromium browser from the desktop does it work?
-
U may need to increase the swap space. Pi 0 has very little memory.
https://wpitchoune.net/tricks/raspberry_pi3_increase_swap_size.html
-
Thanks @sdetweil , after a couple of reboots this is now working as expected. Not sure what the issue was, I will have to keep an eye on it. Thanks for the link on swap space, I will also look in that direction if I have any more of the same issues.
-
@NathTheDude ok… let me know if there are any other issues…
-
@sdetweil this installer script is now the script in 2.10…
I will close/lock this topic in a couple days
-
Should I install electron with --arch=armv7l ?
-
@jorgnyg Yea guess so. Installation fails on rpi zero. So I deleted the electron folder from node_modules, and ran npm install --arch=armv7l electron@3.0.13
-
@jorgnyg doesn’t fail on my pi 0.
Can u send me the install.log
-
@sdetweil note that we made electron optional. There is no armv6l at node 10
So we will run in split mode use chromium -
@sdetweil sure thing. Guess this is the most relevant error
26380 verbose stack Error: electron-chromedriver@1.8.0 install: `node ./download-chromedriver.js` 26380 verbose stack Exit status 1 26380 verbose stack at EventEmitter.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16) 26380 verbose stack at EventEmitter.emit (events.js:198:13) 26380 verbose stack at ChildProcess.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14) 26380 verbose stack at ChildProcess.emit (events.js:198:13) 26380 verbose stack at maybeClose (internal/child_process.js:982:16) 26380 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5) 26381 verbose pkgid electron-chromedriver@1.8.0 26382 verbose cwd /home/pi/MagicMirror 26383 verbose Linux 4.19.75+ 26384 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" 26385 verbose node v10.18.1 26386 verbose npm v6.13.4 26387 error code ELIFECYCLE 26388 error errno 1 26389 error electron-chromedriver@1.8.0 install: `node ./download-chromedriver.js` 26389 error Exit status 1 26390 error Failed at the electron-chromedriver@1.8.0 install script. 26390 error This is probably not a problem with npm. There is likely additional logging output above. 26391 verbose exit [ 1, true ] -
@jorgnyg the run-start.sh script now handles this problem and launches chromium instead of electron to connect to mm in serveronly mode
-
@sdetweil got it!
-
Hi - firstly thanks for putting together this installer!
I am running Raspbian on RP3b+ as a fresh install using the command
curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/raspberry.sh | bash
Installer indicated successful install of MagicMirror.
Using SSH DISPLAY=:0 npm start gives the following error:
magicmirror@2.10.1 start /home/jojo/MagicMirror
./run-start.shNo protocol specified
(electron:17801): Gtk-WARNING **: 18:36:26.218: cannot open display: :0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.10.1 start:./run-start.sh
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the magicmirror@2.10.1 start script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.npm ERR! A complete log of this run can be found in:
npm ERR! /home/jojo/.npm/_logs/2020-01-25T18_36_26_308Z-debug.logDebug log contents are as follows:
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@6.13.4
3 info using node@v10.18.1
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.10.1~prestart: magicmirror@2.10.1
6 info lifecycle magicmirror@2.10.1~start: magicmirror@2.10.1
7 verbose lifecycle magicmirror@2.10.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.10.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/jojo/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle magicmirror@2.10.1~start: CWD: /home/jojo/MagicMirror
10 silly lifecycle magicmirror@2.10.1~start: Args: [ ‘-c’, ‘./run-start.sh’ ]
11 silly lifecycle magicmirror@2.10.1~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.10.1~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.10.1 start:./run-start.sh
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid magicmirror@2.10.1
15 verbose cwd /home/jojo/MagicMirror
16 verbose Linux 4.19.75-v7+
17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
18 verbose node v10.18.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.10.1 start:./run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.10.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ]Any thoughts on how to troubleshoot? Many thanks.
-
@jthirasilpa seems like you are running in console mode, instead of graphical mode.
Mm requires the full desktop.
-
@sdetweil Thanks. The RP is running a full desktop - if I run npm start directly from the RP, the debug log gives the following output:
0 info it worked if it ends with ok
1 verbose cli [ ‘/usr/bin/node’, ‘/usr/bin/npm’, ‘start’ ]
2 info using npm@6.13.4
3 info using node@v10.18.1
4 verbose run-script [ ‘prestart’, ‘start’, ‘poststart’ ]
5 info lifecycle magicmirror@2.10.1~prestart: magicmirror@2.10.1
6 info lifecycle magicmirror@2.10.1~start: magicmirror@2.10.1
7 verbose lifecycle magicmirror@2.10.1~start: unsafe-perm in lifecycle true
8 verbose lifecycle magicmirror@2.10.1~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/jojo/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
9 verbose lifecycle magicmirror@2.10.1~start: CWD: /home/jojo/MagicMirror
10 silly lifecycle magicmirror@2.10.1~start: Args: [ ‘-c’, ‘./run-start.sh’ ]
11 silly lifecycle magicmirror@2.10.1~start: Returned: code: 1 signal: null
12 info lifecycle magicmirror@2.10.1~start: Failed to exec start script
13 verbose stack Error: magicmirror@2.10.1 start:./run-start.sh
13 verbose stack Exit status 1
13 verbose stack at EventEmitter. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/index.js:332:16)
13 verbose stack at EventEmitter.emit (events.js:198:13)
13 verbose stack at ChildProcess. (/usr/lib/node_modules/npm/node_modules/npm-lifecycle/lib/spawn.js:55:14)
13 verbose stack at ChildProcess.emit (events.js:198:13)
13 verbose stack at maybeClose (internal/child_process.js:982:16)
13 verbose stack at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
14 verbose pkgid magicmirror@2.10.1
15 verbose cwd /home/jojo/MagicMirror
16 verbose Linux 4.19.75-v7+
17 verbose argv “/usr/bin/node” “/usr/bin/npm” “start”
18 verbose node v10.18.1
19 verbose npm v6.13.4
20 error code ELIFECYCLE
21 error errno 1
22 error magicmirror@2.10.1 start:./run-start.sh
22 error Exit status 1
23 error Failed at the magicmirror@2.10.1 start script.
23 error This is probably not a problem with npm. There is likely additional logging output above.
24 verbose exit [ 1, true ] -
@jthirasilpa change line 1 of run-start.sh to be
#~/bin/bash -xthen do the npm start again…
also do
which chromium-browsermy system returns
/usr/bin/chromium-browsercan u send me the MagicMirror/installers/upgrade.log via email
same userid as here, at gmail
thanks
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