Server Crashing Thread

[TimSad]

Well, I don't see any other thread like this so I thought I'd make this here to help us keep track of crashing until it is completely fixed. Report server crashing and client dumping/crashing alike here and state the server version you are currently on.

(10/27/2011) My server is now running R5 and it still seems to crash during loading the next map.

[Edge100x]

I've forwarded a couple more of those mapchange crashes to DICE today.

[TimSad]

We just got up to 20 players on Noshahar Canals after that last crash and the next map to be loaded was Caspian and crashed on map load. The server wasn't even up for 1.5 hours and it crashed again. In case you want to see my server settings if they are relevant, I'll post them here.

Code: Select all

# This file is to be editable by the server administrator.
# It can contain any remote administration commands that are to be run during game server startup.
vars.idleTimeout 0
vars.idleBanRounds 0
vars.vehicleSpawnAllowed true
vars.3dSpotting true
vars.miniMap true
vars.miniMapSpotting true
vars.killCam true
vars.autoBalance true
vars.3pCam true
vars.regenerateHealth true
vars.onlySquadLeaderSpawn false
vars.nameTag true
vars.hud true
vars.teamKillCountForKick 6
vars.teamKillValueForKick 4100
vars.teamKillValueIncrease 1000
vars.teamKillValueDecreasePerSecond 50
vars.gamePassword ""
vars.autoBalance true
vars.crossHair true
vars.vehicleSpawnDelay 100
vars.soldierHealth 100
vars.playerRespawnTime 100
vars.playerManDownTime 100
vars.bulletDamage 100

vars.serverName "[-SoC-] 24/7 CONQUEST! - LA"
vars.bannerUrl "soldiersofchaosgaming.com/images/socBanner.dds"
vars.roundStartPlayerCount 8
vars.roundRestartPlayerCount 4
vars.maxPlayers 64
vars.friendlyFire false

[jasonelmore]

Same here, Getting map change crash's. The other crash bug that was happening during mid match has seemed to have been fixed.

In the morning, i'm disabling the NFO Daemon, and the Map Changer, and i'm gonna run full stock.

If any of you are running completely stock without any daemon's or admin tools (procon, BF3CC, NFO Daemon) that manage your server rotation, and you have still gotten the map change crash. Please let us know.

[dapriest]

I have the R4's running NFO's map changer and the R5's running the map changer and haven't had any crashes. I also haven't dished out admin or used in-game admin.

[zaNe]

Server was running great for basically the whole day, then around 9:15pm PST it crashed, had about 55/64 players in the server.

Server wouldn't restart after about 15 minutes so I had to open a support ticket to get her back up again. Map was Seine Crossing. Crashed on Map change.

[TimSad]

Okay, I tested it @ 42 players playing Conquest Small and it ran for 4 maps (1 round rotations) at a full 42 but then crashed at the next map load! I almost thought I had something going for a while.

I'm getting reports that some server providers are not crashing at all (aside from the ones that I'm keeping my eye on) with 64 player Conquest servers. Do we know what's up with that?

[IcEWoLF]

My 64 player today crashed few times (full)
the 32 slot servers do well..

Hopefully EA will be able to address these issues (most) in R6.
R5 is not much of an upgrade.

[jasonelmore]

My 64 player today crashed few times (full)
the 32 slot servers do well..

Hopefully EA will be able to address these issues (most) in R6.
R5 is not much of an upgrade.

Are you using the NFO Map Cycler or Procon to handle map rotation?

[GitSum]

This is from our server usage graph and roughly shows 24 hours - 5 am Thurs to 5 am Fri

You can see we had about 6 crashes during that time frame, but we were able to stay on top of things and get the server repopulated until it died out in the wee hours. Current with r5, we were using Procon but I just disabled it to see if things will improve

Settings are for Hardcore with quick match, using NFO map changer (by the slot server)

usage.jpg (48.58 KiB) Viewed 8297 times

[Edge100x]

We've seen many mapchange crashes both with and without the NFO mapcycler, unfortunately. They're quite common.

I also saw a couple of crashes this morning for other reasons -- one was due to the way the game handled the Blaze back-end, and one was a seemingly random one in the middle of gameplay.

[TimSad]

A guy in our clan that plays on our server as well as another server with another group he plays with told me that they told him they hardly crash at all. He also said they were hosted by you guys, NFO, in San Jose. Their IP is 66.151.138.95.

These guys play Rush so I decided to try my server on Rush and apparently it got full this morning according to GT but then while I was idling I got disconnected so I guess it crashed. I'm not so sure why these guys' server would be able to stay up longer than ours.

I'll try to get my server full again on 32 Rush just to be sure.

[Edge100x]

Some servers randomly do stay up while others crash more. We haven't been able to pin down why yet on our end, but DICE should be able to fix these from the dumps.

[TimSad]

Wow, okay! Now that I've changed it to Rush 32 players, it has been up for 5 hours now without crashing. That is not to mention that 5 hours ago, when I joined to start it up, it filled fast which leads me to believe that Quickmatch actually worked for me for once.

So, it seems that the problem lies with Conquest and a larger amount of players.

[TimSad]

Wow, okay! Now that I've changed it to Rush 32 players, it has been up for 5 hours now without crashing. That is not to mention that 5 hours ago, when I joined to start it up, it filled fast which leads me to believe that Quickmatch actually worked for me for once.

So, it seems that the problem lies with Conquest and a larger amount of players.

EDIT: Rush just had a very good run without crashes! It was up for 8 hours without crashing.