howichrgelazer

Honestly, they are also under the minimum player count. I think a server needs to have at least 20-25 slots. Unless they are testing, then something is possibly going on. Keep in mind locked =/= passworded. But it's odd to me their server name is that. I thought you needed to restart the server for a name change to take effect. It's almost like it's planned?

I agree with blergh. I'd like to know about how it monitors "lag," what the definition of "lag" is in this case, and what is its benchmark to compare numbers? Just to get an idea of what this program will be able to do and how it monitors the server. :)

If somebody was infected it could have spread to you. Don't know why you weren't coughing though. Keep in mind, there is a chance you can get an infection after being wounded or you start bleeding. It's not always about body temp and all it takes it one person to get it in the group.

Did a reboot and messed with a few things, and it looks like people are logging in successfully now. I tried it myself too. Sorry for the downtime today guys. I guess something bugged out with the beta update. Going to investigate further. (There were issues with the hive today earlier today, but yeah. Looks like there was something on my end as well.) EDIT: If you guys are still having problems, please let me know. I'm still concerned about the routing I see when trace routing the master db. It doesn't seem local to the server though, because I see it happen on my PC as well. EDIT 2: Okay, We found the issue aside from the hive problems everyone was having earlier today. I messed with the bandwidth settings to tighten some values (utilize more of our bandwidth to make things more responsive). It was causing some weird problems on loading. Should be sorted now and things should run smooth. We just needed some changes on a mission file for a jip workaround Dwarden was testing.

I brought it back up for now, looks like things are still de-syncing. So your mileage may vary. Unfortunately there's nothing I can do from this end. But hey, they don't call it an alpha for nothing ;)

Master server seems to be having issues again, going to leave the server locked with 0/50 until I notice that it has calmed down. This is an issue across most if not all DayZ servers. Doesn't look like character data is loading (or possibly even saving) :(

Hahah, I'll do that. Sorry, I haven't paid attention to steam all weekend. Between working on the server and trying out some development bug fixes and helping other admins in IRC I completely forgot about everything else. I think I maybe got an hour or two of the ghostbusters game in and that was it :P

Server has been up and running since last night. I've been monitoring things and it looks like the master server had it's routing issues sorted out. Other admins were reporting things working on there end as well. :)

Would it help you to keep this spreadsheet going? https://docs.google.com/spreadsheet/ccc?key=0AgcDCzWfiNxrdDRPTXVDVG1CM0V6Z2l2TEJ0ZzRPTGc I can pass ownership over to you if you'd like as well.

Admins don't have the ability to kill people, teleport people or, anything of the sort. Somebody is exploiting/cheating on there. Be sure to report it to the server admin so he/she can get a log of it.

You may want to consider changing the colors of that yellow text. It's impossible to read on the white theme :P

I'll start with what I found today r_player_ 10.06.2012 12:30:36: gaybutt (76.188.209.92:2304) dec49607ac619c6bd574504e0d5f1231 - #13 pos %4; newvehicle setdir %5; newvehicle setVehicleInit " this setVehicleVarName ""vehicle_%1_%2"" 10.06.2012 12:30:36: gaybutt (76.188.209.92:2304) dec49607ac619c6bd574504e0d5f1231 - #37 _ALICE_Pack_EP1","DZ_Backpack_EP1"]; r_player_ 10.06.2012 12:28:42: gaybutt (76.188.209.92:2304) dec49607ac619c6bd574504e0d5f1231 - #13 pos %4; newvehicle setdir %5; newvehicle setVehicleInit " this setVehicleVarName ""vehicle_%1_%2"" 10.06.2012 12:28:43: gaybutt (76.188.209.92:2304) dec49607ac619c6bd574504e0d5f1231 - #37 _ALICE_Pack_EP1","DZ_Backpack_EP1"]; {_abox addWeaponCargo [_x,100];} forEach _dayz_wep; {_abox add 10.06.2012 12:28:46: dvsdiablo (98.180.48.197:2304) 96b8a9bdd9b4010de80919a868ac4b09 - #37 layer addMagazine _x} forEach _mags; {player addWeapon _x} forEach _wpns; }; r_player_ 10.06.2012 12:23:28: gaybutt (76.188.209.92:2304) dec49607ac619c6bd574504e0d5f1231 - #13 pos %4; newvehicle setdir %5; newvehicle setVehicleInit " this setVehicleVarName ""vehicle_%1_%2"" 10.06.2012 12:23:29: gaybutt (76.188.209.92:2304) dec49607ac619c6bd574504e0d5f1231 - #37 _ALICE_Pack_EP1","DZ_Backpack_EP1"]; ---------------------- hint "Weapon spawned.. 10.06.2012 12:15:48: Gerasic Eravle (82.6.50.36:2304) 4eca1302efe45aa1c9fbe0b5577c1725 - #31 marker = "playerMarker" + (str i); marker = createMarkerLocal [marker,pos]; marker setMarkerTypeLoca 10.06.2012 12:15:48: Gerasic Eravle (82.6.50.36:2304) 4eca1302efe45aa1c9fbe0b5577c1725 - #32 marker setMarkerTypeLocal "mil_dot"; marker setMarkerPosLocal (pos); marker setMarkerColorLocal("Col 10.06.2012 12:15:48: Gerasic Eravle (82.6.50.36:2304) 4eca1302efe45aa1c9fbe0b5577c1725 - #37 #line 1 "mapgps.sqf" player addWeapon "ItemGPS"; player addWeapon "ItemMAP"; --------------------- r_player_ 10.06.2012 12:10:43: RG (71.163.130.247:2304) 5ce90e28c21e71b76ca17a1a8946e6ed - #31 marker = "playerMarker" + (str i); marker = createMarkerLocal [marker,pos]; marker setMarkerTypeLoca 10.06.2012 12:10:43: RG (71.163.130.247:2304) 5ce90e28c21e71b76ca17a1a8946e6ed - #32 marker setMarkerTypeLocal "mil_dot"; marker setMarkerPosLocal (pos); marker setMarkerColorLocal("Col 10.06.2012 12:10:44: RG (71.163.130.247:2304) 5ce90e28c21e71b76ca17a1a8946e6ed - #31 marker = Format["%1Markers%2",_count,_obj]; createMarkerLocal [_marker,position _x]; _marker setMark 10.06.2012 12:10:44: RG (71.163.130.247:2304) 5ce90e28c21e71b76ca17a1a8946e6ed - #31 marker2 = "VehMarker" + (str i); marker2 = createMarkerLocal [marker2,getPos veh]; marker2 setMarke 10.06.2012 12:10:44: RG (71.163.130.247:2304) 5ce90e28c21e71b76ca17a1a8946e6ed - #32 rker2 setMarkerTypeLocal "mil_dot"; marker2 setMarkerPosLocal (getPos veh); marker2 setMarkerColorLo Looks like the first spawned vehicles, the second spawned a gps and a map, and the third tried marking vehicles. Are these legit for permabans?

I'm gathering logs and have a few people that are suspect. :)

I'm gathering logs right now. :)

Should be up within the next 15 minutes guys. Just setting FireDaemon back up. EDIT: Server is up

Hey guys because of the breach today, we're going to do a complete overhaul of the server, just to make sure we aren't affected. I'll try my best to have it up and running again by 9:00pm central time. Sorry for the inconvenience. Just want to make sure we have a secure and stable server for all to play on. :) EDT: The DayZ team has posted about the breach here: http://dayzmod.com/forum/showthread.php?tid=9123

I've been trying to compile a list like this, but my thread keeps getting knocked to the bottom (server list project). Although, the dev team said they are going to change the naming system to allow for values in the name. I haven't heard anything since though.

We do not have a community tag no. The only admin that wears a tag is Crooked' date=' but that isn't our clan either. Any admins that join the server should be announced by BEC (unless it glitched). I am looking to create a sqaud.xml at some point though. I'm sorry, but the ban will not be reversed. I have the chat logs saved from this and you guys caused a bit of disruption with the usage of racial slurs. Two of them still decided to chime in after the warning. Even though you may have been the one that stopped, as a whole your community acted unprofessional (Unprofessional probably isn't the best word here, but you get my drift). That type of "roleplaying" is unacceptable for our environment.

Thank you for the kind words FailBoatin. The server is now back up, sorry for the delay there. Our server files had to be moved to a new dedicated server to facilitate the change in resources. That caused the extra downtime.

Update - 5/26/2012 We are in the progress of increasing the resources for Chicago 10, there will be a slight extended downtime while this change happens. Estimated time of outage is 30 minutes. We're sorry for the delay. EDIT: Looks like it's taking a bit longer to move than expected. May be down for 30 minutes more :( EDIT 2: Server move complete, server is in the process of doing chkdsk because of the size change. Instead of forcing it to stop, I'm going to let it finish.

THIS GUIDE IS OUT OF DATE. I NEED TO UPDATE IT FOR 1.7.0 AND ITS NEW HIVE. To clear up some of the posts on this category, I think we should work together as a community to make a reliable one stop shop topic for all server admin questions and references. Here we can cover anything from basic server admin commands to troubleshooting to performance tips. I'll frequently update the OP with shared information posted in this topic. So without further ado, let's get this ball rolling. Table Of Contents 1) Starting A DayZ Server 2) Server Configuration 3) Running a Beta Server 4) The Hive And You 5) Remote Administration 6) Tips From Fellow Admins 7) Other Notes 1) Starting a DayZ Server The majority of information on starting a DayZ server can be located in this topic: http://dayzmod.com/forum/showthread.php?tid=1429 If this is your first time hosting a server, I recommend that you become familiar with the Windows Server platform. It is important to be comfortable with creating user accounts, setting permissions, and managing a firewall. There is a nice article on Server 2008 security features here: http://technet.microsoft.com/en-us/library/dd548350(v=ws.10).aspx I also suggest that you find a nice reliable text editor like Notepad++ or Notepad2. This will make editing config files MUCH easier. Also, if you choose to have RDP access open, it's VERY IMPORTANT, and I mean VERY IMPORTANT you monitor your security logs. The second a windows machine comes up, you're guaranteed to be port scanned and eventually have a brute force attempt against your RDP login. Please make sure that only essential users have permissions set for remote desktop access (this can be configured in local policies). For a little bit of security through obscurity, change the RDP port (http://www.techrepublic.com/blog/datacenter/changing-the-rdp-listening-port-on-windows-server/1939). MAKE SURE TO IMPLEMENT A FIREWALL RULE FOR YOUR NEW RDP PORT BEFORE EDITING THE REGISTRY. If you do not, you can lock yourself access out of your box. If you do change your RDP port, there is no need to reboot the server, just restart the remote desktop service for it to take effect. Another great tool that I've been using so far is this script here: https://github.com/EvanAnderson/ts_block. It's been very handy in deterring multiple RDP connection attempts on my box. Keep in mind, this script runs silent in the background under the wscript.exe process. So after you configure it to your liking and run the .vbs file, you won't see any output. The best way I found to install ArmA is have your normal install directory and copy that to another location to use for DayZ. That way you have an untouched install that you can patch and revert back to if necessary. 2) Server Configuration Main Server Configuration (rcon password, server name, mission rotation, MOTD, etc.) This is broken down into two sections, for servers that use the DayZ monitor and those that do not. With The Monitor The bulk of your server settings can be found in your monitor directory. The file that you want to edit is named config.xml. Every value is easily identified with the XML tags and are pretty self explanatory. As of this edit, the monitor does not support the use of the beta server. I don't know if the server team agrees with this next statement, but I do suggest you change your rcon password to something secure that you can remember. The other configuration file you'll need to adjust is Arma2.cfg. This is generated in your configuration directory on first launch. This contains values for bandwidth and a few other available tweaks. Without The Monitor If you are not running the monitor, you'll have to make your edits in the server.cfg file. The community wiki has a good article on its values: http://community.bistudio.com/wiki/server.cfg The other configuration file you'll need to adjust is Arma2.cfg. This is generated in your configuration directory on first launch. This contains values for bandwidth and a few other available tweaks. Difficulty Settings You can alter the difficulty settings in the cfgdayz arma profile file. It should be located under %ARMADIRECTORY%\cfgdayz\Users\cfgdayz\cfgdayz.ArmA2OAProfile Just simply edit the flags under your set difficulty to your liking. The information on the flags are here: http://community.bistudio.com/wiki/server.armaprofile#Example_Configuration_File The example config has comments, which should clearly describe each setting. I recommend that if you turn most settings off, you should be using the Veteran or higher difficulty. It will be easier for users to understand your server doesn't have all the assists as a normal server does. I may break this down further on my next edit pass. 3) Running a Beta Server If you'd like to run a beta server, I'd suggest making two different directories, one that contains your normal install and one that contains a copy of your normal install. That way you always have something to fall back to later on (this isn't really required, because the beta installs as an expansion, but better safe than sorry) The arma patches are located here: http://www.arma2.com/beta-patch.php. Your beta files will be placed in %ARMA2PATH%\Expansion\beta during the install. You will also need the JayArma2Lib_new addon, as JayArma2Lib does not support the beta. I grabbed it from six updater and uploaded it to my server directory. Be sure to move dsound.dll out of your beta directory, or your server won't launch with JayArma2Lib_new defined. As of this writing you cannot use monitor to run the beta server. However, I do run it to update hive (I just point it to a bogus arma 2 directory in the config.xml, but leave the hive path correct. I close the monitor before it tries to launch the server after the update process is done. That way I can manually combine ban files and other things if need be.) There's an easier way, but I don't have the links to download the hive updates directly, so this is how I get by. You'll need to make a batch file with the following startup in your beta folder (you can make a shortcut of it later): aram2oaserver.exe -beta=Expansion\beta;Expansion\beta\Expansion -mod=@dayz;@CBA;@CBA_OA;@JayArma2Lib_new;Expansion\beta;Expansion\beta\Expansion Be sure to tack on any extra flags you use like -cfg and -config to ensure you're loading the correct config files. You can copy those from your old launch config for the normal server. Then just run your HiveAuth and Hive programs, and launch the server with the batch file. (This will need to be cleaned up a bit) 4) The Hive And You The hive is an essential part to the DayZ server. It manages all the character updates and authentications to the master server database. There are things you can look out for to ensure the hive is running correctly. Hive is stuck at waiting for client connection, even though server is running and players are on Chances are the serve hasn't been whitelisted or there is a configuration issue. In this case, contact the dev team. The DayZ live chat is a wonderful place to start. Hive is spamming database errors If this happens, you can try to restart the process to see if it resolves itself. You should not have to restart the ArmA server. If you are using the DayZ monitor, simply close out of the hive process that is having the issue and let the monitor relaunch it. If your hive is still getting errors, it's best to jump on IRC (DayZ live chat) and see if other server admins are having problems. There can be a chance it's the master server, and not on your end. 5) Remote Administration If you would like to manage your server remotely, there are a few Rcon tools out there that can help. I'll cover the two most popular ones here. BattlEye Rcon The following link has great information on the BattlEye Rcon: http://community.bistudio.com/wiki/BattlEye#RCon If you wish to talk to the entire server through the Rcon you can do so with this command #say 0 ArmA2 Rcon Gui https://dev-heaven.net/projects/rcon This is a very slick tool. It can be unstable at times, but it's real easy to use and it's a GUI interface. Plus it stores a local database on your computer of all users who connect to your server. Which makes it easy to retroactively ban people if you find evidence against them which violates your server rules. 6) Tips From Fellow Admins Freeborne suggest changing the default profile name

Chicago 10 runs on central time. It's veteran, but does require the beta patch.

May I be added to the forum group as well?

Thank you for the good words so far guys. I try to run a tight ship. Glad to hear experiences have been positive thus far.