You need to install glibc alongside your current installation of glibc as you cannot update to glibc 2.14 directly in centos 6.x safely. Follow the steps below to install glibc 2.14:

1. mkdir ~/glibc214
2. cd ~/glibc214
3. wget http://ftp.gnu.org/gnu/glibc/glibc-2.14.tar.gz
4. tar zxvf glibc-2.14.tar.gz
5. cd glibc-2.14
6. mkdir build
7. cd build
8. ../configure --prefix=/opt/glibc-2.14
9. make -j4
10. sudo make install
11. export LD_LIBRARY_PATH=/opt/glibc-2.14/lib (for current login session) OR add LD_LIBRARY_PATH=/opt/glibc-2.14/lib in the /etc/environment and perform source /etc/environment(to add env variable permanently)

According to distrowatch, CentOS 6.10 shipped with GLIBC-2.12.

I used ldd --version

ldd is highly unreliable for anything (it will lie to you).

What matters is what version of /lib64/libc.so.6 you have. You can find out by running it, like so:

/lib64/libc.so.6

You don't have a high enough version of libc6, that is causing the error.

From How to fix “/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.14' not found”? – Super User:

That means the program was compiled against glibc version 2.14, and it requires that version to run, but your system has an older version installed. You'll need to either recompile the program against the version of glibc that's on your system, or install a newer version of glibc (the "libc6" package in Debian).

So, you just need to upgrade your libc6 package. All versions of Ubuntu have at least version 2.15 because it's a faily important package (reference).

To upgrade it, use these commands in a terminal:

sudo apt-get update
sudo apt-get install libc6

You cannot update glibc on Centos 6 safely. However you can install 2.14 alongside 2.12 easily, then use it to compile projects etc. Here is how:

mkdir ~/glibc_install; cd ~/glibc_install 

wget http://ftp.gnu.org/gnu/glibc/glibc-2.14.tar.gz

tar zxvf glibc-2.14.tar.gz

cd glibc-2.14

mkdir build

cd build

../configure --prefix=/opt/glibc-2.14

make -j4

sudo make install

export LD_LIBRARY_PATH="/opt/glibc-2.14/lib${LD_LIBRARY_PATH:+:$LD_LIBRARY_PATH}"

I've just spun up a C6 VM, installed the webtatic repo on it, and got the server package installed and running. I don't know how you got it to install on top of the existing mysqld, but at any rate, when I install it in place of the existing one, the glibc requirements are correct and are satisfied.

Why yours is asking for glibc 2.14, I can't understand. Maybe webtatic temporarily released one with wrong run-time links, then released a correct one over the top of it without bumping the version number. It's hard to say, but this is the sort of thing that sometimes happens when you decide to go off-piste and install things from strange repos.

If I were you, I'd make a copy of /var/lib/mysql, uninstall and reinstall the mysql55w packages (doing it cleanly this time!), then stop the freshly-installed mysqld, copying your /var/lib/mysql in place of any new one that might have appeared (and keeping any such new one to hand in case you need it), and trying to start the server up.

Failing that, get ready to restore your DB from backups.

That means the program was compiled against glibc version 2.14, and it requires that version to run, but your system has an older version installed. You'll need to either recompile the program against the version of glibc that's on your system, or install a newer version of glibc (the "libc6" package in Debian).

Debian has glibc 2.16 in the "experimental" repository, but recompiling the program is the safer option. Glibc is the library that everything depends on, so upgrading it can have far-reaching implications. Although there's probably nothing wrong with Debian's glibc 2.16 package, the fact that it's in the experimental repository means it hasn't received as much testing.

It is a real error, but a temporary one: it occurred because glibc-common was installed before glibc, so the updated C library itself wasn’t available yet when the updated build-locale-archive ran.

You could re-install glibc-common to re-run the post-installation setup:

rpm -Uvh glibc-common-2.15-60.el6.x86_64.rpm

(I haven’t checked whether that is necessary, but it won’t do any harm.)