Jump to content

pchaxor

Member
  • Content Count

    337
  • Joined

  • Last visited

  • Medals

Everything posted by pchaxor

  1. pchaxor

    Linux 1.62.95577 alpha

    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. :)
  2. pchaxor

    Linux 1.62.95577 alpha

    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.
  3. Well then BIS must be false advertising if it says they support it but don't. Unfortunately, there is nothing you or anyone can do about it other than rant and be mad about it. That doesn't get results it only gets threads locked and people banned from the forums. I have learned over the years to change the things you can and leave the things you cant. I think BIS or someone needs to come out with more info though... "It's ready when it's ready" is getting pretty old for quite a few people.
  4. I am the author of the No ranting thread that got ranted all over. (I tried) I actually own my server, and the hosting I get for free because I admin for a company. I chose Linux for many reason I am not going to get into as this is not a "what is better" argument. I made the choice and yes it sucks right now but I know BIS will get it done. I know all of us linux server admins would really LOVE an update on the progress but considering the hostility BIS has received from the community I would not doubt that they will postpone or drop Linux support all together. I too understand the NEED, but I also understand economics and the cost of development. Does Linux Support make BIS money? Are we paying for the support? Maybe we should be. Perhaps we consider that BIS gives the Linux support as a gift and not EXPECT and demand it unless we are willing to pay for the support costs of having an on staff programmer that can do the Linux updates along side of the windows updates (beta and all). Thoughts?
  5. RANTING = To suddenly give a long speech that usually results in rambling and repeating of nonsence. Old thread locked and then redirected to now an irrelevant ranting post in a beta forum... Source: http://forums.bistudio.com/showthread.php?137632-ARMA-2-OA-beta-build-95248-%281-62-MP-build%29&p=2193863#post2193863 Just wanted to create this so it is relevant in the forum most Linux admins are going to look. Just an update: Bugs were found in the Linux server code a few days before launch so it was postponed and is being worked on. "It will be ready when it is ready" is what I gathered from searching and reading through posts. There is no new news as of yet so please just try to be patient. *** If you rant in this post it will get locked so please no ranting. I would like this post to serve only as a place to get updates on the status of the linux server for those that want to know.
  6. I would honestly expect more admins to be offering to test an alpha when it is ready, or maybe get excited that the Linux version they are working on is by far the best one ever made by man. The reason they are taking so long is probably because the version is super duper special and requires super duper programming to make it work super duper good. When it does finally come out your server is going to start running the best it ever has and then you will chant how great BIS is and how immature you acted by making all that fuss. My words of wisdom... Just relax and sit back and spend some time with your family and friends. Love one another. Just think... your wait now will only make you appreciate it more when it is finally here. It will be like the greatest thing ever. Super Linux Server Surprise! Christmas in August. :) So please just sit back, drink a brew and take a chill pill.
  7. The facts are in. It is what it is. Just be patient.
  8. Sounds like a bunch of ranting useless information that has nothing to do with the actual release or status of the 1.62 Linux Server. RANTING = To suddenly give a long speech that usually results in rambling and repeating of nonsence. Please shut the hell up unless your name is Suma, Dwarden, Maruk or a Moderator that has valuable information that results in education and knowledge. 99% of Linux server admins just want to know WHEN and this thread will hopefully get an update next week telling them when to expect it or why it is not happening. Your ranting (like I am doing now) will only cause this thread to get locked. Please stop so we can use this thread for COMMUNICATION purposes. If you have something to say about DayZ or whatever else ... there are PLENTY of threads out there. Not this one. again: please. ---------- Post added at 19:01 ---------- Previous post was at 18:57 ---------- Thanks Max Powers for enforcing. Feel free to lock the thread if you feel you have to. Suma, Maruk and Mods can post in locked threads so this may be best anyways.
  9. yeah your right on the 1.60. I could have done an rsync, but opted to do fresh.
  10. I think most of us Linux server admins are just going to wait to do it right. WINE to me (opinion) seems like a coble job to get inferior code to run on a superior box at the cost of resources and possibly causing more issues that may result in a trip to the colo. We are just going to have to stop WINE'n and wait for the real deal to be ready.(I am a funny guy heh?) If BIS Devs need a few Linux admins to test an Alpha ... I have a box ready for testing. (I would rather be part of the solution than the problem.)
  11. Linux admins have to update to 1.62 and then upload the 17GB of data and then install the server. Ok so maybe a week out or less if you have physical access to your colo servers or they provide you with the updated server files. I am not so lucky. The mere release of the server linux code is a small part of what it takes to prep my arma2 linux server for production use. (not including any ACE updates that come during the wait) I am uploading 1.62 now in prep of the new server code while maintaining the 1.61 server. It appears that most players have updated to 1.62 and the only servers found now in the gs list are the Windows DayZ servers. We used to pack a full house but now there is only a hand full on the server. Oh well a short break for fresh bug free server code right? :)
  12. Question: When linux server is available do we need to upload the 17GB of 1.62 data files to the server again or will the patch convert the 1.61 files on the linux server to 1.62?
  13. If the servers you are trying to connect to are Linux then they are still at 1.61 since there is not yet an update to 1.62 for Linux. They are working on it so Linux servers should be updated in a few weeks.
  14. Only windows servers can be updated. So if they are Linux Servers it could be some time before they are updated. (maybe a week or two or more)
  15. First off thanks Maruk, Dwarden, Suma and the rest of BIS for all your hard work on making Arma2 so great. So many years invested with you guys and I LOVE YOU with all my heart. Great people doing great things. HELLS YEAH! Now for my rant ... I think some of these people need to take a week off and go for a walk or maybe do some geocaching, hiking, camping maybe some metal detecting, go spend time with family or just take a freakin break from it. I think it would be good for us instead of the complaining and ranting. You know, the devs have to take time away to go deal with this crap in the forums instead of fixing the problem or spending time with their family... So big fuckin whoopie ... your server is empty, well you know what so is ours. Yes, we run Linux and we preach to all the players to not upgrade until the servers are updated, they know this and you should do the same. Its a few days; maybe a week, let them do their jobs and get it done and get it done right. I would rather shut my servers down for as long as it takes and go play some DayZ until it is ready for production than listen to another mother fucker cry and bitch about no linux server blah blah blah. If you don't like it and how shit works 'round here then get the fuck on. The community don't need cry baby ass bitches. :) Sorry ... just irritates the shit out of me ... SHUT THE HELL UP ALREADY and let them get it done.
  16. Also waiting on the linux 1.62 server for several well populated servers. - We are telling all DO NOT UPDATE until the servers have been updated. - We understand linux server is low priority, but an update on ~date/exact time would be nice. :D lolz Love ya BIS! ---------- Post added at 22:57 ---------- Previous post was at 22:50 ---------- I have 2 systems with Steam versions ... both systems ignored the "Do Not Keep Updated" option. I had to manually pause both, so if you don't realize it is updating and you say ... go to work. Your screwed. I am not mad because I stopped it but I can see how it could make things crappy for some.
  17. Makes sense. I updated the Tracker with ... I edited the Domination mission and commented out the spectator script init in decsciptions.ext: // #include "spect\spectating.hpp" This removes the spectating script but also allows a player with broken ACRE to drop the radio and pick it back up to fix the problem. I suspect there are also compatibility issues with the respawn script we are using and ACRE also. I am not sure this is an issue with ACRE itself but perhaps an issue with script compatibility. I think an ACRE dev might be able to see where these scripts are failing and maybe advise on a correction or work around. Thanks!
  18. You can surely come play on the 15thMEU Recruiting servers and try it out. We think it has alot to do with the Kegetys spectator script and ACRE compatibility. Dropping the radios, pack / unpack, mute and unmute in TS3, quit and reconnect TS3 does not fix. You have to disconnect to lobby and reload back in. Does any of your missions use Kegetys spectator script?
  19. haha they have found the bug, its been reported over and over again and the bug track just gets closed from what I can see. I am just trying to see how or why its not getting fixed or what can be done to get the problem fixed. I know its free and in that same respect appreciate their work getting it this far; if it is money stoppping the bug from getting fixed I am sure the community (including us) can come up with a good donation. I dont think it's that though. I can share that it is quite annoying having to explain the "drop the radio and pick it up fix" to every pubber/person that all of a sudden starts broadcasting to 30+ people in the ts3 channel and wondering why everyone is talking at once. So we will just let this be and since there is no support on getting it fixed obviously we will just deal with it and just keep saying "its broke". Eventually players will just not bother with acre since it has a reputation of "crashing" and not working proper so it becomes more of a hastle. So ok .. I will leave it and just hope that one day eventually they can get the time to look at it and come up with a solution. Thanks! Edit: sorry for the attitude here, just frustrated.
  20. Either way the issue is annoying and seeing bug tracker threads opened, ignored and then closed with no resolution is just silly. 6-9 mos on the same bug??? really? its the blame game. someone fix it please? (We run both insurgecy and domination missions.)
  21. Not true with the 148VHF, 343 sure. Just would be nice for them to take this serious and get it resolved. If it is mission side issues then what do we need to change? The spectator script? any coders now how to fix it?
  22. Great work, but is there any chance this issue can get resolved soon? http://tracker.idi-systems.com/issues/224 Seems to be a common issue and unreseolved with a low priority. This is a real problem and can confirm it exists on both unit servers amoungst all players. (Insurgency and Domination ACE missions) Thanks!
  23. Perhaps this has been answered already and the answer I read maybe wasn't the answer I was hoping for... Is there an easy way to update a Linux server with major patch updates other than rysnch or transferring all the changed pbo files again? Does Six-Updater by chance support the synch of dedi linux updates? That would be the bestestest. I know it would be quite a feat to actually update the game files on Linux, but I just wanted to ask before the next update so I am prepared. A major update would of coarse put our server down for a day or so if updated files had to be re-transferred. Thanks! ---------- Post added at 01:14 PM ---------- Previous post was at 01:12 PM ---------- Maybe this post should have gone under Multiplayer ... not sure.
  24. Will this work with 1.03?
×