=OSF= FR16 DayZ Server

icomrade · June 15, 2012 at 7:13 PM Official Post

We finally got a server up, it's running smooth now after a couple initial complications, the server is provided by TeabagPsc and is hosted in France for those who couldn't figure that out. At the moment it is running as UTC -5 (eastern time zone) which means it should be light when it is dark in Europe.

Admins (more may be added): Icomrade, TeabagPsc, NecessaryEvil

Server hardware:
10 GBit lan (not ever used) + 1Gbit wan connection (highest tested is 640Mbps down 60 up)
i7 920 quadcore @ 2.66 - 2.93GHz (turbo)
120GB SAS 10k or 15k RPM hdd (not sure which)
4GB Ram - not sure on speed

Current configuration:

Map marker = ON
Name tags = OFF
3rd person = ON
Crosshair = ON
Difficulty = Veteran
Timezone = UTC/GMT -5
Max ping = 250ms

If you have any suggestions for the server please make them as a reply to this thread. If you are an =OSF= member and you want administrator/RCON access please PM me.

K9shibby · June 18, 2012 at 8:18 PM

Server time zone to be in seattle not NY, thats about all i got

icomrade · June 18, 2012 at 8:57 PM Official Post

Quote from "K9shibby"

Server time zone to be in seattle not NY, thats about all i got

so.. you want the server timezone to be Seattle (UTC/GMT -8) instead of Eastern? That's pretty easy if everyone else wants it to be like that.

NecessaryEvil · June 18, 2012 at 9:01 PM Official Post

I will also vote for west coast time for now...but once we don't have nightvision our minds might change, so lets wait until then.

icomrade · June 19, 2012 at 7:29 PM Official Post

Set to UTC -8.

NecessaryEvil · August 4, 2012 at 8:16 PM Official Post

Thought I'd ask everyone how they felt about running two 40 slot servers rather than one 50 slot? It would be twice the amount of vehicles and 20% less players to stumble upon hiding spots during peak hours. And to the OSF DayZ fans, it would be 30 additional slots overall for the community. Not sure yet if Teabag's server can handle, but it's something to think about.

Ripley · August 4, 2012 at 8:22 PM

if that is technically possible I´d say give it a go

K9shibby · August 4, 2012 at 9:11 PM

already waiting for it to come online...

icomrade · August 4, 2012 at 9:32 PM Official Post

You'd also have to have to obtain another instance ID which is usually a long process that consists of mostly waiting. Of course, I would not be apposed to the idea so long as teabag's server can handle it. However, when the server is done with a 50 player day of hosting it usually gets around 7 fps which doesn't usually pick up until a restart where it holds @ 50 fps (the max) until about 20 players.

In addition to the performance issue I feel that 50 players is the optimal number for a DayZ game, it leaves just enough people to be able to not be noticed. Personally, I don't think that a lower slot server would help chances of our vehicles getting slotted, although this should have no affect of changing the settings of a public server, and non-OSF members should have an opportunity to chime in.

I have considered setting up an unofficial Lingor (or other map, maybe Fallujah ) server with a local/private database; this may or may not require another VM which may also be a problem.

NecessaryEvil · August 5, 2012 at 5:24 AM Official Post

The instance ID part is no problem, I already got another one when I tried to sign up for the server-related emails for server administrators. Actually, I filled out the form with the specifications of teabag's server and got an email saying the request was not approved because the uplink speed must be at least 100mbs so I re-did it but just said uplink speed is 100 because I was only interested in being added to the mailing list and not a new instance id, but they sent one anyways.

Hopefully fps won't be a problem if we restart the server at more frequent intervals like the recommended four per day. We can also run the servers with opposite times of day so peak hours are offset.

icomrade · August 5, 2012 at 12:07 PM Official Post

Actually, teabag's server has a 10Gbit Ethernet adapter but only a 1Gbps line/pipe, it's actually tested to be right around 200Mbps up and 300mbps down recently. I would still like to see at least one 50 player OSF server.

Ripley · August 19, 2012 at 2:18 PM

what do you guys think about letting the server restart 2 times a day instead of 1?
its getting pretty laggy when its not yet breakfast time in the US

icomrade · August 19, 2012 at 2:27 PM Official Post

Quote from "Ripley"

what do you guys think about letting the server restart 2 times a day instead of 1?
its getting pretty laggy when its not yet breakfast time in the US

Sure, the problem is the server is populated when it would be restarted. Unfortunately, it's a choice between server performance and popularity, come up with a good time and i'll set it up. FYI no matter how many times the server is restarted it will not perform well with over 200 zombies, dead or alive, on the map.

Ripley · August 19, 2012 at 3:28 PM

As soon as you restart it when its getting to laggy the server will be a lot more populated again.
I vote for 18:00 GMT+0 (right now it is set to about 10:00 GMT+0 I believe)

NecessaryEvil · August 19, 2012 at 11:45 PM Official Post

Adding a scheduled restart won't have an impact on server popularity as it crashes at least once per day as it is. DayZ recommends four restarts per day, but I think once every 12 hours might be enough.

eraser1 · August 20, 2012 at 1:00 PM

Quote from "Ripley"

As soon as you restart it when its getting to laggy the server will be a lot more populated again.
I vote for 18:00 GMT+0 (right now it is set to about 10:00 GMT+0 I believe)

I think it's 9:10 GMT+0 (cause it restarts at 4:10, central time GMT-5). And often, when a populated server restarts, regardless if it's crashed or planned, most of its players return when it's back up. I think 2 restarts a day is a good idea, each 12 hours apart (9:10 GMT+0 and 21:10).

icomrade · August 20, 2012 at 1:25 PM Official Post

It restarts at 02:10 GMT -8 AM, which is 10:10 AM UTC. Instead of doing a server restart every 12 hours it would be better to simulate an 6 hour restart I.e. have one right before everyone hops onto the server and one 6 hours later; the server won't restart after the second until another 12 hours.

NecessaryEvil · August 21, 2012 at 7:13 PM Official Post

I think it's time for the recommended 4 restarts per day. Every 6 hours after the current 2:10am restart should be fine with the standard warning messages ahead of time. If we really want to get carried away, we can warn when the next restart is coming each hour. I'll get started on the schedule and of course submit for approval before implementing any changes.

XML

<?xml version="1.0" ?> 
- <Scheduler>
- <!--  INTERNAL COMMANDS 
  --> 
- <job id="0">
  <time>01:50</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 10 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="1">
  <time>01:55</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 5 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="2">
  <time>01:59</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 1 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="3">
  <time>02:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>#shutdown</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="4">
  <time>03:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 5 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="5">
  <time>04:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 4 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="6">
  <time>05:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 3 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="7">
  <time>06:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 2 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="8">
  <time>07:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 1 hour</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="9">
  <time>07:50</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 10 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="10">
  <time>07:55</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 5 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="11">
  <time>07:59</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 1 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="12">
  <time>08:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>#shutdown</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="13">
  <time>09:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 5 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="14">
  <time>10:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 4 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="15">
  <time>11:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 3 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="16">
  <time>12:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 2 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="17">
  <time>13:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 1 hour</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="18">
  <time>13:50</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 10 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="19">
  <time>13:55</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 5 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="20">
  <time>13:59</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 1 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="21">
  <time>14:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>#shutdown</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="22">
  <time>15:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 5 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="23">
  <time>16:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 4 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="24">
  <time>17:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 3 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="25">
  <time>18:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 2 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="26">
  <time>19:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 1 hour</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="27">
  <time>19:50</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 10 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="28">
  <time>19:55</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 5 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="29">
  <time>19:59</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Server will Auto restart in 1 min</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="30">
  <time>20:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>#shutdown</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="31">
  <time>21:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 5 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="32">
  <time>22:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 4 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="33">
  <time>23:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 3 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="34">
  <time>00:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 2 hours</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <job id="35">
  <time>01:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>0</loop> 
  <cmd>say -1 Next scheduled restart in 1 hour</cmd> 
  <cmdtype>0</cmdtype> 
  </job>
- <!--  EXTERNAL COMMANDS 
  --> 
- <job id="36">
  <time>02:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>1</loop> 
  <cmd>C:\BEC\Config\restart_server.bat</cmd> 
  <cmdtype>1</cmdtype> 
  </job>
- <job id="37">
  <time>08:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>1</loop> 
  <cmd>C:\BEC\Config\restart_server.bat</cmd> 
  <cmdtype>1</cmdtype> 
  </job>
- <job id="38">
  <time>14:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>1</loop> 
  <cmd>C:\BEC\Config\restart_server.bat</cmd> 
  <cmdtype>1</cmdtype> 
  </job>
- <job id="39">
  <time>20:00</time> 
  <day>1,2,3,4,5,6,7</day> 
  <loop>1</loop> 
  <cmd>C:\BEC\Config\restart_server.bat</cmd> 
  <cmdtype>1</cmdtype> 
  </job>
  </Scheduler>

Display More

Hopefully I saved you some time commie but I'm not sure if the last part is right under external commands

icomrade · August 21, 2012 at 8:28 PM Official Post

New restart times implemented, same as evils post if they don't work out I will most likely change them. I may or may not give notice about it.

NecessaryEvil · August 21, 2012 at 8:39 PM Official Post

2:00, 8:00, 14:00, and 20:00 should be fine, and there shouldn't be any surprises with countdown messages each hour, plus the standard 10, 5, and 1 minute warnings.