BF3 server crash after R11 update.

[chemist]

I feel like I'm beating a dead horse here - and I know that this is outside of NFO's realm, but never the less, it is rather annoying. Since R11 has been released, my 64 slot BF3 server has frequently dropped all connected players. This essentially kills the traffic that I work very hard to get. As I am in the process of kick starting a new gaming community, I need all the players that I can get, so it is a bummer to look at the usage log and see this:


Luckily in the first crash - I was able to quickly recover, but that is not normal. Sometimes it takes a few days before I can get back to a full server.

Within 24 hours time, my server dropped all 64 connected players. Here is an example of the log file generated at the time of the dump:

Code: Select all

[12.11.2011 17:45:48] Lost Connection (slot #7) 67.168.171.37:3659 42bb3d37f68671141c6c8176d16cede1(-) Islandbuzz
[12.11.2011 17:46:16] Lost Connection (slot #22) 95.160.46.201:3659 f902584617f980f8d5e19cd977211733(-) Elioths
[12.11.2011 17:46:37] New Connection (slot #7) 70.82.121.106:3659 [?] "MrAbracks" (seq 12078605)
[12.11.2011 17:46:37] Player GUID Computed 16bca69f56d390891be67db0b207f082(-) (slot #7) 70.82.121.106:3659 MrAbracks
[12.11.2011 17:46:47] New Connection (slot #22) 108.28.240.32:3659 [?] "woowoo11" (seq 12727453)
[12.11.2011 17:46:47] Player GUID Computed f85d2f6a797d4bb06bafbab11c456f1f(-) (slot #22) 108.28.240.32:3659 woowoo11
[12.11.2011 17:47:39] Lost Connection (slot #29) 68.205.51.25:3659 978272ab8642849f67bb9f895c5e2c4d(-) FixX08
[12.11.2011 17:48:34] Lost Connection (slot #25) 98.183.227.209:3659 953910776f67c1ad61b9763e1e9aed61(-) htwalden
[12.11.2011 17:48:38] Lost Connection (slot #61) 142.179.60.201:3659 14904882023ccfb137f67b8fd8479837(-) Spectrezi
[12.11.2011 17:48:39] Lost Connection (slot #26) 99.28.173.4:3659 38ec6e6c6679e55f8cff484ee89c9339(-) countertesl
[12.11.2011 17:48:40] Lost Connection (slot #20) 74.76.129.61:3659 505b3a4045496f50c30338061f4ee6f4(-) Jeffpm
[12.11.2011 17:48:40] Lost Connection (slot #28) 173.74.204.213:3659 b506e9c6788827115b957423213be3fd(-) 19jealous79
[12.11.2011 17:48:49] Lost Connection (slot #38) 67.172.209.149:3659 bbc6631479c86a03a208942f08a3fcb0(-) SeoulTemplar
[12.11.2011 17:48:49] Lost Connection (slot #24) 76.105.77.163:3659 9e70057f55b1779f8272c5e0b5aa0c77(-) Happymrsnowman
[12.11.2011 17:48:51] Lost Connection (slot #41) 99.27.149.101:3659 59f6cc7ac78bc55cefb6d4289bb9966c(-) w00dballs
[12.11.2011 17:48:51] [From #7 f082(-) MrAbracks] My dx C:\Windows\system32\d3d9.dll size=1826816 md5=7459301D21C2E21468823F73042D9F87
[12.11.2011 17:48:53] Lost Connection (slot #21) 50.35.181.208:3659 80d86337cb68601c1d2fd4144ad2d77f(-) Team_VroomShad
[12.11.2011 17:48:58] Lost Connection (slot #19) 71.231.170.236:3659 b08c3b341759693e283bd76e8cc9fc69(-) Batpimp
[12.11.2011 17:48:58] Lost Connection (slot #11) 99.89.14.17:3659 0df75a84de15fd7d3ed5e70e44a0cdd4(-) enchanterDown
[12.11.2011 17:48:59] Lost Connection (slot #33) 142.167.251.138:3659 5e7f3a1476ebacffca4f7a5dc9b86a3e(-) Maverickxthree
[12.11.2011 17:49:01] [From #22 6f1f(-) woowoo11] My dx C:\Windows\system32\d3d9.dll size=1828352 md5=6EF5F3F18413C367195F06E503AB86A6
[12.11.2011 17:49:07] Lost Connection (slot #22) 108.28.240.32:3659 f85d2f6a797d4bb06bafbab11c456f1f(-) woowoo11
[12.11.2011 17:49:11] Lost Connection (slot #35) 142.167.247.145:3659 f4a795857c77f591c107c20fa40a93da(-) thebert338

It only happens on ConquestLarge, and when the server is near full or at 64/64.
bfmidwest.game.nfoservers.com:25200

Is anyone else experiencing this problem? If so - What have you tried to avoid this from happening?

Again, I understand that this is not NFO's issue. I also understand that this is still considered a "new" game and may have a few bugs, however I have other friends that also host 64 person conquest64 servers, and have not had this issue.

Any help is appreciated.
Cheers,
Chem

[TimeX]

Others have been reporting the problem as well, and it seems to be more specific to servers with 64 players in them and running high ticket counts. Reducing ticket counts or player slots a bit should help.

[IcEWoLF]

I've noticed more often crashes with Metro and Bazaar with 64 players.
That's because some of the kits were not disappearing.

[.=QUACK=.Major.Pain]

We have the same thing 3-6 times a day since the latest update on 32 slots server, but today we haven't had any. Odd.

[Sorry]

We ran for 24 hours. Our best run since increasing to 64slots. Battlelog dumped our players today about 1500 texas time to end it. Hoping EA gets this fixed.

[chemist]

TimeX, thanks for that suggestion. I will take it into consideration, and reduce my tickets to the default 100% vs. the 175% that I was operating at.

Icewolf, have you noticed the dump on other maps? My server only runs flight capable maps.

Thanks.

[BeardedBubba]

TimeX, thanks for that suggestion. I will take it into consideration, and reduce my tickets to the default 100% vs. the 175% that I was operating at.

Icewolf, have you noticed the dump on other maps? My server only runs flight capable maps.

Thanks.

Had same issue on ours on metro, as well as GB and Caspian.

I also had a crash today on Karg, but that may or may not have been related to this situation. Server was full @ 64, and was at 325% tickets.

[IcEWoLF]

TimeX, thanks for that suggestion. I will take it into consideration, and reduce my tickets to the default 100% vs. the 175% that I was operating at.

Icewolf, have you noticed the dump on other maps? My server only runs flight capable maps.

Thanks.

Hi there, I've mainly had big dump issues with Bazaar mainly.

I removed it for now until the next patch which supposedly they will fix the kit issues that John earlier on mentioned.

[Edge100x]

There are still many crash bugs in the server, but the most common seems to relate to kits and happens on high-player-count, high-ticket-count servers, as TimeX and IcEWoLF suggested. DICE has posted that this bug should be fixed in R12, to be released on Tuesday.

[globel]

There are still many crash bugs in the server, but the most common seems to relate to kits and happens on high-player-count, high-ticket-count servers, as TimeX and IcEWoLF suggested. DICE has posted that this bug should be fixed in R12, to be released on Tuesday.

it happens more often on high ticket maps because there more popular (because people like playing on these more). Empty servers don't crash typically.

[Edge100x]

I wouldn't say that it's just about popularity, globel. The bug is that kits aren't cleaned up for 10+ minutes. A higher maximum player count means that more can be on the map at a time, and a longer round (from having more tickets) means that there's a longer window for when the problem can occur.

It is true that higher ticket counts seem to attract and retain players; I don't see many busy servers with the standard number of tickets. I think a big part of that is because players often quit between rounds, and longer rounds means that the server can ramp up to being full much more easily. This is why I recommend high ticket counts in the KB article on server popularity.

[chemist]

R14, ConquestLarge, 64 Players (full), Default 100% tickets, all B2K maps.

Still crashes. I guess this is just something we should all get use to.

I've lowered my player count to 60, but who knows how long it will be until I can fill it. I'll let you know my findings when that happens.

[wyseguy79]

Were running a 48 man Wake server and it has crashed close to 4 times today. Generally after about 30 min of being full for 48. We get the same log file of just seeing all the connections kicked as shown in the example by other members.

I was really hoping they would have fixed it this time, but I guess there still on the wild goose chase of at DICE.

[Edge100x]

There was one widespread problem with Blaze a little before 7pm PST, and several smaller problems throughout the day, and these have also caused many player dumps and crashes. I imagine that EA is having some problems keeping up with people buying B2K and using the adjusted browser.

[.=QUACK=.Major.Pain]

There were also problems with the Origin Store last night too. Talking to a couple people who tried to purchase them game, who said all they got was an error when trying to pay.

Must have been putting in overtime to repair Origin and Battlelog.