BF3 server kicking everyone automatically

[//RS Maverick]

my BF3 server is kicking people after 5 minutes or so..... any ideas?

No hardcore mode or anything enabled. Only changed the player start count.

[kraze]

Are you running Procon or using any type of in game admins commands?

[//RS Maverick]

No ingame commands or procan used yet... I looked in my pb/sv_viol.log file and this is what I'm seeing. I believe it's punkbuster related as one person has updated there punkbuster directly through the website and they are the only ones not being kicked.

ideas?

[10.26.2011 23:00:13] VIOLATION (COMFAIL) #131: lif3r (slot #1) PB Client Not Responding [db6a22c7af452fd131a94aa8de92ffe9(-) 174.0.66.168:3659]
[10.26.2011 23:00:41] VIOLATION (COMFAIL) #131: rsmaverick (slot #2) PB Client Not Responding [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:00:45] VIOLATION (COMFAIL) #131: Blondie210 (slot #3) PB Client Not Responding [0d6422ee954fa71ebda1f684e15c330a(-) 68.147.159.130:3659]
[10.26.2011 23:01:01] VIOLATION (AUTO-UPDATE FAILURE) #141: lif3r (slot #1) This PB Server Requires (A1386 C2.279) - Error loading pbag [db6a22c7af452fd131a94aa8de92ffe9(-) 174.0.66.168:3659]
[10.26.2011 23:01:19] VIOLATION (AUTO-UPDATE FAILURE) #141: rsmaverick (slot #2) This PB Server Requires (A1386 C2.279) - Error loading pbag [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:01:43] VIOLATION (AUTO-UPDATE FAILURE) #141: Blondie210 (slot #3) This PB Server Requires (A1386 C2.279) - Error loading pbag [0d6422ee954fa71ebda1f684e15c330a(-) 68.147.159.130:3659]
[10.26.2011 23:03:36] VIOLATION (COMFAIL) #131: Garrigansaddler (slot #1) PB Client Not Responding [656d4a8c3bfbd28bf7408e014fe1be6c(-) 71.68.214.226:3659]
[10.26.2011 23:04:04] VIOLATION (COMFAIL) #131: lif3r (slot #2) PB Client Not Responding [db6a22c7af452fd131a94aa8de92ffe9(-) 174.0.66.168:3659]
[10.26.2011 23:04:24] VIOLATION (AUTO-UPDATE FAILURE) #141: Garrigansaddler (slot #1) This PB Server Requires (A1386 C2.279) - Error loading pbag [656d4a8c3bfbd28bf7408e014fe1be6c(-) 71.68.214.226:3659]
[10.26.2011 23:04:43] VIOLATION (AUTO-UPDATE FAILURE) #141: lif3r (slot #2) This PB Server Requires (A1386 C2.279) - Error loading pbag [db6a22c7af452fd131a94aa8de92ffe9(-) 174.0.66.168:3659]
[10.26.2011 23:11:37] VIOLATION (COMFAIL) #131: rsmaverick (slot #1) PB Client Not Responding [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:12:35] VIOLATION (AUTO-UPDATE FAILURE) #141: rsmaverick (slot #1) This PB Server Requires (A1386 C2.279) - Error loading pbag [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:18:53] VIOLATION (COMFAIL) #131: rsmaverick (slot #1) PB Client Not Responding [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:19:41] VIOLATION (AUTO-UPDATE FAILURE) #141: rsmaverick (slot #1) This PB Server Requires (A1386 C2.279) - Error loading pbag [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:20:36] VIOLATION (COMFAIL) #131: wQQter (slot #2) PB Client Not Responding [c172aaffb2be704166cfd085ae0515ba(-) 174.253.139.89:5445]
[10.26.2011 23:21:24] VIOLATION (AUTO-UPDATE FAILURE) #141: wQQter (slot #2) This PB Server Requires (A1386 C2.279) - Error loading pbag [c172aaffb2be704166cfd085ae0515ba(-) 174.253.139.89:5445]
[10.26.2011 23:21:35] VIOLATION (COMFAIL) #131: lif3r (slot #3) PB Client Not Responding [db6a22c7af452fd131a94aa8de92ffe9(-) 174.0.66.168:3659]
[10.26.2011 23:22:04] VIOLATION (COMFAIL) #131: Blondie210 (slot #4) PB Client Not Responding [0d6422ee954fa71ebda1f684e15c330a(-) 68.147.159.130:3659]
[10.26.2011 23:22:33] VIOLATION (AUTO-UPDATE FAILURE) #141: lif3r (slot #3) This PB Server Requires (A1386 C2.279) - Error loading pbag [db6a22c7af452fd131a94aa8de92ffe9(-) 174.0.66.168:3659]
[10.26.2011 23:26:18] VIOLATION (COMFAIL) #131: rsmaverick (slot #1) PB Client Not Responding [d40bbe46c5b9e4e8ccc1dec114d6e920(-) 68.147.233.208:3659]
[10.26.2011 23:26:45] VIOLATION (COMFAIL) #131: lif3r (slot #2)

[kraze]

Have all clients or clan members run pbsetup and update there PB. We have found this helps in many cases!

[//RS Maverick]

Okay! Any idea why this is happening on this server and not others? Most likely will prevent us from getting any new joiners?

[kraze]

It really depends. PB has never been *stable*. Some servers will have this issues while others will not. I have been unable to determine why this is. Your best bet is to just have your clan members update there PB then you can issue this command to the server via the server control tab;

punkBuster.pb_sv_command PB_SV_Update

This will update the servers PB.

http://www.nfoservers.com/forums/viewto ... =70&t=5911

[//RS Maverick]

Sounds good. Just executed the command. Does it need to restart or switch maps to take effect?

[dapriest]

A new version of punkbuster was released and auto update on clients isn't working hence why they're kicked.

[kraze]

The server shouldn't need a restart,no.

[//RS Maverick]

Any idea why other servers are able to handle players with older clients?

Also.... what are the rcon commands to change level within the control panel? I'm trying the referenced commands but nothing works.

[kraze]

I am not sure of the full command list, but Dice said it is still a work in progress and and it will cause server crashes, if you use it. I would suggest enabling our admin daemon, you can do this via the easy set up tab.

Command list for our admin daemon;
http://www.nfoservers.com/forums/viewto ... =70&t=5933

[Edge100x]

Older servers (R4 and below) run an older version of PB, so even most servers here don't require the new one for clients. New servers (R5) do, so clients that do not properly auto-update will have problems with newer ones here and anywhere else that runs it. We are currently investigating possible workarounds for this and asking DICE if there is a fix on the way to force clients to update properly.

[//RS Maverick]

Thanks for the explanation on this! Is there anyway to disable punkbuster and keep it ranked?

[Grifter]

Having the same issue and it's really frustrating. I was so excited to see our server start getting action right away, and then horrified when everyone (including myself) started getting kicked repeatedly.

There are multiple posts about this on a competitor's website, and it seems they have released a patch for their servers. Any chance we'll see one here too? Or is there a way to roll-back to the version of PB that BF3 is using right now?

[Edge100x]

The other RSP's "patch" would have been to either disable PB or switch back to the old version. DICE has told RSPs not to do these things.

The best fix is to have clients update their PB using pbsetup.