Repository navigation
The latest cli (1.32.0-245) cause "ERROR SHARED stderr {"data": "Error: /lib64/libstdc++.so.64: version GLIBCXX_3.4.21 not found".... #239
Description
Description
Hi, the above problem raised when "Starting shared process[x/5]", after I update my code-server cli from 1.31.1-100 to 1.32.0-245. It works properly when using the former version. I am wondering whether the latest cli depends on different C++ library from the former one?
PS: The message is:
INFO Starting shared process [1/5]...
ERROR SHARED stderr {"data":"Error: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /path/to/my/home/.local/share/code-server/dependencies/spdlog.node)\n...
Activity
neighthan commentedon Mar 14, 2019
I was getting a similar, though not exactly the same, error before. What OS are you on? I got the error on Ubuntu 14.04 but not when I used 16.04 instead. The specific error I was getting is described in this SO question.
mbeattie commentedon Mar 15, 2019
This error is because your os's version of libstdc++ doesnt contain the latest symbols. You'll need to upgrade the that package (or perhaps the OS) to fix it. You might be able to get away with building it yourself, but I have been having trouble getting that to work also.
absudabsu commentedon Mar 15, 2019
I'm on Centos 7, just installed/upgraded to latest libstdc++ offered, same issue.
and before this:
jgbradley1 commentedon Mar 15, 2019
I encountered this same error when trying to build code-server in a CentOS docker image here.
Michaelvll commentedon Mar 15, 2019
I don't
sudoprivilege on my server (actually a cluster) and cannot update the libstdc++. I am wondering if it is possible to release a pre-build that compiled using library with lower version. By the way, the system on my server is CentOS Linux release 7.3.jwshields commentedon Mar 15, 2019
Neither my Debian Jessie machine, nor my CentOS 7.5 machine are able to run the server. I've updated with yum/apt and installed a number of the devtools (yum) and various glibc/libstdc/gcc packages to no avail.
taime commentedon Mar 16, 2019
The same problem Ubuntu "18.04.2 LTS (Bionic Beaver)"
(it's google cloud Ubuntu mini )
duman commentedon Mar 17, 2019
Same problem on CentOS Linux release 7.6.1810 (Core)
sinni800 commentedon Mar 18, 2019
For me, I have that problem even when building on centos 7. I would have assumed that building there would build with the present glibc/glibcxx in mind. But apparently it's pulling binary dependencies in that would ruin this.
krazyito65 commentedon Mar 18, 2019
Make sure you're updated, i was able to run it on CentOS 7 after running this:
yum install -y git bzip2 gcc gcc-c++ make libX11-devel.x86_64 libxkbfile-devel.x86_64 libsecret-devel.x86_64duman commentedon Mar 18, 2019
What to do now? :)
krazyito65 commentedon Mar 18, 2019
Cry? /s
not sure.. I'll poke around again.. I know I had this exact issue but I ended up fixing it at some point..
$ npm --version
6.9.0
$ node --version
v8.15.0
$ yarn --version
1.13.0
maybe npm update?
npm install -g npmkrazyito65 commentedon Mar 18, 2019
OH i remember now... I have
Maybe try doing
unset $LD_LIBRARY_PATH? Or if you can find the right lib you can point it to it./usr/lib/oracle/12.2/client64/lib--- I have this becasue I use it for my SQLplus installationsinni800 commentedon Mar 18, 2019
I found out that this problem is (for me) caused by the "spdlog.node" binary. I ended up rebuilding that binary from the repo at https://github.com/Microsoft/node-spdlog... And while I have no idea about how to look into the build process of this project, I presume it doesnt build that binary itself but rather downloads it as a dependency (I mean, my system doesnt HAVE a 3.4.21 GLIBCC header to build with, so this has to be the case).
Building node-spdlog does NOT take long at all (a few seconds) so I would suggest that this project should build it itself (it also builds a lot of stuff with gcc compiler in general, so adding this would make the builds more OS independent)
EDIT: At the same time, I somehow ruined everything and through cleanups and all, it wouldn't build the cli-linux-x64 binary anymore (which is code-server), but that's unrelated to this issue
17 remaining items
Blair2004 commentedon May 4, 2019
@EasySoftwarePoland indeed ! the reason why i'm interested with this is to use the physical resource for one of my servers.
crackerandres commentedon May 4, 2019
any update on this? same issue here. I tried the latest release but same errors. seems like the best option right now is to wait.
EasySoftwarePoland commentedon May 4, 2019
@crackerandres it is not the only issue on centos. We fixed this one but the terminal was not working, but it could be an other missing library. We finished with Debian, and everything works well.
crackerandres commentedon May 4, 2019
@EasySoftwarePoland ah gotcha! thanks for the heads up. I just went ahead and switched over and it works like a champ! Thank you again 👍
patrick-stickler-csc-fi commentedon May 20, 2019
Any resolution yet for this on Centos7?
ekanna commentedon May 20, 2019
Any update on this? Latest release also not working! But release notes mentions this issue!!
longv2go commentedon May 23, 2019
same issue!
NMSAzulX commentedon May 27, 2019
Still unable to work on CentOS 7.6.
tnkteja commentedon May 31, 2019
Yep.
JoeFirmament commentedon Jun 9, 2019
Same issue.
kiemrong08 commentedon Jun 28, 2019
I resolved this issue by install gcc-9.1.0 (
gcc-9.1.0.tar.gz) manually in CentOS 7.https://gcc.gnu.org/mirrors.htmlMy version:
code-server1.1156-vsc1.33.1-linux-x64Blair2004 commentedon Jun 28, 2019
I'm completely off here, Visual Studio Code's Remote Development extension does the job for me.
Good luck !
NMSAzulX commentedon Jun 28, 2019
@kiemrong08 Thanks. @Blair2004 Yes. Me too.
sr229 commentedon Sep 12, 2019
We're already building it against CentOS 7 so this should be a fixed now.