FileZilla Log Analyzer Now Released!

[Stunner]

The problem is just what I expected, "Failed to create listen socket on port..." wasn't being checked for by the parser, so it threw that error. I will be sure to fix that in the next version(coming soon... just working on documentation these days).

Unfortunately, as of now there are no flags or settings that would allow you to disregard files in the listed summary log. That feature has been duly noted and may be implemented in a future release.

And no, file sizes are not logged in log files so I cannot use that information in analysis. If you want that information you will have to make a request to include that functionality to the FileZilla Server developers.

[Stunner]

Alright guys, I finally just released FileZilla Log Analyzer version 1.10 alpha, available here: http://sourceforge.net/projects/fla/. It has a good amount of bug fixes and even more feature enhancements, such as the ability to filter, and a better flag system. Many of the feature enhancements/bug fixes came from the suggestions of users so keep those ideas/bug reports coming.

Version Changes

Code: Select all

1.10 alpha:
ENHANCEMENTS:
    -Can now filter by user, IP address, date, port or any combination thereof.
    -Scrambling by IP address now appropriately scrambles only public IPs. Specifically, those that are not in the following CIDR ranges:
        -127.0.0.1/8 (Loopback addresses)
        -10.0.0.0/8 (Private network)
        -172.16.0.0/12 (Private network)
        -192.168.0.0/16 (Private network)
        -169.254.0.0/16 (Link-local addresses)
    -Scrambling by user can be done in numbered fashion(User_1,User_2,etc.)
    -Flags can be specified much more flexibly, major improvements/changes made to flagHandler module:
        -concise and verbose flags can be specified(-p and --parse respectively)
        -flags that perform similar functions have been consolidated into one:
            -f,u, and i flags are now parameters to the scramble flag(-s, or --scramble)
    -Created help flag which briefly displays all flags and their parameters to command prompt
    -Writing/overwriting is now specified without redundancies (i.e. Writing xxx..., Overwriting xxx...)
BUG FIXES:
    -Made parser recognize message which caused an error to be thrown about file not being an authentic FileZilla Server log
    -Fixed bug that would cause an error when parsing by user instance if selecting portion where user only logs in or disconnects in log file
    -User names scrambled in action portion of log is now generated properly(consistent with user found in user portion of log)
    -Fixed rare bug in which scrambled IP wouldn't be created properly whenever an IP was scrambled to a private address

[Legs]

nice work

[Charlene]

Thanks a lot, the log analyzer is prefect! This is exactly what I needed for the payroll site that I am working on. I have been looking around for something like this, with out really knowing exactly what it was I needed. When I stumbled across this thread, I knew right away that this was exactly what I had been searching for. I am very grateful for this, thank you!

[Stunner]

Not a problem, happy to help! Thanks for the thanks.

[lisawinkler]

Nice analyzer be happy.

[PrzemekRyk]

Hi All

Well - I tried to analzye logs from my server, and I have a problem. My log files have 169,5 MB and 599 MB. I use command:

python FLA.py -Ff u logname.log

Command line runs with administrator privileges.

Unfortunatelly - I receive a message:

Writing FL-fzs-2012.log\FL-User\fl-user---.log...
Traceback (most recent call last):
File "FLA.py", line 41, in <module>
FLACore.main(sys.argv)
File "C:\temp\FLACore.py", line 2097, in main
processAndExecute(argv,nextArg)
File "C:\temp\FLACore.py", line 1991, in processAndExecute
writeLog(loginInst,discInst)
File "C:\temp\FLACore.py", line 1879, in writeLog
generatedLine,changeData,isMessage = generateOutput(line,prevLine)
File "C:\temp\FLACore.py", line 1696, in generateOutput
(m,p,d,t,f,u,i,a) = FLAmodule.getOriginalLine(toWrite)
File "C:\temp\FLAmodule.py", line 193, in getOriginalLine
(m,p,d,t,f,u,i,a) = _parseOriginal(line)
File "C:\temp\FLAmodule.py", line 156, in _parseOriginal
a = _parseAction(G.nextIndex, fline) #action
File "C:\temp\FLAmodule.py", line 68, in _parseAction
if fline[i+1] == "\n":
IndexError: list index out of range

I've tested this tool under Windows XP Professional ENG SP3 (with newer updates) and 32-bit Python 2.5.7 and under Windows 7 Ultimate x64 with 64-bit Python 2.5.7 installed.

I don't know what causes this errors, byt analyzer stops before checking the whole log file.

[avitalsamson]

Hey thanks for posting that..i guess the issue has been resolved so i really appreciate that.

[res5ect]

its great info, thanks for the goodies

[Stunner]

Hi All

Well - I tried to analzye logs from my server, and I have a problem. My log files have 169,5 MB and 599 MB. I use command:

python FLA.py -Ff u logname.log

Command line runs with administrator privileges.

Unfortunatelly - I receive a message:

Writing FL-fzs-2012.log\FL-User\fl-user---.log...
Traceback (most recent call last):
File "FLA.py", line 41, in <module>
FLACore.main(sys.argv)
File "C:\temp\FLACore.py", line 2097, in main
processAndExecute(argv,nextArg)
File "C:\temp\FLACore.py", line 1991, in processAndExecute
writeLog(loginInst,discInst)
File "C:\temp\FLACore.py", line 1879, in writeLog
generatedLine,changeData,isMessage = generateOutput(line,prevLine)
File "C:\temp\FLACore.py", line 1696, in generateOutput
(m,p,d,t,f,u,i,a) = FLAmodule.getOriginalLine(toWrite)
File "C:\temp\FLAmodule.py", line 193, in getOriginalLine
(m,p,d,t,f,u,i,a) = _parseOriginal(line)
File "C:\temp\FLAmodule.py", line 156, in _parseOriginal
a = _parseAction(G.nextIndex, fline) #action
File "C:\temp\FLAmodule.py", line 68, in _parseAction
if fline[i+1] == "\n":
IndexError: list index out of range

I've tested this tool under Windows XP Professional ENG SP3 (with newer updates) and 32-bit Python 2.5.7 and under Windows 7 Ultimate x64 with 64-bit Python 2.5.7 installed.

I don't know what causes this errors, byt analyzer stops before checking the whole log file.

Hey, apologies for not getting back to you on this sooner... Don't know what happened but I stopped being notified via email regarding replies on this thread. In order to determine what is causing the crash and allow me to fix it I will need to reproduce what you are witnessing. Is it possible for you to give me a scrambled log file that is stripped down to the point where it crashes? If you look back in this thread you will see the information I ask of someone in order to help me fix the bug. If you can provide me with that I would be happy to look into fixing this up for you.

EDIT: Just saw that you mentioned python 2.5.7... That may be why you are experiencing the crash. Try running the script on python 2.6 or 2.7.