Mavy

Administrator
  • Content count

    259
  • Joined

  • Last visited

Community Reputation

398 Excellent

1 Follower

About Mavy

  • Rank
    Has a particular set of skills
  • Birthday 08/10/87

Recent Profile Visitors

568 profile views
  1. hekhal
  2. YOUR NAME : Mavy PLAYER NAME : Katla_Haddock BAN ; Posted direct copy text from Mein Kampf knowing that people got banned for it. As admin I cannot tolerate CM's to behave in such a manner. For that reason I have decided to impose a 1 week ban.
  3. Sadly this is a complex issue. There is multiple reasons performance is so bad. Some we can "sort of" tune and some are out of our hands. The parts we cant solve are related to the server engine, even with 64-bit performance of the engine is sub par. Even with the move to a more powerful server we would still run into another issue, the net code. There was a 250 player test on the arma sub reddit this weekend. It was a 125v125 PvP that used some mods like TFAR but was mostly vanilla. Even that showed poor performance as the servers net code couldn't deal with the amount of data being handled. Then there is the matter of tuning. I started this process before 64bit was released, it is a slow process of changing settings every day to see what performs best. This is however made harder by the lack of a proper way to monitor server perfomance. The other thing we did was reactivate the headless clients. This greatly helped with the performance, specifically the zeus performance. So we are making steps with regards to performance, however it is slow going. As for the client side fps, these issues can be linked to both the net code and the client side engine. Due to our unique player base we will always see some performance impact from pings and desync.
  4. Ban extended to end of June. This was at the request of Monkeh himself.
  5. Could you please encase the code block using the actual code tag? This function is here for a reason! It makes everything look cleaner! But yeah, pastebin or attachments would have been a better options to start with.
  6. We currently have plenty of server space to deal with all the games. I am more worried about licenses atm
  7. Uninstall all your java versions, reboot, then install 32bit again.
  8. Try installing the 32bit version of Java. I think A3S relies on some 32bit libraries.
  9. As most of you know by now the repo has been down for a few days due to some security concerns. In this post I will try to explain why I took such measures and more importantly what I did to fix things. Let me start by saying that none of my personal info was leaked. The info shared was that of a repo server I was building. It was in no form secret or private data! The incident: Last Thursday the new 64-bit version of ArmA rolled out, and with it a load of new bugs and mod updates that we had hoped wouldn't be needed. As a result I decided on Friday that I would add a new repo server and set up some form of balancing between the 2. As I was in the process of configuring the new setup I had asked the one of the CM's to test some things for me. During this test 2 things happened. Firstly the CM's got so excited they all decided to start downloading, not what I asked for guys. This caused some frustration as I was trying to do some log tests. Second I noticed someone was actively trying to circumvent the blockades I had put in place during the testing. Now this in itself I don't mind, if anything I applaud people who test our infrastructure. It helps me make things more resilient and allows you guys to enjoy a safe environment to share your stories in. However! I do not want some kid to go on non FK channels and boast about his escapades. Not only is this a gross breach of trust it is also against everything I stand for myself. What ever he found he should have reported to me, and no one else. Sadly for him he didn't really find anything useful. The info he gathered was something anyone could have found with some simple techniques. Hell I am going to share the same details with you guys right now. The new repo setup: In the past we had one repo server that would host a simple web server, this would allow arma3sync to connect via http which it used to download the mods. This box had reached its limits with regards to network speeds and caused painfully slow downloads. To expand this setup I would need a new server and a way to "balance" the load, however due to the amount of data we send out a true load balancer was not an option. Instead I have opted for redirect technique. What does this mean? It means we now have 3 web servers for the repo, one front end and 2 back end servers. In detail: The front end (a3sync.fuckknows.eu) hosts a small webserver that takes an incoming request and redirects you to another url. It does this by picking a random number between 1 and 4, based on that number it knows what repo to redirect you to. This is not real load balancing, however it does allow us to share load over the 2 repo's. It also allows us to add more servers fairly quickly if we decide to expand in the future. The back end hosts (repo1.fuckknows.eu & repo2.fuckknows.eu) are web servers that hold the actual repo files. They operate standalone from the front end and allow you to directly connect to should you so desire. They do nothing more but serve files that arma3sync downloads. Al in all this is not really rocket science, it is a fairly simple setup that allows for easy management and expansion. The future: What happened last Friday in detail? On Friday evening I changed the a3sync url, instead of pointing directly at repo1 it would now point at the front end server. I had disabled this web server while I did the initial setup and synchronization of the new repo server. During a short period of time I brought it online to perform some tests, in these 5 min tops several people connected and tried to download mods. Once I disabled the front end I expected load on the repo servers to drop again, however that did not happen. A quick look at the log files told me someone was bypassing the front end and when I blocked repo1 that same IP jumped to repo2. I did this testing several times and every time the same client IP popped up. That IP was also using a tool other then arma3sync to download with. I responded by banning that IP from the servers and thought nothing more of it until the screenshot posted by Linnet reached me. What did I do to prevent this? Even tho I can not make the setup 100% obscured due to the way arma3sync works, I can limit the way's people connect. One of the things I can do is limit the allowed user agents to the web servers, anything other then arma3sync gets a 403 error. I have also increased the monitoring of the log files, repeated attempts to access the repo without arma3sync will get an IP ban. This ban will get propagated to all FK servers in a matter of minutes. Again I encourage people to try and find issues with our infrastructure, however I do ask you do it in a thoughtful manner. I am not asking you to try and ddos our servers because any monkey can do that for a few bucks. I am asking you to find holes in our security and reporting them to me. If I find anyone exploiting our servers or sharing private info I will not hesitate to report you to the police and your ISP. Needles to say such an action will also result in a ban from our community.
  10. Just wanted to give you guys an update on the repo status. I have pushed the new repo to our servers, yes servers!, the new update is about 7GB due to an issue called RHS. To help deal with the larger amounts of players I have added a second server to "balance" the load between the 2. Note how balance is in quotes, this is because it does not actually balance the load. A server gets picked at random everytime you connect to the repo. The reason the update is once again several gigabytes is because RHS decided to include an update script in their latest version. Sadly however the servers that contain the updates did not actually get updated. As a result our repo now contained an older version of RHS then before. We never ran into this issue because RHS used to upload their mods to several other sites. However as of 4.2.1 they started using the workshop. Instead I opted to use said script with this disastrous result. I am still having some difficulty with the new repo, however as soon as those are resolved I will bring the repo back online.
  11. Anden, var=PreRelease if var == "PreRelease": print "Not ready for production!" elif var == "Stable": print "Yay we are in business" else: print "I don't know what you are but you ain't coming near my servers."
  12. I will update the repo with the 64bit dll today. The latest dll did not get released properly til yesterday evening. Keep an eye on the repo for an update soonish.
  13. Don't let me stop you from testing this. But keep in mind that the new version is planned to drop within the next few days. So if you truly want to test this I suggest you do it asap.
  14. To be very blunt: don't waste time on this. Why? I offered the ArmA developers a source of information in the form of this community, they declined it. I asked them why they had not asked the arma community for help, they responded with radio silence. (2 hours after I asked the post asking for help popped up on their forums and reddit...) The new version is about to be released this week. It will include 64bit and a ton of bug fixes. For all we know it will mark the end of the 3fps bug.
  15. Changelog: Added CUP_Terrains_CWA 1.3.0