Facebook
TwitterI've had some problems with the statistics tools which I have finaly managed to solve. But now I'd like to get statistics.exe to prosess old log entries to rebuild log statistics for the time when the statistics where not working corecly... Dos anyone know how this can be done?
-
Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
-
The BIND DNS server has already been deprecated and removed from Plesk for Windows.
If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release. -
The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.
How to prosess old log files
- Thread starter VagaStorm
- Start date
M
Mr.Incredible
Guest
As far as I know it's impossible - statistics.exe can't process old log files 
V
vautrain
Guest
Does anybody have a workaround for this? I would run awstats.pl by hand, if I knew exactly how Plesk calls it. In fact, I have a script that I can use to run awstats.pl until it "catches up" with the current date. I just haven't been able to figure out how Plesk runs awstats. I'm on 7.0.3, BTW.
E
eara01
Guest
If the log files can't be processed, then this begs a question:
Why have the option to keep them around? If you can keep them around for any length of time, one would think that there would be a way to process them.
Perhaps someone from SWsoft will read this and shed some light on it for you.
Why have the option to keep them around? If you can keep them around for any length of time, one would think that there would be a way to process them.
Perhaps someone from SWsoft will read this and shed some light on it for you.
J
JAFO@
Guest
Log procession feature will be extended in later versions of Plesk, may be it will be possible to reprocess old logs...
I'm not from SWSoft btw, these folk have told exactly the same I've just told you...
I'm not from SWSoft btw, these folk have told exactly the same I've just told you...
V
vautrain
Guest
I opened a trouble ticket with SWSoft on this. I could take care of this myself, if I knew exactly how Plesk statistics.exe calls AWStats to update the reports. Hopefully SWSoft can provide that info to me.
J
jbuts
Guest
Actually, old log files can't be processing again.
V
vautrain
Guest
Actually, I've done it with custom installations of AWStats. If I could just get someone to tell me exactly how Plesk runs AWStats, I could do it with all my Plesk sites, also.
V
vautrain
Guest
I have a solution for this that is working on my Windows 2003 server. It does not use Plesk at all, except to copy the "statistics" directory for a new virtual directory to put the stats pages. It requires:
Win2003/IIS6
PHP CLI (included with Plesk)
robocopy (downloadable from MS/Resource Kit)
It uses the IIS6 logs, not those generated by Plesk. It works by calling a modified version of iisweb.vbs to output a text csv file of webs, service numbers, and log file locations, and it reads that data into an array.
Looping through the array, it determines when the last time awstats was run on the site, by attempting to read a date from a data file. It then calls awstats to update the data file(s) for each day between the last time it was run, and the day before the current day. This is how it can process old log files, and "catch up" to the current date. It takes a while to catch up, especially if you turn on DNS lookup. I tried to turn on DNS lookup, and it would have taken several days to catch up all the sites on my server (about 150 sites). I turned it off.
It then checks for the physical directory and icons where the static pages will be stored, and creates them if they don't exist, tries to create the virtual directory. Finally, it outputs the static report pages.
I also have a version that outputs data files for CGI (I have to use a slightly different conf file). Some of my clients need the CGI version.
Email me if you want the files. Most of the code is not commented, but it's not difficult to follow, if you're familiar with basic scripting, and you're familiar with awstats. I can't offer any warranty or support, but if I can make it work, a monkey should be able to make it work.
will at hansoninfosys dot com
Win2003/IIS6
PHP CLI (included with Plesk)
robocopy (downloadable from MS/Resource Kit)
It uses the IIS6 logs, not those generated by Plesk. It works by calling a modified version of iisweb.vbs to output a text csv file of webs, service numbers, and log file locations, and it reads that data into an array.
Looping through the array, it determines when the last time awstats was run on the site, by attempting to read a date from a data file. It then calls awstats to update the data file(s) for each day between the last time it was run, and the day before the current day. This is how it can process old log files, and "catch up" to the current date. It takes a while to catch up, especially if you turn on DNS lookup. I tried to turn on DNS lookup, and it would have taken several days to catch up all the sites on my server (about 150 sites). I turned it off.
It then checks for the physical directory and icons where the static pages will be stored, and creates them if they don't exist, tries to create the virtual directory. Finally, it outputs the static report pages.
I also have a version that outputs data files for CGI (I have to use a slightly different conf file). Some of my clients need the CGI version.
Email me if you want the files. Most of the code is not commented, but it's not difficult to follow, if you're familiar with basic scripting, and you're familiar with awstats. I can't offer any warranty or support, but if I can make it work, a monkey should be able to make it work.
will at hansoninfosys dot com
Similar threads
