pyBEscanner

After the update I get the following time by time:

Code: 
Traceback (most recent call last):
  File "D:\..dnl\..git\pyBEscanner\pyBEscanner.py", line 254, in <module>
    pyBE.start()
  File "D:\..dnl\..git\pyBEscanner\pyBEscanner.py", line 217, in start
    server_scan.scan()
  File "D:\..dnl\..git\pyBEscanner\battleye_modules.py", line 214, in scan
    self.scan_battleye_logs(log)
  File "D:\..dnl\..git\pyBEscanner\battleye_modules.py", line 90, in scan_battle
ye_logs
    x)
  File "D:\..dnl\..git\pyBEscanner\battleye_modules.py", line 345, in scan_log
    if re.search(temp, entries_code[x]) is not None:
  File "C:\Python27\lib\re.py", line 142, in search
    return _compile(pattern, flags).search(string)
  File "C:\Python27\lib\re.py", line 244, in _compile
    raise error, v # invalid expression
sre_constants.error: unexpected end of regular expression
 
Yshido said:
After the update I get the following time by time:

Code: 
Traceback (most recent call last):
  File "D:\..dnl\..git\pyBEscanner\pyBEscanner.py", line 254, in <module>
    pyBE.start()
  File "D:\..dnl\..git\pyBEscanner\pyBEscanner.py", line 217, in start
    server_scan.scan()
  File "D:\..dnl\..git\pyBEscanner\battleye_modules.py", line 214, in scan
    self.scan_battleye_logs(log)
  File "D:\..dnl\..git\pyBEscanner\battleye_modules.py", line 90, in scan_battle
ye_logs
    x)
  File "D:\..dnl\..git\pyBEscanner\battleye_modules.py", line 345, in scan_log
    if re.search(temp, entries_code[x]) is not None:
  File "C:\Python27\lib\re.py", line 142, in search
    return _compile(pattern, flags).search(string)
  File "C:\Python27\lib\re.py", line 244, in _compile
    raise error, v # invalid expression
sre_constants.error: unexpected end of regular expression
Click to expand...

That error is flagged from a filter file containing dodgy regex. Try redownloading the lists (banlist, kicklist, whitelist etc) and see if that fixes the problem
 
hey k4n30, i know you from BF3 :) i used to play on your aVa gaming server and i killed you many times :p (on Battlelog my name is Stapo19)
 
Thanks for the hint. I found the problem and solved it.

May I asked another question though? I got this entry within my ban logs:

21.12.2012 15:00:21: PLAYERNAME: (IP) GUID - #0 113:5 Survivor2_DZ 117:14 Bandit1_DZ -1 [0,1,0]

Is this really considered a hack?
 
Maybe I'm missing something, but I'm having a little trouble here -

I want to run pyBEscanner against my Chernarus, Namalsk, & 2017 servers. The moment I fired it up, it banned a dozen people because Namalsk & 2017 have lots of custom weapons. So, I understand I need to update the filters to allow all this new stuff. But - I can't find an easy list somewhere of new weapons, etc.

So, is there a log-only mode? From another forum post by Torndeco (advising someone on getting gCam working) I had the impression there was, but looking at servers.ini I can't figure it out.

tl;dr - Anyone have filters for Namalsk & 2017, or a tip on how to setup pyBEscanner to log-only for a few days so I can collect lists of the legit things I need to add to the filters?
 
U can specfic to use different filter settings for different server's

So for example in servers.ini in the server sections u could have the following

Code: 
[Namalsk]
ServerName = Namalsk
ServerIP = 127.0.0.1
ServerPort = 2302
RconPassword = CHANGEME
BattlEye Directory = C:\DayZ Servers\IE 10\profile\Bliss\BattlEye
Server Console Log = C:\DayZ Servers\IE 10\profile\Bliss\server_console.log
Server RPT Log = C:\DayZ Servers\IE 10\profile\Bliss\arma2oaserver.RPT
Filters = dayz-namalsk, dayz-namalsk-weapons
 
 
[2017]
ServerName = 2017
ServerIP = 127.0.0.1
ServerPort = 2312
RconPassword = CHANGEME
BattlEye Directory = C:\DayZ Servers\IE 10\profile\Bliss\BattlEye
Server Console Log = C:\DayZ Servers\IE 10\profile\Bliss\server_console.log
Server RPT Log = C:\DayZ Servers\IE 10\profile\Bliss\arma2oaserver.RPT
Filters = dayz-2017, dayz-2017-weapons

If the filters dont exist, pyBEscanner will create the folder & empty filter files..
This way both servers can use different filters, since u are running different maps / mods....

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

pyBEscanner will log all unknown entries into log files in <battleye folder>/logs/<date>/*unknown.txt
U can then review the log entries after its running for abit, and start to add to the filters i.e
/path/to/pyBEscanner/filters/<filter sets>/

pyBEscanner will not re-scan old log entries, so any chances will only effect new scans.
So after u add the new entries to the filters u could delete the unknown log files if u wanted, u still got the original log files if u need to find a hacker / scripter
U can also add alter / change the settings / filters while app is running, just if u make a typo it will cause the pyBEscanner to crash with an execption.

If u need a hand i am normally semi-afk on irc irc.thekreml.in/6667 # dayz
U can also look over other filters / filter's readme aswell

edit:- If u do make up some filters for namalsk / 2017 . And get some spare time upload them somewhere or submit them on github if u like thx
 
@Everyone
Still working away slowly on new version...
Am considering changing the name with new version due to aim of it having scan different files than just battleye
Also due to fact am changing over to python 3 aswell...

------------
------------
@Yshido
What log file is the following from ?
21.12.2012 15:00:21: PLAYERNAME: (IP) GUID - #0 113:5 Survivor2_DZ 117:14 Bandit1_DZ -1 [0,1,0]
Click to expand...

After awhile be logs all start to look the same to me
 
Torndeco said:
After awhile be logs all start to look the same to me
Click to expand...

Tell me about it. Seems alot of people are using this program other than myself, don't hesitate to suggest filter improvements everyone (through pull requests), atm its just what I see in the logs, plus some from Torndeco when he gets the chance

Keep up the good work Torndeco :)
 
Torndeco said:
------------
@Yshido
What log file is the following from ?


After awhile be logs all start to look the same to me
Click to expand...

Found it multiple times in the attachto-unknown.txt but i would not put it on the whitelist. The reason is: At least 2 players with an entry like that where banned for other stuff (addmagazinecargo). So it might be a hint for the admin to have a closer look at those players.
 
@Yshido
Not sure to be honest, but does look odd
Prob need to look into code of bandit morphing, since it might trigger it...
But really need to look @ dayz code & prob do some testing on it
Shame dayz code isn't document abit more....

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

@Everyone else
Done some filter cleaning up / tweaking...
Mainly to reduce filter entries + make them catch abit more...

Main change is a blanket catch all ban rule on create-vehicle.banlist

Its alot easier for us to just white-list the good items, and just have a single rule to ban for everything else...
That way we don't have blacklist every single vehicle / object in arma / dayz mod / map

More than likely will do the same for the filters i.e addmagazinecargo / addbackpackcargo etc
 
@ Torndeco - isn't that the strict option? I'm running that on a few files like remoteexec and mpeventhandler too

@ Yshido - as its a legit dayz process its hard to scan for, but they usually slip up elsewhere (other log files) or spam the attachto then you know you can ban them. Unfortunately its one of those ones you need to monitor and cant just ban for it
 
I completely forgot about strict option...
Anyway i reverted the createvehicle banlist back...

Prob should look @ at making an example of a basic servers.ini / servers-recommeded.ini over the weekend.
i.e recommended would have more strict options as default...

To tired atm, but the createvehicle spam detection has a tendancy to ban the odd person for spaming tents

Might be worth changing the rule to
Code: 
4 1 BAN #0  (?!["WeaponHolder_ItemTent"])
5 8 BAN #0  (?!["WeaponHolder_ItemTent"])

And just make a seperate kick rule for tents ?

Or am i beening to kind :)
 
Just installed this and I like it - I let it scan todays logs and it added 3 people to my bans list. Great! Although I had already banned said people myself earlier on in the day. What I want to know though, where is the log evidence it used to make the ban stored?

Edit: Nevermind I was being blind! Thumbs up.
 
Ok finally getting some work done on new version of pyBEscanner...
Its @ https://github.com/Torndeco/pyBEscanner-v3

Requirements = Python 3.3
It uses the exact same filters

Atm, there isn't much changed really....

I just got internal tracking of bans done...
And some nicer console output i.e less spam (not counting intial spam while loading bans.txt)
Also improved some error handling on exiting app during file operations..

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

Short Version
pyBEscanner-v3 = developmental version, bugs
pyBEscanner = stable version (i.e will fix bugs, update filters, but no new features)
 
Happy New Years...
Update for pyBEscanner-v3 if anyone doesn't have a hangover + wants to test it out & see whats breaks

Got the backbone for server_console.log done.
App now creates a backup server console log + aswell as a seperate chatlog aswell.
Will be using same / similar code for reading rpt logs aswell

Please read the readme as there are afew changes....
Especially when it comes to server restarts to avoid file locking / open with server logs

Note:- This is still what i consider a development stage, so expect bugs & changes
 
Hey Torn,

I'm doing something noobish here, maybe you will know. the v2.7 pyBEscanner stopped working after a server crash - every time i opened it, it just closed itself. So I downloaded v3 and updated to python v3.3, and when i start the v3 scanner, it just opens and closes itself instantly, but strangely, after updating to v3.3, the v2.7 scanner now works fine? Dafaq am I doing wrong? Also I noticed BanZ Union mentioned in your readme :3

EDIT: And yes before you ask i have edited the servers.ini :)
 
There was afew commits in last few mins that might have problem sorted

But to really need to launch the app in a console window i.e cmd.exe
This way u will see the error it exits out on especially if u are gonna be using v3 (still has some teething issues)
edit:- Also if pyBEscanner-v3 crashes it wont launch again unless u use launch it using -f switch.
pyBEscanner.py -f



As for why standard pyBEscanner started to work for u after the crash.
More than likely u removed the temp folders once u updated to v3...
A temp file prob got corrupted during the server crash
Once u deleted / removed the temp folders (as mentioned in v3 readme), it ran fine afterwards...
 
Torndeco said:
There was afew commits in last few mins that might have problem sorted

But to really need to launch the app in a console window i.e cmd.exe
This way u will see the error it exits out on especially if u are gonna be using v3 (still has some teething issues)
edit:- Also if pyBEscanner-v3 crashes it wont launch again unless u use launch it using -f switch.
pyBEscanner.py -f



As for why standard pyBEscanner started to work for u after the crash.
More than likely u removed the temp folders once u updated to v3...
A temp file prob got corrupted during the server crash
Once u deleted / removed the temp folders (as mentioned in v3 readme), it ran fine afterwards...
Click to expand...


You're like a magician. Yes I had deleted the temp files. People will write songs about you! I will update to your latest commits. Thank you again
 
I ran the module in IDLE

Code: 
---------------------------------------------------------
       pyBEscanner-v3
---------------------------------------------------------
Traceback (most recent call last):
  File "***\pyBEscanner-v3-master\pyBEscanner.py", line 321, in <module>
    main.start()
  File "***\pyBEscanner-v3-master\pyBEscanner.py", line 239, in start
    self.loadconfig()
  File "***\pyBEscanner.py", line 133, in loadconfig
    default[options[x][1]] = config["Default"][options[x][0]]
  File "C:\Python33\lib\configparser.py", line 1205, in __getitem__
    raise KeyError(key)
KeyError: 'Bans Symlinked'
>>>
 
You must log in or register to reply here.
Back
Top