To save you time, I’ve created a list of tips that you can use to run AWStats with fewer problems. So, scheduling report generations is simple however, you still need to keep security in mind-a topic I’ll discuss a little later.ĪWStats is powerful and simple to use, but it does have some problems running on Windows. Remember, you launched it manually only to check the output and verify that the environment is OK. In fact, you actually need to run only, because that runs in the background. You can open the HTML file with a browser to see the analyzed data.Īs you can see, after setting up the correct folders and configuration, analyzing log data and creating reports requires running only two scripts. The preceding command causes AWStats to create an HTML-formatted report in the specified folder. Make sure to change the path to the report path you created. Now, from the same command window you used previously, run this command:Īwstats_ -update -config=.
#Awstats watch series archive
Also create a directory in this folder, to archive all report files for this particular configuration/Web site (you can create a different folder for each configuration/Web site you manage). Create a folder to contain the report (for this example, I used E:Reports, and copy the binicon folder to it. That’s because it builds on old data, checking and analyzing only new records in the IIS log.Īfter analyzing the log data, you can make AWStats create a report. AWStats now runs very fast, skipping all the records it’s already analyzed. If most rows are decoded, that’s Ok otherwise you probably have problems with your IIS log format. If you find that AWStats failed to decode only some rows (the results will indicate such problems), don’t panic. conf files are defined correctly, and that your IIS log file is in the correct format, and exists in the location where AWStats expects to find it. If any problems occur (you can check this from the results report), make sure that your Perl interpreter is installed and working, your. The actual file name depends on the configuration file name, the analyzed month, and so on. If everything worked, you’ll find a new file in your bindirdata folder. To run your first analysis, enter the command:Ī -config=That command causes AWStats to open your log file, analyze it, show the results, and then end. In the command window that opens, change directories to the bin folder that contains all the AWStats resources. Now select Start, Run, and enter the command cmd.exe /f:on. conf file at the log file you specified using the IIS MMC.
You will need to have an IIS log file to analyze, so you can point your. First, create an awstats.file in your bin folder as described in the previous section. The main parameter is -config, which defines the configuration file used by the program to analyze data and create reports.Įventually, you’ll schedule report generation automatically, but at first it’s useful to run AWStats directly from the command line, both to see how it works and to test that your configuration files are OK. Running AWStats is quite simple: You need run only and awstats_ however, you do need to provide some parameters.
0 kommentar(er)
