| User | Post |
|
5:20 pm
October 15, 2007
|
Alec
| | |
| Guest
| | |
|
|
I have a question. I have awstats set up running against IIS logs and it has been working for quite a few months. But for some reason, every now and again it skips a day or two. For example, on one of the servers I deal with, it ran up until September 28, 2007, then skipped September 29 and 30th, and then started again with October 1st. There are log files that exist for those two dates, but awstats just didn't run against then.
Any thoughts as to why they wouldn't? And I've looked in the system logs and I couldn't find anything that gives me a good reason.
Thanks!!!
|
|
|
5:36 pm
October 15, 2007
|
Jean-Luc
| | |
| Admin
| posts 1043 | |
|
|
How do you run the AWStats updates ?
It seems that :
- either the update was performed before the log file was available and it failed
- or the update was not performed at all.
You should double check your update process.
Jean-Luc
|
|
|
6:25 pm
October 15, 2007
|
Alec
| | |
| Guest
| | |
|
|
We're running a single bat file through a scheduled task at around 1am each day against approximately 5 or 6 apps. Each app has 2 or 3 servers which are taken in and combined through logresolve, then thrown into awstats.pl.
The scheduled task runs every day, so the only thing I could think of would be if the servers were down at that point. But then every app wouldn't have a log. For this, though, some have logs, some don't.
|
|
|
7:23 pm
October 15, 2007
|
Jean-Luc
| | |
| Admin
| posts 1043 | |
|
|
I would monitor the results of the intermediate steps during the execution of the bat file. Among other things, you can record the output messages of the AWStats update in a file. I guess this would help understand why a problem happens from time to time.
Jean-Luc
|
|
|
10:28 am
October 15, 2008
|
fox1977
| | |
| Member | posts 3 | |
|
|
How can i record the errors from the awstats update job. I'm experiencing similar problems
Thanks
|
|
|
2:16 pm
October 15, 2008
|
Jean-Luc
| | |
| Admin
| posts 1043 | |
|
|
Hi,
Try to run the AWstats update from the command line. You can get several types of error messages. If the update is not aborted, at the end of the update, AWStats prints a count of old records, dropped records, corrupted records and new valid records. This should help understand where a problem is.
|
|
Login 
Register 
Search 
Home
Print this Post 
Reply to Post
Add a New Topic
Quote and Reply 
Topic RSS 
