Processing advanced statistics stuck at 100%
Processing advanced statistics have been stuck at 100% for hours, running on a zip file with 1.2 GB worth of data when unzipped. Is it stuck due to the large size?
Replies 8
The program is using around 16-20% CPU and 49,1 MB memory, so by no means a heavy strain on the server. It is my first time running the program, would it be it has so far been stuck for at least 5 hours like this.
Should I cancel the analyzing and try again?
Should I cancel the analyzing and try again?
It is a very unusual behavior. The program shouldn't stuck on 100% in "processing advanced statistics" for more than few seconds.
You should try to cancel the analysis and run again, but probably you will have to close the program through the Task Manager, open it again and run the analysis.
If the error appears again, could you check if it occur if you analyze another log? Also have you set custom analysis settings (e.g. including queries or increased the default session timeout)?
You should try to cancel the analysis and run again, but probably you will have to close the program through the Task Manager, open it again and run the analysis.
If the error appears again, could you check if it occur if you analyze another log? Also have you set custom analysis settings (e.g. including queries or increased the default session timeout)?
The program is not frozen, so I could shut down the program without resorting to task manager.
I still get the same problem when I attempt to read other zipped log files.
I'm not using any custom analysis settings.
When I unzip one of the log files and use the program on a single log file, there's no problems. Is there a specific way that the zip files with the logs must be set up?
I still get the same problem when I attempt to read other zipped log files.
I'm not using any custom analysis settings.
When I unzip one of the log files and use the program on a single log file, there's no problems. Is there a specific way that the zip files with the logs must be set up?
No, the zipped logs are processed the same way as unzipped ones. Could you send us a sample zipped log that causes the problem so we check why it happens? Our email is support@weblogexpert.com
Unfortunately, the zip files are too large to send as an email, but I have uploaded one to the public part of a dropbox account and will send you the link.
The email has the title "Processing advanced statistics stuck at 100% log file"
Please let me know when it has been downloaded.
The email has the title "Processing advanced statistics stuck at 100% log file"
Please let me know when it has been downloaded.
Thank you, I've downloaded and checked the file. The problem is that the .zip files contains a very large number of small logs. Opening each separate log in a .zip file currently requires much more time than opening usual files, so that's why the program takes too long time to analyze the logs.
"Processing advanced statistics" is always shown at 100% because this message is shown at the end of analysis of each log before analysis of the next log is started. As analysis of each log (after opening it) takes almost no time, the message seem to be unchanged all the time.
The best solution for future logs is to switch to daily ones instead of hourly ones. For the existing logs you can either wait for analysis to finish (it should finish eventually, it will simply take a lot of time) or unpack .zip file and analyze unpacked logs.
BTW if you wish you can analyze folder with multiple subfolder with unpacked logs at once. You can analyze log files that match a wildcard from a folder and its subfolders by adding the @ character before the log path.
Example: @c:\Logs\*.gz
In this example files with the .gz extension from the c:\Logs folder and its subfolders will be analyzed.
"Processing advanced statistics" is always shown at 100% because this message is shown at the end of analysis of each log before analysis of the next log is started. As analysis of each log (after opening it) takes almost no time, the message seem to be unchanged all the time.
The best solution for future logs is to switch to daily ones instead of hourly ones. For the existing logs you can either wait for analysis to finish (it should finish eventually, it will simply take a lot of time) or unpack .zip file and analyze unpacked logs.
BTW if you wish you can analyze folder with multiple subfolder with unpacked logs at once. You can analyze log files that match a wildcard from a folder and its subfolders by adding the @ character before the log path.
Example: @c:\Logs\*.gz
In this example files with the .gz extension from the c:\Logs folder and its subfolders will be analyzed.
Thanks for the help, unfortunately changing the logging is not an option, so I will simply let it run its course and try the wildcard option.
1.2GB log is relatively small log, so there shouldn't be any problem with analyzing it because of its size.