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.

    After update 2.23.0 crash

    Scheduled Pinned Locked Moved Bug Hunt
    56 Posts 9 Posters 21.6k Views 8 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.
    • J Offline
      JoeFranz
      last edited by

      I ran “electron-rebuild”, now it works again :-)

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

        @JoeFranz on what module?

        Sam

        How to add modules

        learning how to use browser developers window for css changes

        J W 2 Replies Last reply Reply Quote 0
        • J Offline
          JoeFranz @sdetweil
          last edited by

          @sdetweil MMM-PIR-Sensor

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

            @sdetweil By chance, do you know of a command I can run to kill any running Node processes? I’m trying to run your upgrade script and its unable to upgrade Node because a process is already running. Googling gives me code to use within an application but that doesn’t seem like it’ll work from the CLI.

            doing test run = false
            update log will be in /home/pi/MagicMirror/installers/upgrade.log
            Check current Node installation ...
            Node currently installed. Checking version number.
            Minimum Node version: v16.13.1
            Installed Node version: v10.24.1
            Node should be upgraded.
            A Node process is currently running. Can't upgrade.
            Please quit all Node processes and restart the update.
            running process(s) are
            pi 881 879 0 09:05 ? 00:00:00 node ./node_modules/.bin/electron js/electron.js
            
            S 1 Reply Last reply Reply Quote 0
            • mumblebajM Offline
              mumblebaj Module Developer @JerryP
              last edited by

              @JerryP Always use Sam’s update script. I used it last night and updated from 2.21.0 to 2.23.0 no issues. Often modules with a package.json requires an npm install in that folder and the upgrade script takes care of all of that.

              Check out my modules at: https://github.com/mumblebaj?tab=repositories
              Check my blog-post: https://mumblebaj.xyz/

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

                @Wenike do this

                from a terminal window

                ps -ef | grep node
                

                this will show you the node processes running and parms to what they are running (file path)

                if all looks understandable and u can’t terminate them thru app shutdown (pm2 stop all will stop all.managed apps, mm included), do

                ps -ef | grep node | awk '{ print $2 }' | xargs kill -9
                

                this will hard kill all the node processes

                Sam

                How to add modules

                learning how to use browser developers window for css changes

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

                  @JoeFranz

                  the script does a new npm install in modules that have a package.json

                  but I know the post install process is wrong for this module

                  my fork fixes that
                  https://github.com/sdetweil/MMM-PIR-Sensor

                  Sam

                  How to add modules

                  learning how to use browser developers window for css changes

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

                    @sdetweil Perfect, fixed it. Thanks!

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

                      @JerryP said in After update 2.23.0 crash:

                      sudo git pull

                      just one more thing

                      NEVER use sudo with MM no need for it.
                      all it does is lead to trouble

                      Sam

                      How to add modules

                      learning how to use browser developers window for css changes

                      1 Reply Last reply Reply Quote 0
                      • H Offline
                        hrjmsh @sdetweil
                        last edited by hrjmsh

                        @sdetweil Thank you very much. Had the same error (cannot find module envsub) on updating the MagicMirror to the new version and this step (rm -rf node_modules and then npm install again) solved the issue for me.

                        S T 2 Replies Last reply Reply Quote 0
                        • 1
                        • 2
                        • 3
                        • 4
                        • 5
                        • 6
                        • 1 / 6
                        • 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