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

[matt216]

Hi all.

Just updated my MM and saw that I was running on an ancient version of node/npm. Upgraded those and I’m currently seeing the following error:

node: /lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by node)

Running on raspberry pi, raspbian v10 buster.
Latest version of MM.
Node v 18.18.0
npm v9.8.1

Zero results when I search for GLIBCXX on the forum :worried_face: Any tips?

Thanks

[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

[sdetweil]

@matt216 please use my upgrade script, with force instead of apply

https://github.com/sdetweil/MagicMirror_scripts

I added support for the latest version and the new node

[matt216]

@sdetweil said in `GLIBCXX_3.4.26' not found (required by node):

with force instead of apply

Thanks. What do you mean with force, instead of apply?

[matt216]

@sdetweil Thanks. What do you mean with force instead of apply?

[sdetweil]

@matt216

the upgrade command is

bash -c  "$(curl -sL https://raw.githubusercontent.com/sdetweil/MagicMirror_scripts/master/upgrade-script.sh)" apply

change the word apply to force

[matt216]

@sdetweil Thank you. It currently can’t upgrade as I have 2 electron node processes running. killall node and the processes start again with a different PID. Can’t seem to stop electron!

[sdetweil]

@matt216 pm2 stop all

pm2’s JOB is to KEEP the monitored apps running… you kill it, and then pm2 restarts…

pm2 status

will show you all the things being managed

[matt216]

@sdetweil Ah but any pm2 command gives me the error `GLIBCXX_3.4.26’ not found I originally mentioned.

[sdetweil]

@matt216 reboot… pm2 will fail to launch then upgrade again …

then pm2 should work

[matt216]

@sdetweil Unfortunately not. After reboot 2 electron processes preventing the upgrade-script from completing and pm2 commands fail without GLIBCXX version.

Appreciate the support here.

[sdetweil]

@matt216 ok, run this command string all one copy/paste and enter

sudo apt-get purge nodejs -y &&\
sudo rm -r /etc/apt/sources.list.d/nodesource.list &&\
sudo rm -r /etc/apt/keyrings/nodesource.gpg

[matt216]

@sdetweil Progress, thank you. After purging and removing those files, I ran the install script. It completes, but during the npm install step I notice:

E: Unable to correct problems, you have held broken packages.
node: /lib/arm-linux-gnueabihf/libstdc++.so.6: version `GLIBCXX_3.4.26' not found (required by node)

The script completes (but doesn’t give a npm version number, interestingly). I rebooted the pi and the mirror doesn’t start and pm2 command is not found.

[sdetweil]

@matt216 can u show me the output of

lsb_release -a
uname -a

and you ran MY install script, correct?

send me ~/install.log
my same userid at gmail

[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