The configuration file needs to remain in the same directory as The model configuration file gives you most of the information you. and this works like a charm, it takes every possible config from /etc/awstats/, but when I would like to generate html with i. Find the location, where script is installed, using one of the following rpm -ql awstats | grep buildstaticpages.
|Published (Last):||13 August 2014|
|PDF File Size:||10.46 Mb|
|ePub File Size:||17.3 Mb|
|Price:||Free* [*Free Regsitration Required]|
I removed it anyway but the result is the same. Jumped lines in file: Note that this domain matches up with the name of the config file you created in the first part of this series.
In the combined log format the web server records the size of all the requests and responses that get sent between the browser and the awstahs.
AWStats tip: creating static pages (and why it’s a good idea)
We used the standard combined log format: You will see that the script launches the awstats update process, then tells buildstaticpaves about every one of the 20 reports it is generating.
In this article, we will explain how to generate reports from the command line. Danny 60 1 9. Blog Rackspace Blog Developer Blog. It seems these values must be in the top file. Generating and Viewing Awstats Reports.
We’ve got awstats installed and configured, and now we can run it to generate web traffic reports. The third article in this series, Scheduling Awstats Report Generationwill show you how to save time and effort by automating the report generation process.
It updates the stats and generates several standard reports by using the main awstats. The first thing to adjust is the log format.
Installing AWStats and using it to build static statistic pages
The docs and even tutorials doesn’t tell anything about that. The main statistics you will see at the beginning of the report bear some quick explanation: In practice it doesn’t work that well most major search engines are wise to the practice and account for itbut that doesn’t mean we should encourage the inconsiderate jerks to keep trying it. Home Questions Tags Users Unanswered.
The first article in this series, Installing awstats on Linuxtaught you how to how to install and configure buildstaticpgaes for your site. We will now break it down and explain where each script option should go:. Wwstats would tell any robot that complies with the robots. We used the standard combined log format:. Edit your awstats config file accordingly, then run the report generation again to make sure it works with the new directory.
It is important to work out the address you will use to view the reports.
The command will look like this in our example: If you want to keep your stats public you should at least modify your site’s “robots. To make matters worse, the Alias is global, not specific to a single virtual domain. You might see less than a day’s worth of traffic in this initial report, or perhaps a week, depending on how often your web logs are rotated. If the same IP address appears in the web logs the next day, that would count as a second visit.
First bypass old records, searching new record Please contact your support team if you have a question or need assistance for any Rackspace products, services, or articles. This is a line in httpd. pp
Configuring Awstats With Static Pages – Network Admin Tools
If you want your web stats to show up on search engines for some reason, then at least tell robots not to index the referer page report: Post as a guest Name. Thank you for visiting the Rackspace Community. This is not necessarily the total bandwidth used by the site — it’s just the total bandwidth that got recorded in your web server’s access logs.
Everything a web browser requests from a site is a “hit. If you discover that you created the reports in a directory you cannot see from a browser, you may want to make a new reports directory. The “config” value should be the main domain name for the site.
Restart Apache to make the changes active, and get rid of the old format entries if you are changing:. You can do it manually by adding the following command to your cron: You can do that by password-protecting that part of the site, or by restricting access to that site to just localhost and using ssh tunneling to view your stats.
If you do this at the beginning, you will be able to hit your logs with a few entries by the time you finish configuring. We added the build script to our crontab:. I remember running this command before and it used to build all the pages, but now that I use it again it only builds the main page.
So not a lot that’s interesting just yet, but enough to make sure the reports were generated properly.