pyBEscanner

Its just pyBEscanner internal storage of bans GUID/IPs...
I prob should disable that debug statement to avoid confusion.

Basicly it parses and loads the bans into memory to check against when banning a player.
Prevents same IP/GUID get beening banned multiple times in bans.txt

Previous versions
A player could get banned multiple times.
Either for getting banned in multiple log files..
Or if they got banned, + on next log scan still had entries from the player (from just before they got banned).
They would end up getting banned again.
 
Ah, thanks for clearing that up. Yes, the debug is rather confusing when you don't know what it's doing. PS - check your inbox. Messaged you something I did not feel comfortable posting here.
 
New update.
Is i just finally got around to fixing up pyBEutility.pl, still had a bunch of python 3 code in it...

Anyway it can actually start now...
Basicly, u can tell pyBEscanner to pause / resume scanning..
Incase u are paranoid of open file locks on server logs, when u try & rotate / delete them.

The Download Ban Files from cbl / banzunion = almost done...
I just want to split out the conf.ini code from pyBEscanner / pyBEutility to a seperate file, so they can both use the same code.
 
Sounds good Torndeco :)

On a separate note, has anyone had any issues with the Selectplayer.txt bans? I notice I've been getting alot of appeals lately but no other admins have mentioned having any issues with it, so I'm wondering is it just me that's getting heaps of false positives or have others turned it off?
 
I had it turned off when i had more players on servers, seem to be triggered on long loading times.
I just assumed it was due to me running custom code + fred's performance changes at the time.
Since no-one else mentioned it / encountered it....

Turn it back off or change it to a kick ?
 
I think we have a false-positive script here. I have seen it a few times and never been sure about it as to be truthful, I didn't understand it. A very trusted player/friend of mine was auto banned for it recently after loading/unloading a patient from a vehicle. I think the filter needs some looking into.

02.02.2013 19:20:36: xxxxxx - #0 "norrnRLact" = <NULL-object>
 
Auto-updating severs bans.txt using CBL / Dwarden / Banzunion bans file is now supported via
Code: 
pyBEutility.pl --download-bans

Plz note this feeature is just doing a simple http url download.
So be kind and don't try and update your bans every hour.
Once a day / week should be good i hope

--------------------------------------------------------------
--------------------------------------------------------------

Removed 2 rules from banlist for now...
selectplayer rule from bans, until get better info... put into kicklist instead ? *shrugs*
norrnRLact seems be cause by code in via dayz_code\medical\load\load_act.sqf


edit: 2474 Total unique bans from CBL / Dwarden / Banzunion Bans
 
Delete your temp folder, its an old bug... fixed in newer pyBEscanner...
Am slighty confused how u encountered it... but not gonna time lookin over older code...
 
Thank you for the fast response.
It didn't fix. Going to remove all the files and re-install it.

Although I am using 2017 Filters that Shin set up, I doubt that would cause the issue though.
 
In your Servers Battleye Folder delete your bans.data files
Your bans.data file = wrong version somehow (corrupted i would have to guess)

Their is a bug in the code when it encounters it, just sent shin a fix for it afew mins ago..
 
@norsk2277
pyBEscanner should have no problems running on windows / linux (needs mono).
Just remember to run it in a console, that way if it crashs / stops u can see the reason why.


------------------
------------------



@Everyone else
Updated Conf Info for for IP Ban Time.
Turns on i had it set to ban by days + not hours opps

Also new config options to set
Temp Directory / Log Directory per server if needed

Thx for HIMjack666 & wriley for above

------------------
------------------

Note:

Server scanning code really does mean expermential...
i.e server_console.log / rpt logs

U will need to delete your server console logs + might aswell do the rpt aswell, during server restarts.
This is easiest way / simplest solution for pyBEscanner to notice the server has restarted.

U prob should move the files to back them up, till server code is finished... just incase i break archiving the logs
 
I think pyBEscanner is causing issues when purging logs

Code: 
16:26:59 BattlEye Server: Failed to open event log file
16:26:59 BattlEye Server: Failed to open event log file
16:36:24 BattlEye Server: Failed to open event log file
16:36:24 BattlEye Server: Failed to open script log file
16:36:24 BattlEye Server: Failed to open script log file
16:36:24 BattlEye Server: Failed to open script log file
16:36:24 BattlEye Server: Failed to open script log file
16:36:37 BattlEye Server: Failed to open event log file
16:36:38 BattlEye Server: Failed to open event log file
16:36:38 BattlEye Server: Failed to open event log file
16:36:38 BattlEye Server: Failed to open event log file
16:36:38 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file
16:36:51 BattlEye Server: Failed to open event log file

^thats spammed in the server_console.log

Running 1.7.5.1 chernarus with beta patch 101480(?latest). Using latest version of pyB from the repo
 
Its just arma complaining the battleye log file = missing when it goes to append a log entry to it...
Never seen it cause any issues yet, except the odd warning about it...
i.e used the same method of moving log files & then scanning them since day 1

I look into rewriting the scanning code to use similar method to scanning server logs (once i fix the bug with it atm) next week.
 
Since 1.7.5.1 I have this kind of logs in my createvehicle-spam logs :
Code: 
Player Name = Lad
    Action = BAN
        10.02.2013 22:35:39: Lad 86.153.140.146:2304 f257b7db81f8b011ee481fe31c957b8 - #0 "DZ_TK_Assault_Pack_EP1" 111:433 [0,0,0]
        10.02.2013 22:35:39: Lad 86.153.140.146:2304 f257b7db81f8b011ee481fe31c957b8 - #52 "DZ_TK_Assault_Pack_EP1" 111:433 [0,0,0]
        10.02.2013 22:35:42: Lad 86.153.140.146:2304 f257b7db81f8b011ee481fe31c957b8 - #0 "DZ_TK_Assault_Pack_EP1" 111:439 [0,0,0]

Does anyone know why it's happening ? I'm pretty sure it is a false positive
 
Its a new backpack in 1.7.5.1
They aren't filtering the DZ_TK_Assault_Pack_EP1 out in CBL filters yet.
Or u could just add the exception to your pyBE rules for createvehicle spam
 
I've had to turn off pyBE - even with the latest filters, people on my server are being banned for innocent things =/ Mostly for

createvehicle
#0 "DZ_TK_Assault_Pack_EP1"
#52 "DZ_TK_Assault_Pack_EP1"

deletevehicle spam
#0 53:297 z_villager2
#0 53:362 z_worker2
 
You must log in or register to reply here.
Back
Top