DarkEnergy

So i have a not to shabby VDS and seeing the load under 50 slots 60% cpu and 50% RAM. I decided to up the slot count to 70 confident that it can take more players. on this trail run where wen the server hit 60 it began to have network issues. yellow/red chain and drops 10-20 people with to high ping message. Then it restores itself. So I am guesing it is either a stability issue or networking. But i am on a VDS with a 10 Gbps line with an outgoing 1 Gbps. Not that that is really available to my VDS but I am just saying this should not be a issue. If you are an admin of a high slot count server could you advise me on what could be the issue. Any advice would be welcome. I know there are config files for networking for arma but im not confident enough to touch those. any help would be appreciated

Thats what I tough a issue with arma itself. seeing as it is not heavy on networking and uses UDP. But i was monitoring the system and it looked stable and not maxing the resources. As for the VDS it is not a perfect method but it is still close to the a physical box. I think i am going to do some digging\tweaking and some more testing before i will let it go but thanks for your input.

Keep the good work up. It is working like a charm.

its not exactly my issue tough. it seems they are ignoring it seeing there is nobody on the bug at this moment.

So i have a not to shabby VDS and seeing the load under 50 slots 60% cpu and 50% RAM. I decided to up the slot count to 70 confident that it can take more players. on this trail run where wen the server hit 60 it began to have network issues. yellow/red chain and drops 10-20 people with to high ping message. Then it restores itself. So I am guesing it is either a stability issue or networking.( still in the green in resources 70% ish) But i am on a VDS with a 10 Gbps line with an outgoing 1 Gbps. Not that that is really available to my VDS but I am just saying this should not be a issue. If you are an admin of a high slot count server could you advise me on what could be the issue. Any advice would be welcome. I know there are config files for networking for arma but im not confident enough to touch those. any help would be appreciated mine ? took 3 days i send it in about a week ago PS: does anybody know if making your server permanently day is a no no ?

same story no vehicles at all now on day 4. count yourself lucky indeed.

Well that's news to me. Then it is kinda weird/lame that he does not recommend a beta to enforce in a pinned thread .. I will update my server to the latest then hope the player base follows suit. the failed beta patch caused high fragmentation in what beta people use.

thanks look in your thread

you should enforce the beta you run. ->95883 as i understand. The whole point of that is to prevent other beta clients to join and have the invisibility thing or other unreported results. I am so unsure on witch beta i should run my server on do you have a clue on where the player base is at this moment ?

Hey Ryahn, I have to thank you again for this great addition to my server. And to report that everything is running as intended except for one thing. The way we set up the restarts by starting servertools.exe is not working. Firstly is that BEC does not allow .exe but i created a .bat file that it does allow. START /REALTIME C:\tools\servertools.exe sadly when executing it gives me this. maybe i need to add parameters to the .bat But i am now using #shutdown again to do the restarts. Heartbeat.exe picks everything up nicely and reboots the server.

ready when you are :)

well if you are still up for an remote session to see what is up that would be great. it seems bec launched correctly but then either crashes or ? also it seems when it checks heartbeat it does not see the active server and launches another instance.

reporting back in. it boots the server :) haven't checked if heartbeat works properly. it seems that bec exits after sigma triggers it i have increased the timeout to see if that was it. does your program add the parameter -f config.cfg to bec.exe when it boots it ?

alright ill adjust it and report back thanks for the quick response

Sadly i cannot get it to work. the server and bec are functioning properly. I suspect i either did something wrong on the pid part, or it is a pathting issue. #Please read the readme.txt before messing with these settings. #Title of Program titleserv= xxxxxx Log Rotation #Locations beroot2=SET beroot="C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead\cfgdayz\BattlEye" startdayz=SET dayz="C:\Program Files (x86)\Steam\steamapps\common\arma 2 operation arrowhead" LID= xxxxxx pidfile=C:\Program Files (x86)\Steam\steamapps\common\pid install=C:\Program Files (x86)\Steam\steamapps\common #Required File Names To Be Killed beckill=Bec.exe heartkill=heartbeat.exe #Custom Task Kills #task1 //Cannot be used until next release #task2 //Cannot be used until next release #task3 //Cannot be used until next release #task4 //Cannot be used until next release #task5 //Cannot be used until next release #task6 //Cannot be used until next release #task7 //Cannot be used until next release #Timout Settings (All times are in SECONDS) timetask=2 timelog=5 timebec=30 timewarm=5 timerunning=45 timereset=5 # Dayz Configurations name=-name=cfgdayz_derp config=-config=cfgdayz\server_derp.cfg cfg=-cfg=cfgdayz\arma2.cfg profile=-profiles=cfgdayz ipserv=-ip=xxx.xxx.xxx.102 port=-port=2302 world=-world=Chernarus cpu=-cpuCount=3 threads=-exThreads=1 #What ever is set here, Must be set at pidfile pid=-pid=C:\Program Files (x86)\Steam\steamapps\common\pid\pid.txt nocb=-noCB maxmem=-maxMem 2047 nosound=-noSound #Can be set with - Realtime, High, AboveNormal, Normal, BelowNormal, Low priority=/Realtime #DayZ Server priorityh=/Realtime #Heart Beat prioritys=/Realtime #Server Tools priorityb=/Realtime #BEC # Bec becpath=C:\Program Files (x86)\Steam\steamapps\common\BEC beccfg=Config.cfg #What ever is set here, must be set in beckill becexe=Bec.exe

Ha nice just god my dedicated installed with bec this makes an excellent addition. now i see that you have uploaded a new version with an installer great !

So i have just setup a new server and everything went great. but now i have 90% or more players getting dropped from my server. in console the lines that pop op allot are; Could not connect to BE Master Update attempt failed is the master server for BE down or is my battleye version outdated ? Thanks in advance,

Great at least it is not my end :)

Very nice ! <3 So few resources indeed needed to scour everywhere for it. But this is great I am getting an unmanaged server so this is just great !

well fuck missed the vps restock. brilliant that you cant reserve have been checking the site per a day for the last 2 weeks -_- fuck me right ? Well have fun i am out.

This has to happen sooner then later. Even without the fix for the tents it would be great for the barb/tent clutter. 5 minutes ago i just got a pm from a mate that found 50 satchel charges. I have been playing this game for quite a wile and never found or saw one. This guy finds 50 of them and after server restart can get 50 more. So he is on his way to blow up an entire city with them. Currently i am not playing the game because this is FUBAR.

Why spread this to the forum ? now every noob will go there.

Hello, Back once again. So we are starting to compare your offer to other providers. Please tell me if i missed something. HA 100 Mbps / - p/m 3GB RAM 100 GB HD E3-1230 2 treads @ 3.6 GHz OS: Windows Server 2008 standard Locations: unknown VDS flexibility, upgrading parts is possible. Day-z Preinstalled. No Whitelisting stock in 1-2 weeks, no posibility to reserve. 50,00 $ p/m Cheers

hi again, ETA on VDS ? Please, if you are unable to stock up for a long period of time, let me know so i can move on.

this interests me to. I am checking for update on that vps stock every time gimme a vps :( edit: nvm jsut read the whitelist stickie. we could do it if you reserve a ip for us tough.