3. MM not starting after install
MagicMirror² v2.4.1 is available! For more information about this release, check out this topic.
Please read the release notes carefully since this update requires adjustments to your Raspberry Pi configuration!

MM not starting after install

  • A

    Hey there,

    I have a freshly installed RPi3 with jessie-lite, with sudo apt-get update && sudo apt-get upgrade done. I installed MM with bash -c "$(curl -sL https://raw.githubusercontent.com/MichMich/MagicMirror/master/installers/raspberry.sh)" (without any errors) and tried to start with DISPLAY=:0 nohup npm start &
    The error in ~/MagicMirror/nohup.out shows the following:

    > magicmirror@2.1.3 start /home/pi/MagicMirror
> sh run-start.sh

/home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries: libgtk-x11-2.0.so.0: cannot open shared object file: No such file or directory

npm ERR! Linux 4.9.35-v7+
npm ERR! argv "/usr/bin/node" "/usr/bin/npm" "start"
npm ERR! node v6.11.5
npm ERR! npm  v3.10.10
npm ERR! file sh
npm ERR! code ELIFECYCLE
npm ERR! errno ENOENT
npm ERR! syscall spawn
npm ERR! magicmirror@2.1.3 start: `sh run-start.sh`
npm ERR! spawn ENOENT
npm ERR!
npm ERR! Failed at the magicmirror@2.1.3 start script 'sh run-start.sh'.
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 magicmirror package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     sh run-start.sh
npm ERR! You can get information on how to open an issue for this project with:
npm ERR!     npm bugs magicmirror
npm ERR! Or if that isn't available, you can get their info via:
npm ERR!     npm owner ls magicmirror
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/npm-debug.log

    npm-debug.log:

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

    As the error ist talking about x11 I also tried to manually install x11vnc (see here: https://github.com/MichMich/MagicMirror/wiki/Configuring-the-Raspberry-Pi), but that din’t change anything.

    Regards,
    AnduriI

    0 1 Reply
  • Module Developer

    @AnduriI said in MM not starting after install:

    /home/pi/MagicMirror/node_modules/electron/dist/electron: error while loading shared libraries:

    I believe that your dependencies did not fully install for electron, based on the above error message. Try this:

    Move or rename or delete the electron folder from the /home/pi/MagicMirror/node_modules/ directory.

    Then run npm install in the /home/pi/MagicMirror/ directory.

    Then run npm start in the /home/pi/MagicMirror/ directory

    0
  • A

    well that didn’t worked…
    I installed libgtk manually, now a new error: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
    Again, installed that manually and found libnss3.soto be missing… let’s follow this route and see where it leads me…

    0
  • A

    well it looks like this was the last one missing, but still it does not work.
    npm-debug.log:

    0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
2 info using npm@3.10.10
3 info using node@v6.11.5
4 verbose run-script [ 'prestart', 'start', 'poststart' ]
5 info lifecycle magicmirror@2.1.3~prestart: magicmirror@2.1.3
6 silly lifecycle magicmirror@2.1.3~prestart: no script for prestart, continuing
7 info lifecycle magicmirror@2.1.3~start: magicmirror@2.1.3
8 verbose lifecycle magicmirror@2.1.3~start: unsafe-perm in lifecycle true
9 verbose lifecycle magicmirror@2.1.3~start: PATH: /usr/lib/node_modules/npm/bin/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/usr/local/sbin:/usr/l$
10 verbose lifecycle magicmirror@2.1.3~start: CWD: /home/pi/MagicMirror
11 silly lifecycle magicmirror@2.1.3~start: Args: [ '-c', 'sh run-start.sh' ]
12 silly lifecycle magicmirror@2.1.3~start: Returned: code: 1  signal: null
13 info lifecycle magicmirror@2.1.3~start: Failed to exec start script
14 verbose stack Error: magicmirror@2.1.3 start: `sh run-start.sh`
14 verbose stack Exit status 1
14 verbose stack     at EventEmitter. (/usr/lib/node_modules/npm/lib/utils/lifecycle.js:255: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. (/usr/lib/node_modules/npm/lib/utils/spawn.js:40: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:920:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:230:5)
15 verbose pkgid magicmirror@2.1.3
16 verbose cwd /home/pi/MagicMirror
17 error Linux 4.9.35-v7+
18 error argv "/usr/bin/node" "/usr/bin/npm" "start"
19 error node v6.11.5
20 error npm  v3.10.10
21 error code ELIFECYCLE
22 error magicmirror@2.1.3 start: `sh run-start.sh`
22 error Exit status 1
23 error Failed at the magicmirror@2.1.3 start script 'sh run-start.sh'.
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     sh run-start.sh
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 ]

    I don’t see any message saying why it failed…

    0
  • Module Developer

    I’ve never used Jessie lite or run node server only so I am a bit at a loss here. Often, troubleshooting can take longer than re-installation. In which case, I usually recommend a manual install. That has always worked for me, although I only use the full version of Jessie

    0
  • A

    yeah I know what you mean… I will try a re-install with full jessie and manual install. I will report back after that… thanks a lot.

    0 1 Reply

  • @AnduriI If you’re worried about overhead and other useless applications on your Pi, the Complete Setup Tutorial has a useful command to uninstall a lot of the stuff you won’t use in a normal Raspbian image. It will pull out the Wolfram engine, LibreOffice, Minecraft, etc.

    0
  • A

    @bhepler well me using raspbian lite is just a habit and was not to decrease load. I have 3+ RPis all running headless with raspbian lite.
    But doing a re-install was a good idea. Have a full jessie installed now and setup of MM went fine the manuall way. Also it seems to be starting, but I can’t reach it from my pc. Monitor for MM has not yet arrived.

    pi@Spieglein:~/MagicMirror $  DISPLAY=:0 nohup npm start &
[1] 3579
pi@Spieglein:~/MagicMirror $ nohup: ignoriere Eingabe und hänge Ausgabe an „nohup.out“ an

    nohup.out:

    
> magicmirror@2.1.3 start /home/pi/MagicMirror
> sh run-start.sh

Starting MagicMirror: v2.1.3
Loading config ...
Loading module helpers ...
No helper found for module: alert.
Initializing new module helper ...
Module helper loaded: updatenotification
No helper found for module: clock.
Initializing new module helper ...
Module helper loaded: calendar
No helper found for module: compliments.
No helper found for module: currentweather.
No helper found for module: weatherforecast.
Initializing new module helper ...
Module helper loaded: newsfeed
All module helpers loaded.
Starting server on port 8080 ...
You're using a full whitelist configuration to allow for all IPs
Server started ...
Connecting socket for: updatenotification
Connecting socket for: calendar
Starting node helper for: calendar
Connecting socket for: newsfeed
Starting module: newsfeed
Sockets connected & modules started ...
Launching application.
Create new calendar fetcher for url: http://www.calendarlabs.com/templates/ical/US-Holidays.ics - Interval: 300$
Create new news fetcher for url: http://www.nytimes.com/services/xml/rss/nyt/HomePage.xml - Interval: 300000

    config.js:

    /* Magic Mirror Config Sample
 *
 * By Michael Teeuw http://michaelteeuw.nl
 * MIT Licensed.
 *
 * For more information how you can configurate this file
 * See https://github.com/MichMich/MagicMirror#configuration
 *
 */

var config = {
        address: "localhost", // Address to listen on, can be:
                              // - "localhost", "127.0.0.1", "::1" to listen on loopback interface
                              // - another specific IPv4/6 to listen on a specific interface
                              // - "", "0.0.0.0", "::" to listen on any interface
                              // Default, when address config is left out, is "localhost"
        port: 8080,
        ipWhitelist: [], // Set [] to allow all IP addresses
                                                               // or add a specific IPv4 of 192.168.1.5 :
                                                               // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::f$
                                                               // or IPv4 range of 192.168.3.0 --> 192.168.3.15$
                                                               // ["127.0.0.1", "::ffff:127.0.0.1", "::1", "::f$

        language: "de",
        timeFormat: 24,
        units: "metric",

        modules: [
[didn't changed anything below here yet]

    But there is no page available at Spieglein:8080 or [IP]:8080. Did I miss a point in the config?

    0
  • A

    adding an address: "0.0.0.0",did it, I can see the black page of MM in my browser… thanks a lot for your help. Now I’m even more waiting for my mirror and screen to arrive…

    1