Upgrade errors?

[BerkSmash1984]

@sdetweil I tried to run the upgrade script on my RPI 4B running Bullseye and it hosed my MM. During the install, I see this:

It appears to have removed/partially remove npm altogether:

Any thoughts?

[sdetweil]

@BKeyport said in Upgrade errors?:

Cannot find module ‘fetch’

we removed this in 2.25

see
https://forum.magicmirror.builders/topic/15778/fix-for-black-screen-in-2-16-and-later

or, you can comment out the require in the module node_helper.js

as fetch is built in in 2.18 and up

[sdetweil]

@BerkSmash1984 I see 64bit… let me look

seems the process is different there… darn

[mumblebaj]

@sdetweil Can you help me fix my WSL? I seem to be having and issue with electron and a missing lib. I have emailed you the install.log as well.

[sdetweil]

@mumblebaj maybe
https://github.com/snobu/destreamer/issues/216

[mumblebaj]

@sdetweil Thanks Sam. A bunch of missing libs but all working again.

Now to add my modules I had running on the dev machine. The joy. :-)

[sdetweil]

@mumblebaj always backup

I have one that makes a small image
https://github.com/sdetweil/MagicMirror-backup-restore

[mumblebaj]

@sdetweil I use your backup scripts on my main mirror. My dev machine I did not backup. Will teach me for next time. :crying_face:

[BKeyport]

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

[sdetweil]

@BKeyport yes I saw that too

[sdetweil]

@mumblebaj My scripts don’t depend on node or anything else they’re all bash scripts. So if you haven’t deleted anything you can still run the back up there and be able to restore it later

[kai]

@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

[JohnGalt]

@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??

[sdetweil]

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

I have a vm of raspi x86 as well…

this same userid at gmail… thx

[JohnGalt]

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

[JohnGalt]

@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!