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

MM crashes after latest update



  • I installed the latest update (v2.11) to MM but now it crashes after starting up. Sometimes it will be stable for 30 minutes or so but then it crashes again.

    I am pretty good at searching but I can’t find a solution.

    I have updated my node and I have deleted and rebuilt all of my node modules with no luck.

    I would appreciate any help. Here is a copy of my last debug log

    0 info it worked if it ends with ok
    1 verbose cli [ '/home/pi/.nvm/versions/node/v10.19.0/bin/node',
    1 verbose cli   '/home/pi/.nvm/versions/node/v10.19.0/bin/npm',
    1 verbose cli   'start',
    1 verbose cli   'dev' ]
    2 info using npm@6.13.4
    3 info using node@v10.19.0
    4 verbose run-script [ 'prestart', 'start', 'poststart' ]
    5 info lifecycle magicmirror@2.11.0~prestart: magicmirror@2.11.0
    6 info lifecycle magicmirror@2.11.0~start: magicmirror@2.11.0
    7 verbose lifecycle magicmirror@2.11.0~start: unsafe-perm in lifecycle true
    8 verbose lifecycle magicmirror@2.11.0~start: PATH: /home/pi/.nvm/versions/node/v10.19.0/lib/node_modules/npm/node_modules/npm-lifecycle/node-gyp-bin:/home/pi/MagicMirror/node_modules/.bin:/home/pi/.nvm/versions/node/v10.19.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/local/games:/usr/games
    9 verbose lifecycle magicmirror@2.11.0~start: CWD: /home/pi/MagicMirror
    10 silly lifecycle magicmirror@2.11.0~start: Args: [ '-c',
    10 silly lifecycle   'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js "dev"' ]
    11 silly lifecycle magicmirror@2.11.0~start: Returned: code: 1  signal: null
    12 info lifecycle magicmirror@2.11.0~start: Failed to exec start script
    13 verbose stack Error: magicmirror@2.11.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js "dev"`
    13 verbose stack Exit status 1
    13 verbose stack     at EventEmitter. (/home/pi/.nvm/versions/node/v10.19.0/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. (/home/pi/.nvm/versions/node/v10.19.0/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.11.0
    15 verbose cwd /home/pi/MagicMirror
    16 verbose Linux 4.19.113-v7+
    17 verbose argv "/home/pi/.nvm/versions/node/v10.19.0/bin/node" "/home/pi/.nvm/versions/node/v10.19.0/bin/npm" "start" "dev"
    18 verbose node v10.19.0
    19 verbose npm  v6.13.4
    20 error code ELIFECYCLE
    21 error errno 1
    22 error magicmirror@2.11.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js "dev"`
    22 error Exit status 1
    23 error Failed at the magicmirror@2.11.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 ]
    


  • did you do an npm install in the MagicMirror folder after the git pull?



  • Yes. I even did a git pull in all of the modules with package.json file.



  • @joberbroeckling and an npm install in those module folders too… (git pull wasn’t required, only the npm install)



  • Yes. That was what I meant. I did a npm install in all of the module folders. It seems like the system load has increased since the latest update.



  • what modules do you have installed?

    can u run my update script…

    bash -c "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" force
    

    then the update info will be in the ~/MagicMirror/installers/upgrade.log



  • @sdetweil said in MM crashes after latest update:

    bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)” force

    I updated with the script and I am seeing the same issue.



  • @joberbroeckling on, can u post the upgrade.log



  • Upgrade started - Thu Apr  2 18:40:15 MST 2020
    system is Linux raspberrypi 4.19.113-v7+ #1300 SMP Thu Mar 26 16:53:09 GMT 2020 armv7l GNU/Linux
    the os is Distributor ID: Raspbian Description: Raspbian GNU/Linux 9.11 (stretch) Release: 9.11 Codename: stretch
    user requested to force apply changes
    doing test run = false
    
    saving custom.css
    remote name = origin
    upgrading from version 2.11.0 to 2.11.0
    fetching latest revisions
    git fetch rc=0
    current branch = master
    On branch master
    Your branch is up-to-date with 'origin/master'.
    Changes not staged for commit:
      (use "git add ..." to update what will be committed)
      (use "git checkout -- ..." to discard changes in working directory)
    
    	modified:   package-lock.json
    
    Untracked files:
      (use "git add ..." to include in what will be committed)
    
    	core
    	css/custom.css.backup
    	css/save_custom.css
    
    no changes added to commit (use "git add" and/or "git commit -a")
    there are 1 local files that are different than the master repo
    
       package-lock.json
    
    save/restore files selection = n
    restoring package-lock.json from repo
    test merge result rc='' , if empty, no conflicts
    executing merge, apply specified
    merge result rc= 0
     Already up-to-date.
    processor architecture is armv7l
    updating MagicMirror runtime, please wait
    
    > electron@6.1.7 postinstall /home/pi/MagicMirror/node_modules/electron
    > node install.js
    
    
    > magicmirror@2.11.0 install /home/pi/MagicMirror
    > echo "Installing vendor files ...
    " && cd vendor && npm install --loglevel=error
    
    Installing vendor files ...
    
    audited 220 packages in 11.443s
    found 8 vulnerabilities (7 low, 1 high)
      run `npm audit fix` to fix them, or `npm audit` for details
    
    > magicmirror@2.11.0 postinstall /home/pi/MagicMirror
    > npm run install-fonts && echo "MagicMirror installation finished successfully! 
    "
    
    
    > magicmirror@2.11.0 install-fonts /home/pi/MagicMirror
    > echo "Installing fonts ...
    " && cd fonts && npm install --loglevel=error
    
    Installing fonts ...
    
    audited 1 package in 0.963s
    found 0 vulnerabilities
    
    MagicMirror installation finished successfully! 
    
    added 3 packages from 39 contributors, updated 30 packages and audited 3040 packages in 90.677s
    
    47 packages are looking for funding
      run `npm fund` for details
    
    found 23 vulnerabilities (20 low, 3 moderate)
      run `npm audit fix` to fix them, or `npm audit` for details
    npm install completed - Thu Apr  2 18:42:09 MST 2020 on base
    downloading dumpactivemodules script
    
    processing dependency changes for active modules with package.json files
    processing for module MMM-DarkSkyForecast please wait
    ----------------------------------
    audited 12116 packages in 19.742s
    
    1 package is looking for funding
      run `npm fund` for details
    
    found 0 vulnerabilities
    
    processing complete for module MMM-DarkSkyForecast
    processing for module MMM-homeassistant-sensors please wait
    ----------------------------------
    audited 1 package in 1.058s
    found 0 vulnerabilities
    
    processing complete for module MMM-homeassistant-sensors
    processing for module MMM-Remote-Control please wait
    ----------------------------------
    audited 36 packages in 1.997s
    found 0 vulnerabilities
    
    processing complete for module MMM-Remote-Control
    processing for module MMM-CountDown please wait
    ----------------------------------
    npm WARN grunt-stylelint@0.14.0 requires a peer of stylelint@^13.2.0 but none is installed. You must install peer dependencies yourself.
    npm WARN stylelint-config-recommended@3.0.0 requires a peer of stylelint@>=10.1.0 but none is installed. You must install peer dependencies yourself.
    npm WARN stylelint-config-standard@20.0.0 requires a peer of stylelint@>=10.1.0 but none is installed. You must install peer dependencies yourself.
    npm WARN MMM-CountDown@1.0.0 No repository field.
    
    audited 429 packages in 9.677s
    
    9 packages are looking for funding
      run `npm fund` for details
    
    found 0 vulnerabilities
    
    processing complete for module MMM-CountDown
    processing for module MMM-CountDown please wait
    ----------------------------------
    npm WARN grunt-stylelint@0.14.0 requires a peer of stylelint@^13.2.0 but none is installed. You must install peer dependencies yourself.
    npm WARN stylelint-config-recommended@3.0.0 requires a peer of stylelint@>=10.1.0 but none is installed. You must install peer dependencies yourself.
    npm WARN stylelint-config-standard@20.0.0 requires a peer of stylelint@>=10.1.0 but none is installed. You must install peer dependencies yourself.
    npm WARN MMM-CountDown@1.0.0 No repository field.
    
    audited 429 packages in 10.51s
    
    9 packages are looking for funding
      run `npm fund` for details
    
    found 0 vulnerabilities
    
    processing complete for module MMM-CountDown
    processing for module MMM-CountDown please wait
    ----------------------------------
    npm WARN grunt-stylelint@0.14.0 requires a peer of stylelint@^13.2.0 but none is installed. You must install peer dependencies yourself.
    npm WARN stylelint-config-recommended@3.0.0 requires a peer of stylelint@>=10.1.0 but none is installed. You must install peer dependencies yourself.
    npm WARN stylelint-config-standard@20.0.0 requires a peer of stylelint@>=10.1.0 but none is installed. You must install peer dependencies yourself.
    npm WARN MMM-CountDown@1.0.0 No repository field.
    
    audited 429 packages in 9.549s
    
    9 packages are looking for funding
      run `npm fund` for details
    
    found 0 vulnerabilities
    
    processing complete for module MMM-CountDown
    processing for module MMM-SystemStats please wait
    ----------------------------------
    audited 1 package in 1.046s
    found 0 vulnerabilities
    
    processing complete for module MMM-SystemStats
    processing for module MMM-CalendarExt2 please wait
    ----------------------------------
    audited 5 packages in 1.106s
    found 0 vulnerabilities
    
    processing complete for module MMM-CalendarExt2
    restoring custom.css
    removing git alias
    Upgrade ended - Thu Apr  2 18:43:39 MST 2020
    


  • @joberbroeckling said in MM crashes after latest update:

    MMM-Remote-Control

    has an issue against it not working on 2.11, and

    maybe MMM-homeassistant-sensors… I can’t tell, there are 6 different versions… which one do you have?
    (git remote -v in the module folder will give the git repo name).


Log in to reply