MagicMirror² v2.13.0 is available! For more information about this release, check out this topic.

Failed at the magicmirror@2.8.0 start script



  • When I restart the Raspberry (PRI3B+) I get this error in the pm2 log:

    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! magicmirror@2.8.0 start: `sh run-start.sh`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the magicmirror@2.8.0 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/pi/.npm/_logs/2019-07-12T19_29_14_310Z-debug.log
    ATTENTION: default value of option force_s3tc_enable overridden by environment.
    ATTENTION: default value of option force_s3tc_enable overridden by environment.
    ATTENTION: default value of option force_s3tc_enable overridden by environment.
    npm ERR! code ELIFECYCLE
    npm ERR! errno 1
    npm ERR! magicmirror@2.8.0 start: `sh run-start.sh`
    npm ERR! Exit status 1
    npm ERR!
    npm ERR! Failed at the magicmirror@2.8.0 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/pi/.npm/_logs/2019-07-12T19_59_43_770Z-debug.log
    

    And this is the output of the npm log:

    0 info it worked if it ends with ok
    1 verbose cli [ '/usr/bin/node', '/usr/bin/npm', 'start' ]
    2 info using npm@6.9.0
    3 info using node@v10.16.0
    4 verbose run-script [ 'prestart', 'start', 'poststart' ]
    5 info lifecycle magicmirror@2.8.0~prestart: magicmirror@2.8.0
    6 info lifecycle magicmirror@2.8.0~start: magicmirror@2.8.0
    7 verbose lifecycle magicmirror@2.8.0~start: unsafe-perm in lifecycle true
    8 verbose lifecycle magicmirror@2.8.0~start: PATH: /usr/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/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.8.0~start: CWD: /home/pi/MagicMirror
    10 silly lifecycle magicmirror@2.8.0~start: Args: [ '-c', 'sh run-start.sh' ]
    11 silly lifecycle magicmirror@2.8.0~start: Returned: code: 1  signal: null
    12 info lifecycle magicmirror@2.8.0~start: Failed to exec start script
    13 verbose stack Error: magicmirror@2.8.0 start: `sh 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:301: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.8.0
    15 verbose cwd /home/pi/MagicMirror
    16 verbose Linux 4.19.42-v7+
    17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
    18 verbose node v10.16.0
    19 verbose npm  v6.9.0
    20 error code ELIFECYCLE
    21 error errno 1
    22 error magicmirror@2.8.0 start: `sh run-start.sh`
    22 error Exit status 1
    23 error Failed at the magicmirror@2.8.0 start script.
    23 error This is probably not a problem with npm. There is likely additional logging output above.
    24 verbose exit [ 1, true ]
    

    The MagicMirror script starts though … and the modules are loaded …
    How can I fix this?



  • I got this after I set the Pi to not auto-start Desktop, reboot my Pi to implement my change. After reboot it starts in CLI, then I got the above message.
    I changed back so Desktop will auto-start, reboot but still same message as above.
    Was working perfect before.
    RPi 3B
    Raspbian Buster



  • My mistake was that I had chossen to auto-start Desktop but not Autologin, after I changed to Autologin with Desktop everything was fine again.


Log in to reply