Jump to content
Sign in to follow this  
suma

Linux 1.62.95577 alpha

Recommended Posts

Finally a build went through a new compiler, and here it is for testing:

ftp://downloads.bistudio.com/arma2.com/update/a2oa-server-1.62.95577-Alpha.tar.bz2

Please, consider this as a highly experimental "unstable alpha" build. A new compiler was used, which means a different libc++ will be needed to run. Moreover, the server is almost untested at the moment. We have tested its basic operation shortly (connected a single player), but other than that it is untested.

Post your experiences here.

Share this post


Link to post
Share on other sites

Thank you for your work BIS, and for your graciousness to get a working version out as early as possible for us.

We'll be sure to pass on any feedback we gain during our testing.

Share this post


Link to post
Share on other sites

WATCHDOG (10609): [Fri Aug 3 06:52:35 EDT 2012] Starting server (port 2302)...

/home/15thmeu/arma2/server: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /home/15thmeu/arma2/server)

/home/15thmeu/arma2/server: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /home/15thmeu/arma2/server)

/home/15thmeu/arma2/server: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /home/15thmeu/arma2/server)

/home/15thmeu/arma2/server: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /home/15thmeu/arma2/server)

Where do I get the supported libs for CentOS 5.5 i386? yum search of coarse did not give me the answers.

---------- Post added at 13:23 ---------- Previous post was at 13:16 ----------

Appears GLIBC_2.7 not supported by CentOS 5.5 so I am SOL unless I can compile the source against the supported version. (which I don't think I can)

---------- Post added at 13:31 ---------- Previous post was at 13:23 ----------

Ok I confirmed that I cant upgrade to 2.7 so I am unable to test this server. Please tell me that 2.7 wont be required to run the final. If this is the case MANY Linux servers are going to remain shut down. Is there a good reason that the server cant be compiled with an earlier version of glibc? If so I understand but replacing the core libraries for most linux admins means replacing the OS itself entirely.

- Thanks a ton for the effort to get this out and tested.

Edited by pchaxor

Share this post


Link to post
Share on other sites

CentOS 5.x is a no go for glibc 2.7... Trying to upgrade will cause the box to become unbootable.

You won't be able to compile to it for a couple of reason... 1. BIS won't give us the source code, and 2. clearly they had to 'upgrade' to a new version of Linux to solve some compiling issues (this is a lot more concerning that most people realize), which likely means even if you had the source centos 5.x wouldn't compile it.

Either way, you're out of luck... CentOS 6 *should* work, or Ubuntu 11 will for sure.

WATCHDOG (10609): [Fri Aug 3 06:52:35 EDT 2012] Starting server (port 2302)...

/home/15thmeu/arma2/server: /lib/libc.so.6: version `GLIBC_2.7' not found (required by /home/15thmeu/arma2/server)

/home/15thmeu/arma2/server: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.9' not found (required by /home/15thmeu/arma2/server)

/home/15thmeu/arma2/server: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.11' not found (required by /home/15thmeu/arma2/server)

/home/15thmeu/arma2/server: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /home/15thmeu/arma2/server)

Where do I get the supported libs for CentOS 5.5 i386? yum search of coarse did not give me the answers.

---------- Post added at 13:23 ---------- Previous post was at 13:16 ----------

Appears GLIBC_2.7 not supported by CentOS 5.5 so I am SOL unless I can compile the source against the supported version. (which I don't think I can)

---------- Post added at 13:31 ---------- Previous post was at 13:23 ----------

Ok I cant upgrade to 2.7 so I am unable to test this server. Please tell me that 2.7 wont be required to run the final. If this is the case MANY Linux server are going to remain shut down.

Share this post


Link to post
Share on other sites

Unfortunately the server is not getting an upgrade if it is required in the final. I will retire the server and simply be done hosting. It is just not worth the hastle to admin a Linux server if it requires me to replace the OS especially when it is solid as a rock stable. (also the colo is 2 hours away and requires escorted entry) Hopefully they can get it to compile on an older version of glibc. I have faith. :)

Share this post


Link to post
Share on other sites
Unfortunately the server is not getting an upgrade if it is required in the final. I will retire the server and simply be done hosting. It is just not worth the hastle to admin a Linux server if it requires me to replace the OS especially when it is solid as a rock stable. (also the colo is 2 hours away and requires escorted entry) Hopefully they can get it to compile on an older version of glibc. I have faith. :)

Maybe one of the devs can speak to this in greater detail... but from the reading between the lines here is what I'm gleaned...

They had a Linux 'build' system that was no longer able to compile the source code for the Linux dedicated server, and had to replace it with a newer server. This was posted in another post as an update... I seriously doubt the server couldn't handle the compile physically (lack of memory or disk space), what it most likely means there is some dependency they are now using in the new code was not supported by the old 'build host'. They upgraded the build host (likely to a newer Linux OS), and that appears to have solved the issue with the ability of the code to compile.

I suspect if they were going to recode the dependency issue, they would have stayed with the old build system, the fact they are releasing this alpha suggests they plan on sticking with the new compiler, and therefore the new glibc 2.7... But that is pure conjecture on my part... just a logically conclusion based off other posts and this alpha build requiring glibc 2.7

It probably would be helpful for the Dev to post the build host OS and version so we can know what other possible issues there would be with dependencies for this build, so that dedicated server admins can migrate to a compatible version of Linux.

My guess is that CentOS 5.x is going to be a no go... any chance you have an ip kvm or drac card in that server and are able to do a remote upgrade to CentOS 6? It's just as stable as 5.x (I run a bunch of both) and wouldn't require much work to get up and running. (much easier than installing wine or doing a windows VM).

Share this post


Link to post
Share on other sites

If that is the case and what you say is truth then unfortunately I am done hosting. There is no upgrade path from 5.5 to 6.2 and no I cant remote upgrade. Even if I could... the server is solid and has other things running on it that I wont compromise or risk losing. It is what it is. Perhaps another day I will buy another (Windows) box and host an ArmA 4 server. :) I will wait for confirmation from the devs and then let the 15thMEU know that the R2 server is going to retire. I appreciate the info and is sad to see the community lose more linux servers, I have a good feeling that mine wont be the only Linux server going off line for good.

Thanks.

Share this post


Link to post
Share on other sites

I can report that the server does run on Ubuntu 12.04 LTS, no dependency issues.

Share this post


Link to post
Share on other sites

WOW

TY Suma, downloading to Ubuntu Server 10, will post any issues here...

Edit 1:

I recon this is the updating/patching procedure:

1: Patch game to 1.62

2: Add ACR LITE

3: Upload to server

4: Install 1.62.95577-Alpha on server

Optional: Install ACR FULL if you got it

5: Test and hopefully have fun?

;)

Edited by Overlord

Share this post


Link to post
Share on other sites

I suspect if they were going to recode the dependency issue, they would have stayed with the old build system, the fact they are releasing this alpha suggests they plan on sticking with the new compiler, and therefore the new glibc 2.7... But that is pure conjecture on my part... just a logically conclusion based off other posts and this alpha build requiring glibc 2.7

It probably would be helpful for the Dev to post the build host OS and version so we can know what other possible issues there would be with dependencies for this build, so that dedicated server admins can migrate to a compatible version of Linux.

The OS where we do the compiling should be irrelevant (it is some Debian, but this really should not affect the compiler output). What matters is we had to move from old GCC 4.x we were using before to GCC 4.6 or 4.7 because the old version did not support some language features used by libraries we are using now.

Share this post


Link to post
Share on other sites

My sanity check:

Ubuntu 12.04 LTS (GNU/Linux 3.2.0-27-generic x86_64)

imago@server:/opt/arma2oa/bin$ ./arma2oaserver-160-94743

Warning Message: No entry '.profilePathDefault'.

No entry '.profilePathDefault'.

Warning Message: '/' is not a value

Warning Message: No entry '.profilePathCommon'.

Warning Message: '/' is not a value

Warning Message: No entry '.extensionSave'.

Warning Message: '/' is not a value

Warning Message: No entry '.extensionProfile'.

Warning Message: '/' is not a value

Warning Message: No entry '.extensionWizardMission'.

Warning Message: '/' is not a value

Warning Message: No entry '.extensionAddon'.

Warning Message: '/' is not a value

Cannot register string STR_SUNDAY - global stringtable not found

Cannot register string STR_MONDAY - global stringtable not found

...

imago@server:/opt/arma2oa/bin$ ./arma2oaserver-162-95577

Segmentation fault

Share this post


Link to post
Share on other sites
If that is the case and what you say is truth then unfortunately I am done hosting. There is no upgrade path from 5.5 to 6.2 and no I cant remote upgrade. Even if I could... the server is solid and has other things running on it that I wont compromise or risk losing. It is what it is. Perhaps another day I will buy another (Windows) box and host an ArmA 4 server. :) I will wait for confirmation from the devs and then let the 15thMEU know that the R2 server is going to retire. I appreciate the info and is sad to see the community lose more linux servers, I have a good feeling that mine wont be the only Linux server going off line for good.

Thanks.

It's actually pretty easy just to run a backup to an external file server, add a new disk or resize a non-core partition to make room for CentOS 6 or a different distro, install via chroot method and point your bootloader to the new kernel. Then you simply resize/delete/move files and partitions around until you have a full CentOS 6 system - you may not even need to do this if you store everything custom in /home and /usr/local partitions as convention holds :)

Or you could hire somebody to do it if you're not comfortable with that.

By the way, there's no guarantee that CentOS 6 is up to date enough with libc and libstdc++. Additionally, any debian stable users will need to migrate to testing (wheezy). Most recent Ubuntu versions should work just fine (Ubuntu is based on Debian Sid (unstable))

EDIT: Imago, read readme.txt - looks like your folder variables in arma2oaserver script are wrong. :) Make sure you direct it to the correct ARMA 2 OA folder.

Edited by Kindling

Share this post


Link to post
Share on other sites
The OS where we do the compiling should be irrelevant (it is some Debian, but this really should not affect the compiler output). What matters is we had to move from old GCC 4.x we were using before to GCC 4.6 or 4.7 because the old version did not support some language features used by libraries we are using now.

Agree completely, just thought it would be short hand for the information you just posted on the version of GCC and support libraries you were using. BTW, thanks for that information it will make troubleshooting issues a lot easier.

---------- Post added at 22:03 ---------- Previous post was at 22:00 ----------

By the way, there's no guarantee that CentOS 6 is up to date enough with libc and libstdc++. Additionally, any debian stable users will need to migrate to testing (wheezy). Most recent Ubuntu versions should work just fine (Ubuntu is based on Debian Sid (unstable))

CentOS 6.x has glibc 2.7, so it *should* work, I'll post results for a test both in a couple of hours.

Share this post


Link to post
Share on other sites

To find out if you can run it with your current system:

Find in /usr/lib32 (on multiarch) or /usr/lib (32bit) the file 'libstdc++.so.6

locate libstdc++.so.6 | grep /usr/lib

For an example, let's say we found /usr/lib32/libstdc++.so.6

strings /usr/lib32/libstdc++.so.6 | grep GLIBCXX_3.4.15 | wc -l

If the above command returns '1' (or more), your current distro should support it. If not, time to upgrade :)

Share this post


Link to post
Share on other sites

Yeah.. I am going to have to deploy another server for this if I am going to continue. I am thinking ahead too .. Arma3 Linux will also need the new glibc 4.7+ also so its kinds something that needs to be done I suppose.

Share this post


Link to post
Share on other sites
To find out if you can run it with your current system:

Find in /usr/lib32 (on multiarch) or /usr/lib (32bit) the file 'libstdc++.so.6

locate libstdc++.so.6 | grep /usr/lib

For an example, let's say we found /usr/lib32/libstdc++.so.6

strings /usr/lib32/libstdc++.so.6 | grep GLIBCXX_3.4.15 | wc -l

If the above command returns '1' (or more), your current distro should support it. If not, time to upgrade :)

imago@server:~$ locate libstdc++.so.6 | grep /usr/lib

/usr/lib/i386-linux-gnu/libstdc++.so.6

/usr/lib/i386-linux-gnu/libstdc++.so.6.0.16

/usr/lib/x86_64-linux-gnu/libstdc++.so.6

/usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.16

imago@server:~$ strings /usr/lib/i386-linux-gnu/libstdc++.so.6 | grep GLIBCXX_3.4.15 | wc -l

1

imago@server:~$

linux alpha build seg faults right away, running from arma2oaserver script or not

edit:

all is well, re-downloaded from OP

md5sum 24f4c09b6232333757242bbbe7ea3610 arma2oaserver-162-95577

apparently had a bad archive download ;-)

Edited by Imago

Share this post


Link to post
Share on other sites
Yeah.. I am going to have to deploy another server for this if I am going to continue. I am thinking ahead too .. Arma3 Linux will also need the new glibc 4.7+ also so its kinds something that needs to be done I suppose.

Hope you get it working. 15th MEU servers have always been well run and great fun. :)

Share this post


Link to post
Share on other sites
Hope you get it working. 15th MEU servers have always been well run and great fun. :)

Agreed.

Hope an improved version of 1.62 Linux is out soon, my 2 favorite servers (15th MEU and Takistan Life: Revolution) are down because of it.

Share this post


Link to post
Share on other sites

Well, that's unfortunate.

In order to even test the new alpha, we (the 15thMEU Realism Unit) will need to reimage all of our servers (currently Centos 5.5) to support the required libraries to run the new server binary.

The new symbol requirements ( GLIBCXX_3.4.15 ) in libstdc++.so.6 are not supported in any current version of Centos or Redhat (even the 6.X versions). This will result in the requirement of completely reinstalling with either Ubuntu 12.04 to support the new server, or give up on Linux and install Windows (2003/2008/whatever). As our servers are remotely deployed, this will require a lot of extra effort. I'm not a programmer though. It might be possible to compile the required libraries and use an alternative LD_LIBRARY_PATH to satisfy the requirements of the new binary. If anyone has any well documented ways of accomplishing this, I would be very grateful if this information was made available to the community at large.

I'm ambivalent about the extra work. In any case, there are likely similar changes required to support the upcoming Arma 3 community alpha. This will be worthy work in the long term. It's just unfortunate that it needs to be done this late in the lifecycle of the Arma 2 series.

I'll be investigating alternatives before committing to any specific upgrade path at this time. That means that the 15thMEU public servers (and our private operational servers) will continue to be unavailable until we sort everything out.

With respect,

- 1stSgt Reite

First Sergeant

Echo Company HQ

15thMEU Realism Unit

Primary Server Administrator

Share this post


Link to post
Share on other sites

Since you guys are who you are, I would quite happily help you with that. I've had fun on 15thmeu servers. Maybe we can work something out that won't require a full disk reinstall - message me with contact info if you're interested.

Share this post


Link to post
Share on other sites
To find out if you can run it with your current system:

Find in /usr/lib32 (on multiarch) or /usr/lib (32bit) the file 'libstdc++.so.6

locate libstdc++.so.6 | grep /usr/lib

For an example, let's say we found /usr/lib32/libstdc++.so.6

strings /usr/lib32/libstdc++.so.6 | grep GLIBCXX_3.4.15 | wc -l

If the above command returns '1' (or more), your current distro should support it. If not, time to upgrade :)

I'm not sure this is accurate. I tried this test, and I got 0, and then I installed the 1.62 server and it appears to be working just fine (Stock standard Ubuntu 11.04), except that on some (not all) missions, about 3 or 4 seconds into the game, there is a yellow chain, then a red chain, and it appears to crash and restart. Perhaps someone can help me find some useful logs for this. The log.2302.txt file doesn't seem to shed any light on why its crashing. I admit, there are several mods running, and it doesn't do this on all the missions, but is there a way to check whether its a mod doing the crashing or something else. (Other than uninstalling all the mods.. that would be pointless, because the missions wouldn't start at all without the mods...)

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
Sign in to follow this  

×