MagicMirror Forum
    • Recent
    • Tags
    • Unsolved
    • Solved
    • MagicMirror² Repository
    • Documentation
    • 3rd-Party-Modules
    • Donate
    • Discord
    • Register
    • Login
    A New Chapter for MagicMirror: The Community Takes the Lead
    Read the statement by Michael Teeuw here.

    MM crashing (after pi os update?)

    Scheduled Pinned Locked Moved Bug Hunt
    14 Posts 2 Posters 2.6k Views 2 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • W Offline
      wmx
      last edited by

      Hi folks,
      I’m running MM for a while now with 2.15.0 on a raspi 3B without problems. Since last weekend I discovered several reboots. On weekends the raspi is automatically updating via cron.
      I did not change the config or something else.
      Now the MM does not start any more. I always get these crashes:

      pi@mirror:~ $ ./mm.sh
      
      > magicmirror@2.15.0 start /home/pi/MagicMirror
      > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
      
      [22.04.2021 09:35.55.388] [LOG]   Starting MagicMirror: v2.15.0
      [22.04.2021 09:35.55.400] [LOG]   Loading config ...
      [22.04.2021 09:35.58.743] [LOG]   Starting node helper for: MMM-Remote-Control
      [22.04.2021 09:35.58.765] [LOG]   MMM-MQTT: Starting node helper
      [22.04.2021 09:35.58.768] [LOG]   Starting node_helper for module: MyCovid19
      [22.04.2021 09:36.07.734] [LOG]   active type=countries
      [22.04.2021 09:36.08.739] [LOG]   active type=countries
      [22.04.2021 09:36.11.312] [LOG]   MMM-MQTT: Starting client for:  {
      *** skipped a few MMM-MQTT debug lines***
      }
      [22.04.2021 09:36.11.327] [LOG]   MMM-MQTT: Connecting to mqtt://moon.fritz.box:1883
      [22.04.2021 09:36.12.149] [LOG]   MMM-MQTT connected to mqtt://moon.fritz.box:1883
      [22.04.2021 09:36.12.152] [LOG]   MMM-MQTT: subscribing to sensor/wemos-schuppen-temp
      [22.04.2021 09:36.14.648] [ERROR] Failed to fetch git data for MyCovid19: Error: block timeout reached
      [22.04.2021 09:36.15.933] [ERROR] Failed to fetch git data for MMM-homeassistant-sensors: Error: block timeout reached
      [22.04.2021 09:36.20.992] [ERROR] Failed to fetch git data for default: Error: block timeout reached
      
      <--- Last few GCs --->
      
      [1636:0x77a8000]    47470 ms: Scavenge (reduce) 214.4 (222.7) -> 214.2 (223.0) MB, 16.6 / 0.0 ms  (average mu = 0.616, current mu = 0.417) allocation failure
      [1636:0x77a8000]    47534 ms: Scavenge (reduce) 214.8 (223.3) -> 214.7 (223.3) MB, 22.5 / 0.0 ms  (average mu = 0.616, current mu = 0.417) allocation failure
      [1636:0x77a8000]    47599 ms: Scavenge (reduce) 215.0 (223.3) -> 214.8 (223.5) MB, 33.7 / 0.0 ms  (average mu = 0.616, current mu = 0.417) allocation failure
      
      
      <--- JS stacktrace --->
      
      /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
      npm ERR! code ELIFECYCLE
      npm ERR! errno 1
      npm ERR! magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
      npm ERR! Exit status 1
      npm ERR!
      npm ERR! Failed at the magicmirror@2.15.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/2021-04-22T07_36_42_804Z-debug.log
      

      And in the given log I find this

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

      I did reinstall of npm in MM dir but always end up here.
      Does anybody see the problem?
      How can I solve this?
      Any help is welcome.

      Second part:
      What’s the problem with getting data from git?
      There is no blocking firewall rule between.

      Regards

      S 1 Reply Last reply Reply Quote 0
      • S Offline
        sdetweil @wmx
        last edited by

        @wmx how old is your sd card? and how big?

        the sd card limited lifetime is because the technology used is write once… so when u write again, different unused bits have to be used, over and over… the filesystem however does not KNOW that some bits will not take another write… so things get weird… these DS card are great for low write environments, like cameras and music players, where its write once and read a lot of times…
        but they fail in computer environments with logs and paging and all other write behavior…
        I have had 10 fail in the last 3 years…

        I now boot from sd, run from ssd (which has the SAME problem, but lots more bits available)

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        W 1 Reply Last reply Reply Quote 0
        • W Offline
          wmx @sdetweil
          last edited by

          @sdetweil

          The sd card is about one year old and half a year in use in the raspberry pi. It is a 16GB card.
          So you think I need to replace it? I have to do a complete new install?

          S 1 Reply Last reply Reply Quote 0
          • S Offline
            sdetweil @wmx
            last edited by

            @wmx u might be able to copy your config file and the modules folder.

            once the card is full, all the bits written, it is dead. no repair.

            weird things starting to happen is an indicator.

            weekly updates is a space consumer.

            Sam

            How to add modules

            learning how to use browser developers window for css changes

            W 1 Reply Last reply Reply Quote 0
            • W Offline
              wmx @sdetweil
              last edited by wmx

              @sdetweil
              I do NOT think the sd card is the reason here. I tried the following.
              Took a completely new second 32GB card, on which I installed MM 2.13.0 in december 2020. This card did only run for some hours in december. Pi came up and MM runs manually started with

              DISPLAY=:0 npm start
              

              for about half an hour.
              Then I decided to update MM (this was the fault here… :-( )
              After Upgrading MM to 2.15.0 (and updating all modules) the same problem occurs with this card!

              pi@mirror:~/MagicMirror $ DISPLAY=:0 npm start
              
              > magicmirror@2.15.0 start /home/pi/MagicMirror
              > DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js
              
              [23.04.2021 00:04.37.808] [LOG]   Starting MagicMirror: v2.15.0
              [23.04.2021 00:04.37.827] [LOG]   Loading config ...
              [23.04.2021 00:04.46.211] [LOG]   Starting node helper for: MMM-Remote-Control
              [23.04.2021 00:04.46.259] [LOG]   MMM-MQTT: Starting node helper
              [23.04.2021 00:04.46.264] [LOG]   Starting node_helper for module: MyCovid19
              [23.04.2021 00:05.18.598] [LOG]   MMM-MQTT: Starting client for:  {
              *** skipped same lines here ***
              }
              [23.04.2021 00:05.18.626] [LOG]   MMM-MQTT: Connecting to mqtt://moon.fritz.box:1883
              [23.04.2021 00:05.22.193] [LOG]   MMM-MQTT connected to mqtt://moon.fritz.box:1883
              [23.04.2021 00:05.22.202] [LOG]   MMM-MQTT: subscribing to sensor/wemos-schuppen-temp
              [23.04.2021 00:05.22.563] [ERROR] Failed to fetch git data for MyCovid19: Error: block timeout reached
              [23.04.2021 00:05.23.732] [ERROR] Failed to fetch git data for MMM-homeassistant-sensors: Error: block timeout reached
              [23.04.2021 00:05.25.023] [ERROR] Failed to fetch git data for MMM-MQTT: Error: block timeout reached
              [23.04.2021 00:05.26.530] [ERROR] Failed to fetch git data for MMM-PIR-Sensor: Error: block timeout reached
              [23.04.2021 00:05.34.347] [ERROR] Failed to fetch git data for MMM-Remote-Control: Error: block timeout reached
              [23.04.2021 00:05.35.557] [ERROR] Failed to fetch git data for default: Error: block timeout reached
              
              <--- Last few GCs --->
              
              [7523:0x77c8000]   113993 ms: Scavenge 210.7 (221.1) -> 210.2 (221.6) MB, 29.0 / 0.0 ms  (average mu = 0.795, current mu = 0.754) task
              [7523:0x77c8000]   114350 ms: Scavenge (reduce) 211.9 (221.9) -> 211.3 (220.1) MB, 103.9 / 0.0 ms  (average mu = 0.795, current mu = 0.754) allocation failure
              [7523:0x77c8000]   114759 ms: Scavenge (reduce) 212.8 (220.6) -> 212.3 (220.9) MB, 134.6 / 0.0 ms  (average mu = 0.795, current mu = 0.754) allocation failure
              
              
              <--- JS stacktrace --->
              
              /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV
              npm ERR! code ELIFECYCLE
              npm ERR! errno 1
              npm ERR! magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
              npm ERR! Exit status 1
              npm ERR!
              npm ERR! Failed at the magicmirror@2.15.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/2021-04-22T22_06_32_848Z-debug.log
              
              

              and the log

              pi@mirror:~/MagicMirror $ cat /home/pi/.npm/_logs/2021-04-22T22_06_32_848Z-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@6.14.8
              3 info using node@v10.23.0
              4 verbose run-script [ 'prestart', 'start', 'poststart' ]
              5 info lifecycle magicmirror@2.15.0~prestart: magicmirror@2.15.0
              6 info lifecycle magicmirror@2.15.0~start: magicmirror@2.15.0
              7 verbose lifecycle magicmirror@2.15.0~start: unsafe-perm in lifecycle true
              8 verbose lifecycle magicmirror@2.15.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.15.0~start: CWD: /home/pi/MagicMirror
              10 silly lifecycle magicmirror@2.15.0~start: Args: [ '-c',
              10 silly lifecycle   'DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js' ]
              11 silly lifecycle magicmirror@2.15.0~start: Returned: code: 1  signal: null
              12 info lifecycle magicmirror@2.15.0~start: Failed to exec start script
              13 verbose stack Error: magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
              13 verbose stack Exit status 1
              13 verbose stack     at EventEmitter.<anonymous> (/usr/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.<anonymous> (/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.15.0
              15 verbose cwd /home/pi/MagicMirror
              16 verbose Linux 5.4.79-v7+
              17 verbose argv "/usr/bin/node" "/usr/bin/npm" "start"
              18 verbose node v10.23.0
              19 verbose npm  v6.14.8
              20 error code ELIFECYCLE
              21 error errno 1
              22 error magicmirror@2.15.0 start: `DISPLAY="${DISPLAY:=:0}" ./node_modules/.bin/electron js/electron.js`
              22 error Exit status 1
              23 error Failed at the magicmirror@2.15.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 ]
              
              

              Sorry, but this is no accident.

              Is there a way to go back to MM 2.13.0?

              S 1 Reply Last reply Reply Quote 0
              • S Offline
                sdetweil @wmx
                last edited by

                @wmx did u use my upgrade script?

                see

                https://github.com/sdetweil/MagicMirror_scripts

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                W 1 Reply Last reply Reply Quote 0
                • W Offline
                  wmx @sdetweil
                  last edited by

                  @sdetweil
                  No, this time i did it manually. I used it for upgrading my first card (from first post).

                  Can I use it now for a second time now?

                  S 1 Reply Last reply Reply Quote 0
                  • S Offline
                    sdetweil @wmx
                    last edited by

                    @wmx u can try, use the force parm instead of apply

                    Sam

                    How to add modules

                    learning how to use browser developers window for css changes

                    W 1 Reply Last reply Reply Quote 0
                    • W Offline
                      wmx @sdetweil
                      last edited by

                      @sdetweil reran script with force, but still same issue

                      S 1 Reply Last reply Reply Quote 0
                      • S Offline
                        sdetweil @wmx
                        last edited by

                        @wmx weird.

                        if u install 2.15 by itself does it run?
                        then copy your module over and config.js

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

                        W 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 1 / 2
                        • First post
                          Last post
                        Enjoying MagicMirror? Please consider a donation!
                        MagicMirror created by Michael Teeuw.
                        Forum managed by Sam, technical setup by Karsten.
                        This forum is using NodeBB as its core | Contributors
                        Contact | Privacy Policy