Read the statement by Michael Teeuw here.
MM not starting after install
-
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 foundlibnss3.so
to be missing… let’s follow this route and see where it leads me… -
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…
-
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
-
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.
-
@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.
-
@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?
-
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…