Due to the number of fixes in the most recent (R12) BF4 dedicated server release, we are deploying it immediately. We expect most servers to be deployed within 2 minutes.
All servers on hosts other than ga0306 and ga0406 are now updated and running. A few remaining servers on those hosts will continue to restart for the next minute or two.
does it fix the resource issues?
none of my servers appear to be registered with battlelog? .... although control panel says they are running (with an extremely small amount of memory - 79MB)
actually... they are all reporting this message:
This server has failed to start several times in a row, indicating a problem with the server. View this servers Failure Reports for more information.
I've found some servers that are crashing on startup. I'm not certain why, they all are showing the same error in the log files. I've sought advice from DICE.
The error in the log file seems to indicate that it could be to do with the maplist - if you want, you could change the maplist for your server and restart it to see if it comes up. No guarantees though, and I expect to have an answer from DICE tomorrow morning our time.
Found the issue with assistance from DICE. It should only affect customers who have edited their startup.txt file, which is why 99% of servers came up properly. I'll poke at whatever servers I can with a temporary fix.
i reverted the startup.txt file - seems to have come up now. Something must not have been compatible...
Right after this update was applied our server became quite laggy. Also changing the running map via procon came very close to crashing the server. When I used procon to load a different map the screen went black for everyone for four or five minutes before the server started loading the map.
I'll watch how it performs tonight and let you know.
I swear to god it feels like every fix Dice applies makes things worse lately.
I saw a few servers start late last night that seemed to be spammed by Procon - the entire maplist appeared to be being overwritten every second.
I'll take more of a poke at it today.
Yeah we got a full round in on the r12 patch then it crashed on the next map load. Also for some stupid reason it changes our player count too 2 players after a crash? i have checked the server back end and it shows 64 player but in procon after a crash and reset it sets it to 2 players
The issue I talk about above (now I've had the OK from DICE to be specific) is that if you "get" the factionoverride cvars during boot (in startup.txt) the server will crash. A "get" is when you call the variable without any value, which a few people had in their config files because its something that procon wrote by default. While I do stress that we really prefer you use the default config files and use the configuration page if at all possible, the server shouldn't be crashing in situations like this and DICE have confirmed it'll be fixed in the next release.
I want to just again give DICE some Kudos; after midnight last night our time I was dealing with this issue for our customers, and DICE had two senior programmers helping me - with the error report from me it took them about 2 minutes to find the problem and give me the workaround.