`GLIBCXX_3.4.26' not found (required by node)

matt216

@sdetweil Your upgrade-script.sh yes, with force.

pi@magicmirror:~ $ lsb_release -a
No LSB modules are available.
Distributor ID: Raspbian
Description: Raspbian GNU/Linux 10 (buster)
Release: 10
Codename: buster

pi@magicmirror:~ $ uname -a
Linux magicmirror 5.10.103-v7+ #1529 SMP Tue Mar 8 12:21:37 GMT 2022 armv7l GNU/Linux

No install.log in my home directory, sorry…

sdetweil

@matt216 ok, can you copy/paste, and execute this

bash -c “$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/node20_install.sh)”

matt216

@sdetweil Initially no such file or directory response so I removed the two sudo rm -r lines and ran again. Looked to complete successfully.
Rebooted.
Same state - mirror doesn’t start, pm2 commands not found.

matt216

@sdetweil I need to pick the boy up from nursery now. Will return tomorrow. Thanks loads for the support.
Matt

matt216

Going for a full fresh install. Did some googling on GLIBCXX and it looks terrifying. Seems particular to raspberry pis. It seems quite fundamental to the OS and people don’t recommend tinkering with it at all. Only advice out there seems to be “rebuild”.

sdetweil

@matt216 yes, it’s a tough problem .

backup your mm config
https://github.com/sdetweil/MagicMirror-backup-restore

matt216

@sdetweil config.js is backed-up regularly to an NFS mount from another machine. Will be a good recovery test :) Would be handy to figure out a way to restore all the modules.

Thanks for your assistance

sdetweil

@matt216 try my backup it saves the config the custom CSS and the URLs on GitHub of all of the modules you have installed

then on restore it uses the URLs to download the modules

check it out You can run them from GitHub without downloading onto your machine

puts everything into a little folder MM _ backup just three files

uses git tags to version the backup, and can push the GitHub if you want when you back up

and will save the extra files found in any module folder like Google or Spotify token files etc

matt216

@sdetweil beautiful!

nnvv3344

I was having this problem and could not figure it out. Here is the fix that worked right away for me…

I uninstalled the version of Node that I had (which was 20) and I went back to install node js 18. It works after doing this