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.

    Upgrade errors?

    Scheduled Pinned Locked Moved Solved Troubleshooting
    35 Posts 9 Posters 9.7k Views 10 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.
    • kaiK Offline
      kai @BKeyport
      last edited by

      @BKeyport said in Upgrade errors?:

      @sdetweil turns out there was an update to MMM-Wallpaper that missed due to all the bugs in upgrading. šŸ˜‰

      …just in case this might be interesting for anyone: I had the same problems on my Raspberry Pi 4 Model B (Rev 1.2) with buster (armv71).

      • node 20 gave me the `GLIBCXX_3.4.26’ not found (required by node) error
      • I had the ā€œfailed to load swrast driverā€

      I checked my modules, and the solution for my MM was (thanks to @sdetweil and @BKeyport here):

      • installing node 18 (I did it manually like mentioned here)
      • removing ā€œDWD Warn Weatherā€ (which caused the swrast error) from config.js

      Now MagicMirror v2.25.0 is up and running! :beaming_face_with_smiling_eyes:

      Thank you for all your effort and your tireless support!
      May the code be with you.
      -kai

      1 Reply Last reply Reply Quote 0
      • J Offline
        JohnGalt
        last edited by

        @sdetweil - I’m not sure this the correct topic for my error, so if not we can move it - but I am having the issues described above, but on an initial install [as opposed to an upgrade]. This is on a freshly created VirtualBox VM using the current RaspbianOS version of Debian, using Sam’s install script.

        After a long series of lines indicating it was setting up various node packages, the install.log file ends with a message that node failed to install:

        added 1 package, and audited 2 packages in 1s
        
        found 0 vulnerabilities
        installing on bullseye
        installing correct version of node and npm, please wait
          installing : node-v20.8.0
               mkdir : /usr/local/n/versions/node/20.8.0
               fetch : https://nodejs.org/dist/v20.8.0/node-v20.8.0-linux-x64.tar.xz
             copying : node/20.8.0
           installed :  (with npm )
        
        Note: the node command changed location and the old location may be remembered in your current shell.
                 old : /usr/bin/node
                 new : /usr/local/bin/node
        If "node --version" shows the old version then start a new shell, or reset the location hash with:
        hash -r  (for bash, zsh, ash, dash, and ksh)
        rehash   (for csh and tcsh)
        node failed to install, exiting
        

        Thoughts??

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

          @JohnGalt can u send me the install.log file…

          I have a vm of raspi x86 as well…

          this same userid at gmail… thx

          Sam

          How to add modules

          learning how to use browser developers window for css changes

          1 Reply Last reply Reply Quote 0
          • J Offline
            JohnGalt
            last edited by

            @sdetweil - Thanks, the log file is on its way to you…

            1 Reply Last reply Reply Quote 1
            • J Offline
              JohnGalt
              last edited by

              @sdetweil - Thanks for the help here and offline. My problem is solved, and for the sake of others following is the resolution.

              Problem: MagicMirror install script outputs node.js errors on new RaspbianOS install running under VirtualBox.

              Diagnosis [by sdetweil]: ā€œso, the problem is that the intel raspian is a hybrid, x86_64 kernel with a i386 user runtime.
              and they stopped making a nodejs for i386 after node 12ā€

              Solution: Rebuilt the virtual machine using Ubuntu instead of RaspbianOS. [I’m sure any Debian or other Linux distribution would work just fine…]

              Thanks again - I can now use this as a dev machine and spare myself the risks associated with fiddling with the production machine!

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