1. Home
  2. Troubleshooting
  3. Can not start MM anymore
MagicMirror² v2.13.0 is available! For more information about this release, check out this topic.

Can not start MM anymore

  • fox

    Hi, i have some problems - mainly after the latest update.

    I cant start MM anymore.

    The logfile (/home/pi/.npm/_logs/2017-10-14T02_58_48_833Z-debug.log)

    0 info it worked if it ends with ok
1 verbose cli [ '/usr/bin/nodejs', '/usr/bin/npm', 'bugs', 'magicmirror' ]
2 info using npm@4.2.0
3 info using node@v7.10.1
4 silly fetchPackageMetaData magicmirror
5 silly fetchNamedPackageData magicmirror
6 silly mapToRegistry name magicmirror
7 silly mapToRegistry using default registry
8 silly mapToRegistry registry https://registry.npmjs.org/
9 silly mapToRegistry data Result {
9 silly mapToRegistry   raw: 'magicmirror',
9 silly mapToRegistry   scope: null,
9 silly mapToRegistry   escapedName: 'magicmirror',
9 silly mapToRegistry   name: 'magicmirror',
9 silly mapToRegistry   rawSpec: '',
9 silly mapToRegistry   spec: 'latest',
9 silly mapToRegistry   type: 'tag' }
10 silly mapToRegistry uri https://registry.npmjs.org/magicmirror
11 verbose request uri https://registry.npmjs.org/magicmirror
12 verbose request no auth needed
13 info attempt registry request try #1 at 04:58:46
14 verbose request id 3fa149b5af7f1094
15 verbose etag W/"56fbae0b-bef"
16 verbose lastModified Wed, 30 Mar 2016 10:44:27 GMT
17 http request GET https://registry.npmjs.org/magicmirror
18 http 304 https://registry.npmjs.org/magicmirror
19 verbose headers { date: 'Sat, 14 Oct 2017 02:58:46 GMT',
19 verbose headers   via: '1.1 varnish',
19 verbose headers   'cache-control': 'max-age=300',
19 verbose headers   etag: 'W/"56fbae0b-bef"',
19 verbose headers   age: '22',
19 verbose headers   connection: 'keep-alive',
19 verbose headers   'x-served-by': 'cache-hhn1550-HHN',
19 verbose headers   'x-cache': 'HIT',
19 verbose headers   'x-cache-hits': '1',
19 verbose headers   'x-timer': 'S1507949927.624052,VS0,VE0',
19 verbose headers   vary: 'Accept-Encoding, Accept' }
20 silly get cb [ 304,
20 silly get   { date: 'Sat, 14 Oct 2017 02:58:46 GMT',
20 silly get     via: '1.1 varnish',
20 silly get     'cache-control': 'max-age=300',
20 silly get     etag: 'W/"56fbae0b-bef"',
20 silly get     age: '22',
20 silly get     connection: 'keep-alive',
20 silly get     'x-served-by': 'cache-hhn1550-HHN',
20 silly get     'x-cache': 'HIT',
20 silly get     'x-cache-hits': '1',
20 silly get     'x-timer': 'S1507949927.624052,VS0,VE0',
20 silly get     vary: 'Accept-Encoding, Accept' } ]
21 verbose etag https://registry.npmjs.org/magicmirror from cache
22 verbose get saving magicmirror to /home/pi/.npm/registry.npmjs.org/magicmirror/.cache.json
23 verbose correctMkdir /home/pi/.npm correctMkdir not in flight; initializing
24 silly bugs url https://github.com/MichMich/MagicMirror/issues
25 verbose stack Error: Command failed: xdg-open https://github.com/MichMich/MagicMirror/issues
25 verbose stack /usr/bin/xdg-open: 1: eval: www-browser: not found
25 verbose stack /usr/bin/xdg-open: 1: eval: links2: not found
25 verbose stack /usr/bin/xdg-open: 1: eval: elinks: not found
25 verbose stack /usr/bin/xdg-open: 1: eval: links: not found
25 verbose stack /usr/bin/xdg-open: 1: eval: lynx: not found
25 verbose stack /usr/bin/xdg-open: 1: eval: w3m: not found
25 verbose stack xdg-open: no method available for opening 'https://github.com/MichMich/MagicMirror/issues'
25 verbose stack
25 verbose stack     at ChildProcess.exithandler (child_process.js:205:12)
25 verbose stack     at emitTwo (events.js:106:13)
25 verbose stack     at ChildProcess.emit (events.js:194:7)
25 verbose stack     at maybeClose (internal/child_process.js:899:16)
25 verbose stack     at Socket. (internal/child_process.js:342:11)
25 verbose stack     at emitOne (events.js:96:13)
25 verbose stack     at Socket.emit (events.js:191:7)
25 verbose stack     at Pipe._handle.close [as _onclose] (net.js:511:12)
26 verbose cwd /home/pi/MagicMirror
27 error Linux 4.9.35-v7+
28 error argv "/usr/bin/nodejs" "/usr/bin/npm" "bugs" "magicmirror"
29 error node v7.10.1
30 error npm  v4.2.0
31 error code 3
32 error Command failed: xdg-open https://github.com/MichMich/MagicMirror/issues
32 error /usr/bin/xdg-open: 1: eval: www-browser: not found
32 error /usr/bin/xdg-open: 1: eval: links2: not found
32 error /usr/bin/xdg-open: 1: eval: elinks: not found
32 error /usr/bin/xdg-open: 1: eval: links: not found
32 error /usr/bin/xdg-open: 1: eval: lynx: not found
32 error /usr/bin/xdg-open: 1: eval: w3m: not found
32 error xdg-open: no method available for opening 'https://github.com/MichMich/MagicMirror/issues'
33 error If you need help, you may report this error at:
33 error     
34 verbose exit [ 1, true ]

    and tail of the mm-error file:

    npm ERR! Please include the following file with any support request:
npm ERR!     /home/pi/.npm/_logs/2017-10-14T02_58_23_366Z-debug.log
error: object file .git/objects/54/95af1f76e98870ede078c41304a08747792caa is empty
error: object file .git/objects/54/95af1f76e98870ede078c41304a08747792caa is empty
fatal: loose object 5495af1f76e98870ede078c41304a08747792caa (stored in .git/objects/54/95af1f76e98870ede078c41304a08747792caa) is corrupt
fatal: The remote end hung up unexpectedly

Sat Oct 14 2017 04:58:52 GMT+0200 (CEST) - WatchDog: Heartbeat timeout. Frontend might have crashed. Exit now.

npm ERR! Linux 4.9.35-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v7.10.1
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.1.3 start: `sh run-start.sh`
npm ERR! Exit status 1
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/.npm/_logs/2017-10-14T02_58_52_966Z-debug.log
error: object file .git/objects/54/95af1f76e98870ede078c41304a08747792caa is empty
error: object file .git/objects/54/95af1f76e98870ede078c41304a08747792caa is empty
fatal: loose object 5495af1f76e98870ede078c41304a08747792caa (stored in .git/objects/54/95af1f76e98870ede078c41304a08747792caa) is corrupt
fatal: The remote end hung up unexpectedly

Sat Oct 14 2017 04:59:23 GMT+0200 (CEST) - WatchDog: Heartbeat timeout. Frontend might have crashed. Exit now.

npm ERR! Linux 4.9.35-v7+
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "start"
npm ERR! node v7.10.1
npm ERR! npm  v4.2.0
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! magicmirror@2.1.3 start: `sh run-start.sh`
npm ERR! Exit status 1
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/.npm/_logs/2017-10-14T02_59_23_738Z-debug.log
error: object file .git/objects/54/95af1f76e98870ede078c41304a08747792caa is empty
error: object file .git/objects/54/95af1f76e98870ede078c41304a08747792caa is empty
fatal: loose object 5495af1f76e98870ede078c41304a08747792caa (stored in .git/objects/54/95af1f76e98870ede078c41304a08747792caa) is corrupt
fatal: The remote end hung up unexpectedly
    0 Mykle1 1 Reply
  • Mykle1
    Project Sponsor Module Developer

    @fox said in Can not start MM anymore:

    I cant start MM anymore.

    Most likely the update and/or the new dependencies failed to completely install.

    Long shot: run npm istall in the MagicMirror directory and try to run your mirror.

    Best shot: https://forum.magicmirror.builders/topic/5274/how-to-manually-install-mm-on-your-pi-for-absolute-beginners

    1
  • cowboysdude
    Project Sponsor Module Developer

    Other case is don’t install updates if you don’t need to…

    1
Log in to reply
 
Enjoying MagicMirror? Please consider a donation!