The point is that you cannot generate an AWStats database file, if the database already contains information about a later date.
The easiest way to work around this problem is to move all database files to a temporary directory before you run the update for the older month (say April 2009). When the update is finished, you can move all database files (except the one of April 2009 if it already existed) back to their original directory.
If you have just one log file for April, add the logfile option as follows:
-logfile=/path_to/april_2009.log
where /path_to/april_2009.log is the path to the April log file.
If you have several log files for April, process them one at a time with the same kind of command as suggested above, starting with the oldest file, or use logresolvemerge as explained in the AWStats documentation.
1 more question if u can help- I am on awstats version 6.8 right now.. I saw at a few places where awstats was able to generate an extra field called filter for say the Pages URL page.. where one could filter by domain..
Is this a new feature in 6.9 or is it a part of any plugin that i may need?
You have Filter and Exclude filter in the Pages-URL section of the report. This is not new, but it cannot be used to filter domains in usual AWStats configurations.
You can use SiteDomain and HostAliases to filter by domain if there is a domain field in the log file. This is not new either. It applies to the complete AWStats report, not only to the Pages-URL section. How it works is described in awstats.model.conf .