[gmodserver] CentOS 6.5 version `GLIBC_2.15' not found

I just did a clean install with centos 6.5 64bit and got this:

[ FAIL ] Stopping gmod-server: gmod6465 is already stopped
[ OK ] Starting debug mode gmod-server: gmod6465
Auto detecting CPU
Using default binary: ./srcds_linux
Enabling debug mode
Server will auto-restart if there is a crash.
Failed to open dedicated_srv.so (/lib/libm.so.6: version `GLIBC_2.15' not found (required by bin/dedicated_srv.so))
cat: hlds.19093.pid: No such file or directory
email debug.log to linux@valvesoftware.com
Mon Jan 1 01:00:47 GMT 2007: Server restart in 10 seconds

Here they are saying Centos is terrible for gmod becauce GLIBC is terribly out of date.

http://steamcommunity.com/app/4000/discussions/1/46476690686730556/#p3

[Scarsz]

There's already a fix for GLIBC in the script. Either the script failed while installing that or you have an outdated script.

I used the script from these instructions: http://danielgibbs.co.uk/lgsm/gmodserver/

(http://danielgibbs.co.uk/dl/gmodserver)

Does the script need the users password to run properly ?
I didn't think it did so used a different one than in the instructions.

[Scarsz]

The script's probably broken, will know when I do a major test later today.

[dgibbs64]

Yeah this should work on its own. Will need to investigate

[dgibbs64]

I have tested on CentOS 6.5 and can confirm it works for me. However i have submitted a request for Facepunch to include the files are part of the server so the fix in the script is not required anymore

Facepunch/garrysmod-issues#1487

[Scarsz]

Possible fix for this could be to use all the files found in the deb file from GLIBC fix 1 but have those and upload them to a zip or tar.gz to the repository. That or we could just throw them all in the repository and implement file lists instead of adding every link to the script.

i just did a clean install again with 6.5 and I got the same error. Sigh. The first time I did it on metal and this time it was on a VM, I also tried premade vm with 6.5 and it didn't work. Is the script on your website the same as the one here ?