Advanced In-Game Admin and Ban Enforcer - AdKats

[ImportBot]

Originally Posted by www-battleplay4u-com*:

 

for all who have the "[AdKats] WARNING: Issue connecting to battlelog." problem:

 

it looks like this issue happens as soon as there are more than 3 instances of either hacker-checker-LIVE or Adkats LRT are running on the same IP. That's why hosting on procon layers with many others isn't really an option anymore... Think about using your owns server for hosting procon and, if you got more than one layer, think about using dynamic IPs so they won't be blocked too fast.

 

Anyways, there will be most likely some delay in LRT, you can see this by using debug level > 3 if any players are queued

 

I hope I could help some of you guys.

[ImportBot]

Originally Posted by Hodor*:

 

Morning 7:00 UTC, one player at my server - just me! Procon has been rebooted 5 minutes ago, at 6:55 and i got an error ahahah

 

Code:

[08:53:26 95] [Insane Limits] Thread(fetch): DONE inserting 0 new players, 0 still in queue, took a total of 22 secs
[08:53:41 50] [AdKatsLRT] WARNING: Issue connecting to battlelog.
[08:53:50 05] [Insane Limits] Thread(fetch): DONE inserting 0 new players, 0 still in queue, took a total of 22 secs
[08:54:11 60] [Insane Limits] Thread(fetch): DONE inserting 0 new players, 0 still in queue, took a total of 22 secs
[08:54:33 15] [Insane Limits] Thread(fetch): DONE inserting 1 new players, 0 still in queue, took a total of 20 secs
[08:54:52 32] [AdKatsLRT] WARNING: Issue connecting to battlelog.
[08:55:33 09] [AdKatsLRT] WARNING: [Some player] took abnormally long to start processing. [32s]
[08:55:39 98] [AdKats] SQL updates fetched.

[ImportBot]

Originally Posted by Chelrid*:

 

Reboot your layer.

Did not works.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Morning 7:00 UTC, one player at my server - just me! Procon has been rebooted 5 minutes ago, at 6:55 and i got an error ahahah

 

Code:

[08:53:26 95] [Insane Limits] Thread(fetch): DONE inserting 0 new players, 0 still in queue, took a total of 22 secs
[08:53:41 50] [AdKatsLRT] WARNING: Issue connecting to battlelog.
[08:53:50 05] [Insane Limits] Thread(fetch): DONE inserting 0 new players, 0 still in queue, took a total of 22 secs
[08:54:11 60] [Insane Limits] Thread(fetch): DONE inserting 0 new players, 0 still in queue, took a total of 22 secs
[08:54:33 15] [Insane Limits] Thread(fetch): DONE inserting 1 new players, 0 still in queue, took a total of 20 secs
[08:54:52 32] [AdKatsLRT] WARNING: Issue connecting to battlelog.
[08:55:33 09] [AdKatsLRT] WARNING: [Some player] took abnormally long to start processing. [32s]
[08:55:39 98] [AdKats] SQL updates fetched.

In other words it's not your layer causing the issue, it's someone else on the same IP as you.

[ImportBot]

Originally Posted by kcuestag*:

 

Update!

 

I am back at GPortal with Procon, before I kept getting Battlelog connection errors every 1-3 minutes. I decided to remove Insane Limits and give it a try, I've not gotten any error since then!

 

Weird thing is, I was only using Insane Limits for !nextmap command and for reserved slots to those who helped us fill our server, not a huge load I think.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Update!

 

I am back at GPortal with Procon, before I kept getting Battlelog connection errors every 1-3 minutes. I decided to remove Insane Limits and give it a try, I've not gotten any error since then!

 

Weird thing is, I was only using Insane Limits for !nextmap command and for reserved slots to those who helped us fill our server, not a huge load I think.

The only way to find the issue here is over longer periods of time. Battlelog does not ban immediately for going over their limit, it's an average over time, at least that's what it has appeared to be. Leave this setup going and see if that works for you.

[ImportBot]

Originally Posted by iraqiboy90*:

 

Hi

 

Questions:

 

How come that Adkats knows that a player changed his name even though he didnt try to join our servers...?

I have confirmed that this player did not join our servers by checking pb logs, event logs, plugin logs, and even metabans doesnt know about the name changes yet.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hi

 

Questions:

 

How come that Adkats knows that a player changed his name even though he didnt try to join our servers...?

I have confirmed that this player did not join our servers by checking pb logs, event logs, plugin logs, and even metabans doesnt know about the name changes yet.

It's nothing special, when a player joins it checks their current name vs the name stored in the database and if it's different it logs the record and updates their name.

 

Don't know what to say other than your other detection of players joining is missing something?

[ImportBot]

Originally Posted by CEBEP78*:

 

Hello

[20:39:44 10] [AdKatsLRT] WARNING: Issue connecting to battlelog.

[20:40:59 42] [AdKats] WARNING: Issue connecting to battlelog.

 

All the time writes so

 

AdKats - 6.8.0.78

[ImportBot]

Originally Posted by spatieman*:

 

Colcol.

2 questions.

how can i remove "admin" users..

we are cleaning up inactive admins, but i cant see how to remove a user from the admin list.

 

and how can i prioritize admins that what to join on a full server without waiting till some1 leaves

[ImportBot]

Originally Posted by www-battleplay4u-com*:

 

Hello

[20:39:44 10] [AdKatsLRT] WARNING: Issue connecting to battlelog.

[20:40:59 42] [AdKats] WARNING: Issue connecting to battlelog.

 

All the time writes so

 

AdKats - 6.8.0.78

The IP of your layer might be (time)banned on battlelog. Try hosting the layer on another IP or wait till it is unbanned again, but LRT won't work in that time as it should.

[ImportBot]

Originally Posted by CEBEP78*:

 

The IP of your layer might be (time)banned on battlelog. Try hosting the layer on another IP or wait till it is unbanned again, but LRT won't work in that time as it should.

I understood. Thank you for advice.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Hello

[20:39:44 10] [AdKatsLRT] WARNING: Issue connecting to battlelog.

[20:40:59 42] [AdKats] WARNING: Issue connecting to battlelog.

 

All the time writes so

 

AdKats - 6.8.0.78

There are a few things that can help you here.

 

Getting your layer on a separate IP that won't be banned for going over the limit battlelog puts in.

 

Turning off the LIVE system in the hacker-checker for AdKats. This will greatly reduce the number of requests from your layer, but make the hacker-checker systems less powerful.

 

Turning off high request volume on your LRT instance. This will greatly reduce the number of requests from your layer, but some players will be able to work around the loadout checks if they learn how it works.

[ImportBot]

Originally Posted by iraqiboy90*:

 

It's nothing special, when a player joins it checks their current name vs the name stored in the database and if it's different it logs the record and updates their name.

 

Don't know what to say other than your other detection of players joining is missing something?

So a guy gets banned with name X1. He joins again with same name several times and the ban gets enforced and it shows up on the list on the Admin panel.

He changes names. We noticed the name change after a refresh of his Battlelog profile few minutes later. His name is now X2.

We refresh the panel and it shows the name change on the pie graph. Also by looking into the name change detection timestamps on the database.

He changes his name again to X3 and it shows up on the panel.

 

What was weird that on the panel, it didn't show that the ban was getting enforced after each name change. So I went into the database and looked into his soldier ID, and on the Main Records there was no lines of the ban getting enforced after the name changes.

So i checked the logs, all of them. Procon Event logs showed no attempt of joining with names X1, X2 and X3. Checked with the Punkbuster logs to check if X1 X2 or X3 joined, nothing. Checked again with the IP address, nothing. Checked again with the PB guid, nothing. Checked again with a proxy IP he used to register a fake website account with, nothing. Also checked the console logs, searching X1 X2 X3 and also the EA guid. Also checked with bf3stats.com on the Reports page. It shows up empty rounds of him attempting to play on the server, before the name change and after the ban.

Also, there is no "[AdKats] player_changename update for XXX by AdKats SUCCESSFUL!" on the plugin log with any of his names.

 

Result: No attempt of join after each name change.

 

The only explanation would be as if Adkats or the admin panel actually checks Battlelog regularly somehow to see if there was a name change, WITHOUT any join attempt...

[ImportBot]

Originally Posted by Hodor*:

 

After a very frequent blocking of battlelog I decided to make my own Procon Layer (before that it was G-Portal). I found a cloud for $5 a month and set procon layer on Linux Ubuntu 14.04 and now I get an error

Code:

[AdKats] EXCEPTION-68078-D-FetchPlayerStatInformation-HackerChecker111: [Error while parsing player stats data.][System.NullReferenceException: Object reference not set to an instance of an object
  at PRoConEvents.AdKats.FetchPlayerStatInformation (PRoConEvents.AdKatsPlayer aPlayer) [0x00000] in <filename unknown>:0 ]

I know that Procon created for Windows, but it works fine for Linux too. disappointing only that the normal work of the plugin on Linux depends on the plug-in developer

[ImportBot]

Originally Posted by iraqiboy90*:

 

Turning off the LIVE system in the hacker-checker for AdKats. This will greatly reduce the number of requests from your layer, but make the hacker-checker systems less powerful.

How do I do this

 

I'm getting the errors now

[ImportBot]

Originally Posted by Hodor*:

 

How do I do this

 

I'm getting the errors now

/pupdate in-game command and after you need look to A18 section

 

This function for 6.8.0.78 version

[ImportBot]

Originally Posted by iraqiboy90*:

 

/pupdate in-game command and after you need look to A18 section

 

This function for 6.8.0.78 version

ah then.

I rather stay on 6.8.0.0 than going for the test build.... I dont want my local code force reset on every forced update, I have some modifications in there...

 

The errors stopped anyways... I'm using Battlelog Cache so this might have helped.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

ah then.

I rather stay on 6.8.0.0 than going for the test build.... I dont want my local code force reset on every forced update, I have some modifications in there...

 

The errors stopped anyways... I'm using Battlelog Cache so this might have helped.

6.8.0.0 has the high frequency code built in, it's part of the LIVE system. If it's not a consistent issue i would not suggest turning it off.

 

If you are using modded code anyway and don't want it wiped when on a test version just put a return statement at the start of the CheckForPluginUpdates function so none of the update stuff runs.

[ImportBot]

Originally Posted by Hodor*:

 

@ColColonCleaner How to fix it? myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry41072

[ImportBot]

Originally Posted by wdfstryfe*:

 

[14:15:20 43] [AdKats] Warning. PlayerListing thread processing completed in 1109ms

[14:15:22 18] [AdKats] Warning. PlayerListing thread processing completed in 1156ms

[14:15:30 84] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:41 22] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:48 15] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:51 72] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:53 15] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[Prophet731]

Originally Posted by Prophet731*:

 

So a guy gets banned with name X1. He joins again with same name several times and the ban gets enforced and it shows up on the list on the Admin panel.

He changes names. We noticed the name change after a refresh of his Battlelog profile few minutes later. His name is now X2.

We refresh the panel and it shows the name change on the pie graph. Also by looking into the name change detection timestamps on the database.

He changes his name again to X3 and it shows up on the panel.

 

What was weird that on the panel, it didn't show that the ban was getting enforced after each name change. So I went into the database and looked into his soldier ID, and on the Main Records there was no lines of the ban getting enforced after the name changes.

So i checked the logs, all of them. Procon Event logs showed no attempt of joining with names X1, X2 and X3. Checked with the Punkbuster logs to check if X1 X2 or X3 joined, nothing. Checked again with the IP address, nothing. Checked again with the PB guid, nothing. Checked again with a proxy IP he used to register a fake website account with, nothing. Also checked the console logs, searching X1 X2 X3 and also the EA guid. Also checked with bf3stats.com on the Reports page. It shows up empty rounds of him attempting to play on the server, before the name change and after the ban.

Also, there is no "[AdKats] player_changename update for XXX by AdKats SUCCESSFUL!" on the plugin log with any of his names.

 

Result: No attempt of join after each name change.

 

The only explanation would be as if Adkats or the admin panel actually checks Battlelog regularly somehow to see if there was a name change, WITHOUT any join attempt...

The BFACP will check battlelog for name changes and update them as well. Once you check a player the first time it stores their battlelog id into the DB if it finds them on battlelog.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Thank you!

This post to remind myself to add this tonight.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

[14:15:20 43] [AdKats] Warning. PlayerListing thread processing completed in 1109ms

[14:15:22 18] [AdKats] Warning. PlayerListing thread processing completed in 1156ms

[14:15:30 84] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:41 22] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:48 15] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:51 72] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

[14:15:53 15] [AdKats] Warning. PlayerListing thread processing completed in 1015ms

I should increase the timer on that thread for warnings. In the meantime don't run such a high debug level. 1 second is normal.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

@ColColonCleaner How to fix it? myrcon.net/...advanced-in-game-admin-and-ban-enforcer-adkats#entry41072

I've explained this in previous posts. I should add it to the Docs. It's difficult for me to test on Linux for all features and thus do not directly support it for all features. There are too many to go through for blanket testing.

 

Most of the errors you will see are issues connecting over https, which for some reason the plugin does not like on that OS. Get me line numbers by enabling plugin debugging on that layer and we can move from there.

 

I'm sure it is disappointing that a plugin nearly half the size of procon itself doesn't magically work on a different operating system, but i believe it was you who coined the phrase "I do not care about the tears of Wipe.", so be careful with your wording and demands.

[ImportBot]

Originally Posted by QuadPrime*:

 

Colcol.

2 questions.

how can i remove "admin" users..

we are cleaning up inactive admins, but i cant see how to remove a user from the admin list.

 

and how can i prioritize admins that what to join on a full server without waiting till some1 leaves

Set their Role to Guest, set a date to let them expire by time, or type "delete" in the significant field for that, in your roles tab.

 

Also, activate "agressive joining" in your server startup.txt, and put make your admins are assigned to a reserved slot.

[ColColonCleaner]

Originally Posted by ColColonCleaner*:

 

Sorry spatie if i missed your post, it happens occasionally when there are so many. Quad's answers are exactly right.

[ImportBot]

Originally Posted by wdfstryfe*:

 

I should increase the timer on that thread for warnings. In the meantime don't run such a high debug level. 1 second is normal.

Okay, I was trying to gather information as to what was wrong why it was crashing so often.

[ImportBot]

Originally Posted by Hodor*:

 

Get me line numbers by enabling plugin debugging on that layer and we can move from there.

I dont know what you meant really, but if you explain to me in detail how to do it - I'll do it

[ImportBot]

Originally Posted by spatieman*:

 

Sorry spatie if i missed your post, it happens occasionally when there are so many. Quad's answers are exactly right.

dont worrie..

the deleting user isue is fixed, i was pretty toated in my head that night.