starred/LinuxGSM

Fork 0

mirror of https://github.com/GameServerManagers/LinuxGSM.git synced 2026-04-25 14:15:59 +03:00

[GH-ISSUE #986] Arma 3 Server GLIBC requirements up to 2.20 #782

New issue

Closed

opened 2026-02-27 02:53:28 +03:00 by kerem · 11 comments

kerem commented

2026-02-27 02:53:28 +03:00

Owner

Originally created by @dgibbs64 on GitHub (Aug 9, 2016).
Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/986

LGSM currently sets GLIBC requirements at 2.13 however after investigating this in light og the gmod glibcfix issue is appears its gone up to 2.17. I am trying to get this working however I am getting seg faults. It may simply not be possible to get Arma 3 working with a GLIBC fix anymore. I will make further attempts however I may change the requirements and have ARMA 3 no longer supported on the likes of CentOS 6 with GLIBC fixes.

Originally created by @dgibbs64 on GitHub (Aug 9, 2016). Original GitHub issue: https://github.com/GameServerManagers/LinuxGSM/issues/986 LGSM currently sets GLIBC requirements at 2.13 however after investigating this in light og the gmod glibcfix issue is appears its gone up to 2.17. I am trying to get this working however I am getting seg faults. It may simply not be possible to get Arma 3 working with a GLIBC fix anymore. I will make further attempts however I may change the requirements and have ARMA 3 no longer supported on the likes of CentOS 6 with GLIBC fixes.

kerem

2026-02-27 02:53:28 +03:00

closed this issue
added the
type: bug
label

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@jach11 commented on GitHub (Aug 9, 2016):

Users shouldn't expect to be able to run a 4 year old release of an OS and not run into any issues. Either install the new OS to meet the minimum requirements or start using a rolling distro.

@jach11 commented on GitHub (Aug 9, 2016): Users shouldn't expect to be able to run a 4 year old release of an OS and not run into any issues. Either install the new OS to meet the minimum requirements or start using a rolling distro.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 9, 2016):

It used to work in CentOS 6 with the Glibc fix however it appears not to anymore. I have just tested on Ubuntu 14.04 that uses Glibc 2.19 as well. That also failed with a seg fault. Can anyone confirm what version of Glibc is the min requirement for Arma 3 as I cannot confirm due to crappy documentation.

Once confirmed I can update my documentation and remove it from the glibc fixes

@dgibbs64 commented on GitHub (Aug 9, 2016): It used to work in CentOS 6 with the Glibc fix however it appears not to anymore. I have just tested on Ubuntu 14.04 that uses Glibc 2.19 as well. That also failed with a seg fault. Can anyone confirm what version of Glibc is the min requirement for Arma 3 as I cannot confirm due to crappy documentation. Once confirmed I can update my documentation and remove it from the glibc fixes

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@jach11 commented on GitHub (Aug 9, 2016):

It looks like Glibc 2.20 is required but i haven't tested it yet.

@jach11 commented on GitHub (Aug 9, 2016): It looks like Glibc 2.20 is required but i haven't tested it yet.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 10, 2016):

It's looking that way. Which means it's by far the highest requirement mist being 2.15. Once confirmed 2.20 I will attempt a glibc fix.

@dgibbs64 commented on GitHub (Aug 10, 2016): It's looking that way. Which means it's by far the highest requirement mist being 2.15. Once confirmed 2.20 I will attempt a glibc fix.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@jach11 commented on GitHub (Aug 10, 2016):

I tested it on Debian 9 with Glibc 2.23 and it works just fine.

@jach11 commented on GitHub (Aug 10, 2016): I tested it on Debian 9 with Glibc 2.23 and it works just fine.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 10, 2016):

I have contacted Bohemia. Hopefully they will 100% confirm this for me as the only distro I can find using 2.20 is an old fedora build. I can confirm works on Ubunut 16.04 as well. However I would prefer confirm 2.20 is accurate rather than just guess.

@dgibbs64 commented on GitHub (Aug 10, 2016): I have contacted Bohemia. Hopefully they will 100% confirm this for me as the only distro I can find using 2.20 is an old fedora build. I can confirm works on Ubunut 16.04 as well. However I would prefer confirm 2.20 is accurate rather than just guess.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 10, 2016):

Just tested on Fedora 24. Getting seg faults. Arma 3 server is a right pain.

@dgibbs64 commented on GitHub (Aug 10, 2016): Just tested on Fedora 24. Getting seg faults. Arma 3 server is a right pain.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@jach11 commented on GitHub (Aug 10, 2016):

I have gotten it to run on CentOS 6.8 with Glibc-2.20 installed.

@jach11 commented on GitHub (Aug 10, 2016): I have gotten it to run on CentOS 6.8 with Glibc-2.20 installed.

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@dgibbs64 commented on GitHub (Aug 12, 2016):

I have figured out the issue on my end. My Test VPS RAM wasnt enough. Ouphs...I have added the system requirements to 1GB min so there is now a warning should the server have less that 1GB Glibc Requirements are still correct :)

@dgibbs64 commented on GitHub (Aug 12, 2016): I have figured out the issue on my end. My Test VPS RAM wasnt enough. Ouphs...I have added the system requirements to 1GB min so there is now a warning should the server have less that 1GB Glibc Requirements are still correct :)

kerem commented

2026-02-27 02:53:28 +03:00

Author

Owner

@jach11 commented on GitHub (Aug 12, 2016):

Hah. That'll explain it.

@jach11 commented on GitHub (Aug 12, 2016): Hah. That'll explain it.

kerem commented

2026-02-27 02:53:29 +03:00

Author

Owner

@lock[bot] commented on GitHub (Jul 19, 2018):

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock[bot] commented on GitHub (Jul 19, 2018): This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.