Unable to install Node 18.12.1 (LTS)

ppo

I decompressed node-v18.12.1-linux-x64.tar.xz and when executing ./bin/node…

./bin/node: /lib64/libm.so.6: version `GLIBC_2.27' not found (required by ./bin/node)
./bin/node: /lib64/libc.so.6: version `GLIBC_2.25' not found (required by ./bin/node)
./bin/node: /lib64/libc.so.6: version `GLIBC_2.28' not found (required by ./bin/node)
./bin/node: /lib64/libstdc++.so.6: version `CXXABI_1.3.9' not found (required by ./bin/node)
./bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./bin/node)
./bin/node: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by ./bin/node)

Installing on opal6 following @sean's instructions
The version 17.9.1 works fine.

sean

ppo the latest Node binary is not compatible with CentOS7 so you won't be able to use it on Opalstack at this time.

We've made a lot of progress behind the scenes towards getting the platform running on a newer OS and we hope to to have some good news about that in the months ahead!

ppo

Thanks sean. It's not a problem for me, the v17 is fine. It was just to let you know.
And Merry Christmas 😉

kptac

sean Hi Sean, I'm having a roadblock with project using Directus, and with their latest release it requires Note 18. For the time being it's not an urgent issue to upgrade (although I'd like everything to be up-to-date). I will appreciate if we can find a solution to this.

Previously argon2 builds was also an issue. A lot of new projects are going to start moving towards 18 LTS now.

Awaiting good news soon.

Thanks and keep up the good work.

sean

kptac you can build your own Node v18 from source with the following commands:

cd ~/apps/name_of_app
mv node node.old
mkdir node
wget https://nodejs.org/dist/v18.12.1/node-v18.12.1.tar.gz
tar zxf node-v18.12.1.tar.gz
cd node-v18.12.1
scl enable devtoolset-11 -- ./configure --prefix=$HOME/apps/name_of_app/node
scl enable devtoolset-11 -- make -j2
scl enable devtoolset-11 -- make install

This will take a very long time to build, particularly the first make command may take an hour or longer. You can reduce the time by increasing the value of the -j parameter, like -j4, but this will use more server resources.

Once it is done the new node will be installed in ~/apps/name_of_app/node.

kptac

sean Hi Sean

Dont see devtoolset-11

$ scl -l 
devtoolset-10
devtoolset-7
devtoolset-9
llvm-toolset-7
php56
php74
php80
php81
php82
rh-redis5
rh-ruby30
sclo-git212

Tried with others, and got errors

$ scl enable devtoolset-10 ./configure --prefx=$PWD/node
Unable to open /etc/scl/conf/./configure!

sean

kptac devtoolset-11 was not installed on your VPS, so I've just installed it.

Also, I've adjusted the syntax of the scl commands in my example above to include -- between the scl package and the command being run. Please use the updated commands.

kptac

sean

The final step, scl enable devtoolset-11 -- make install gives following error:

......
rm 7555b2416445b472167f2771d3f7abdb2ca0ebba.intermediate bf0956357fb95d1143bd3d8eab41c64ed8517efb.intermediate b38d4a8019d825d963ba26f8f42aa941ea2c5565.intermediate 5968ba6a9b1488d701a0356f3c0973e83209c09e.intermediate
if [ ! -r node ] || [ ! -L node ]; then \
  ln -fs out/Release/node node; fi
/usr/local/bin/python3.11 tools/install.py install '' '/home/kptac/apps/kptac-directus-app/node-v18.14.1/node'
installing /home/kptac/apps/kptac-directus-app/node-v18.14.1/node/bin/node
Traceback (most recent call last):
  File "/home/kptac/apps/kptac-directus-app/node-v18.14.1/tools/install.py", line 351, in <module>
    run(sys.argv[:])
  File "/home/kptac/apps/kptac-directus-app/node-v18.14.1/tools/install.py", line 342, in run
    files(install)
  File "/home/kptac/apps/kptac-directus-app/node-v18.14.1/tools/install.py", line 150, in files
    action([output_prefix + output_file], 'bin/' + output_file)
  File "/home/kptac/apps/kptac-directus-app/node-v18.14.1/tools/install.py", line 77, in install
    try_copy(path, dst)
  File "/home/kptac/apps/kptac-directus-app/node-v18.14.1/tools/install.py", line 65, in try_copy
    try_mkdir_r(os.path.dirname(target_path))
  File "/home/kptac/apps/kptac-directus-app/node-v18.14.1/tools/install.py", line 40, in try_mkdir_r
    os.makedirs(path)
  File "<frozen os>", line 225, in makedirs
NotADirectoryError: [Errno 20] Not a directory: '/home/kptac/apps/kptac-directus-app/node-v18.14.1/node/bin'
make: *** [Makefile:190: install] Error 1

sean

kptac please try like this instead:

cd ~/apps/name_of_app
mv node node.old
mkdir node
wget https://nodejs.org/dist/v18.12.1/node-v18.12.1.tar.gz
tar zxf node-v18.12.1.tar.gz
cd node-v18.12.1
scl enable devtoolset-11 -- ./configure --prefix=$HOME/apps/name_of_app/node
scl enable devtoolset-11 -- make -j2
scl enable devtoolset-11 -- make install

db122

sean Is it really --prefx and not --prefix? That would be wild. I've got no horse in this race, just curious! 🙂

db122

sean Using this procedure I was able to build a Node 18.15.0 binary. Unfortunately, the binary fails many unit tests and when I try to use it with my own code, it fails when trying to make network connections to my local mongodb instance (ECONNREFUSED) and presumably other things. Some of the failed tests refer to binding to unprivileged ports. I wonder if there's either a) some dev dependency I'm missing or b) just a general incompatibility with the CentOS version in use, which is why they stopped providing their own binaries. I'd appreciate any advice!

FWIW, I'm seeing some of my regular dependencies (semantic release plugins for a start) start to creep up with Node 18 minimum requirements.

sean

db122 my bad, typo corrected.

db122

db122 I'm currently building a v16 binary to see if it's a problem with my build environment.

sean

db122 That doesn't sound like OS incompatibility to me. If you'd like us to look into it then please send your build and test logs to support (or tell us where we can find them on the server) and we'll go from there.

db122

Putting a bit of resolution to my issue, in case anyone else experiences it or something related. Node 18 introduced new ipv6 hostname lookup behavior and my local mongo/redis servers weren't configured to bind to the ipv6 interfaces so the connections failed.

TL;DR: My Node binary build was fine, it was just my setup that needed to be fixed. Thanks to Sean for pointing me in the right direction! As always, Opalstack support is A++.

twiago

hey Sean,

I have tried installing Node v18 using the method mentioned above, however i get a "Unable to open /etc/scl/conf/devtoolset-11!" back

I dont see the devtoolset-11 under the scl -l

One more question: My goal is to have multiple Applications under the shell user, where all use the new Node version, do i have to install the new node under each application or is there a way to that only once?

Thanks

sean

twiago I dont see the devtoolset-11 under the scl -l

Sorry about that, devtoolset-11 wasn't installed on your server. I've corrected that so you can now proceed with the procedure.

twiago One more question: My goal is to have multiple Applications under the shell user, where all use the new Node version, do i have to install the new node under each application or is there a way to that only once?

You could install node.js higher up in the home directory, like in ~/opt/node, and then edit your apps' start scripts to use that install instead of the one in the app directory.

twiago

Thanks, i have successfully installed the newest version and changed the starting script on my application, however how can i use the newest npm that has been installed with the node?

sean

twiago if you used ~/opt/node as the installation prefix then the following command should make the included npm the default:

export PATH=$HOME/opt/node/bin:$PATH

twiago

Worked like a charm 🙂 Thank you