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.

    Mirror not starting after update

    Scheduled Pinned Locked Moved Solved Troubleshooting
    33 Posts 4 Posters 4.4k Views 4 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.
    • X Offline
      xIExodusIx @sdetweil
      last edited by

      @sdetweil

      Raspberry Pi 4
      OS = bookworm 64bit

      S 1 Reply Last reply Reply Quote 0
      • S Do not disturb
        sdetweil @xIExodusIx
        last edited by sdetweil

        @xIExodusIx did you use my upgrade script?

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        1 Reply Last reply Reply Quote 0
        • S Do not disturb
          sdetweil @chrisfr1976
          last edited by

          @chrisfr1976 can you show me the output of thew npm run install-mm

          do it this way (from the MM folder of course)

          cd ~/MagicMirror
          npm run install-mm >somefile.txt 2>&1
          

          then when it finishes all the output is in somefile.txt

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          X 1 Reply Last reply Reply Quote 0
          • X Offline
            xIExodusIx @sdetweil
            last edited by

            @sdetweil
            lsb_release -a shows:
            No LSB modules are available.
            Distributor ID: Debian
            Description: Debian GNU/Linux 12 (bookworm)
            Release: 12
            Codename: bookworm

            uname -a shows:
            Linux MirrorPi 6.6.51+rpt-rpi-v8 #1 SMP PREEMPT Debian 1:6.6.51-1+rpt2 (2024-10-01) aarch64 GNU/Linux

            yes I used your upgrade-script with apply and also with force.

            pm2 start MagicMirror will start the MM but it won’t show up!

            npm start results in following errors:
            [41163:1002/155017.678545:ERROR:ozone_platform_x11.cc(245)] Missing X server or $DISPLAY
            [41163:1002/155017.688550:ERROR:env.cc(258)] The platform failed to initialize. Exiting.
            /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

            S 2 Replies Last reply Reply Quote 0
            • S Do not disturb
              sdetweil @xIExodusIx
              last edited by

              @xIExodusIx before this morning, my upgrade script had a bug

              do

              cd ~/MagicMirror
              ls installers
              

              that should fail (not found)
              then do

              mkdir installers
              curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/mm.sh >installers/mm.sh
              chmod +x installers/mm.sh
              

              Sam

              How to add modules

              learning how to use browser developers window for css changes

              X 1 Reply Last reply Reply Quote 0
              • S Do not disturb
                sdetweil @xIExodusIx
                last edited by

                @xIExodusIx also, if you do

                cd ~/MagicMirror
                npm start 
                

                does MM come up?

                Sam

                How to add modules

                learning how to use browser developers window for css changes

                X 1 Reply Last reply Reply Quote 0
                • X Offline
                  xIExodusIx @sdetweil
                  last edited by

                  @sdetweil

                  magicmirror@2.29.0 install-mm
                  npm install --no-audit --no-fund --no-update-notifier --only=prod --omit=dev

                  magicmirror@2.29.0 postinstall
                  npm run install-vendor && npm run install-fonts && echo "MagicMirror² installation finished successfully!
                  "

                  magicmirror@2.29.0 install-vendor
                  echo "Installing vendor files …
                  " && cd vendor && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

                  Installing vendor files …

                  up to date in 2s

                  magicmirror@2.29.0 install-fonts
                  echo "Installing fonts …
                  " && cd fonts && npm install --loglevel=error --no-audit --no-fund --no-update-notifier

                  Installing fonts …

                  up to date in 1s
                  MagicMirror² installation finished successfully!

                  magicmirror@2.29.0 prepare
                  [ -f node_modules/.bin/husky ] && husky || echo no husky installed.

                  no husky installed.

                  up to date in 14s

                  after that, nodejs is still the same: 18.19.0

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

                    @sdetweil
                    the installers folder is still there.
                    should I delete it?
                    or should run the script without delete the installers folder?

                    1 Reply Last reply Reply Quote 0
                    • X Offline
                      xIExodusIx @sdetweil
                      last edited by

                      @sdetweil
                      if I do npm start

                      I get this error at the end:
                      .
                      .
                      .
                      [2024-10-02 16:13:22.616] [LOG] All module helpers loaded.
                      [2024-10-02 16:13:22.627] [LOG] Starting server on port 8181 …
                      [63161:1002/161323.449087:ERROR:ozone_platform_x11.cc(245)] Missing X server or $DISPLAY
                      [63161:1002/161323.449298:ERROR:env.cc(258)] The platform failed to initialize. Exiting.
                      /home/pi/MagicMirror/node_modules/electron/dist/electron exited with signal SIGSEGV

                      1 Reply Last reply Reply Quote 0
                      • S Do not disturb
                        sdetweil @xIExodusIx
                        last edited by

                        @xIExodusIx said in Mirror not starting after update:

                        nodejs is still the same: 18.19.0

                        this version like last requires node 20 or 22 (not 21)
                        this is the ‘problem’

                        magicMirror will not upgrade nodejs… only my upgrade script will do that
                        npm run install-mm should have failed as there is a test for the correct node version(s)…

                        can you show me the part of
                        ~/MagicMirror/installers/upgrade.log
                        from one of your upgrade runs?
                        or open an issue on my scripts repo and attached the log there
                        no personal info is present in the log

                        Sam

                        How to add modules

                        learning how to use browser developers window for css changes

                        X 1 Reply Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 2 / 4
                        • 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