Talk:AWStats Installation

From DreamHost
Revision as of 04:27, 19 October 2009 by Tobymackenzie (Talk | contribs) (Config files: include for multiple sites: new section)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

unnecessary directory move?

I didn't need this step:

Move the files in the /home/yourusername/awstats/wwwroot/cgi-bin/ directory into /home/yourusername/awstats/.

mv ~/awstats/wwwroot/cgi-bin ~/awstats

Should it be removed?

--Decio 12:53, 4 Jan 2007 (PST)

the 8am problem

Everuthing runs smoothly except for one problem : log analysis stops at 8am. I know for a fact that I get visits all day long. Can it be a time zone difference problem - I live in Europe. I think my config file is plain-vanilla but since I'm an awstats newbie I may be dead wrong.


You must specify a different logfile name, using time "tags" explained in awstats configuration docs.

You will end up each day analyzing yesterday's log and your statistics will always be 1 day late, but you really shouldn't mind, since this way you will not lose a single hit and you'll gain stats accuracy. My logfile name is specified as follows (add correct path before): access.log.%YYYY-24-%MM-24-%DD-24
Edit: I just noticed that DH nicely created an access.log.0 symlink that points to the last rotated log (substantially equivalent to the awstat tag above)

You might also want to check your logs last mod-time and adjust the time your crontab calls awstats, so that log rotation and awstats processes don't overlap.


ls/ .htaccess file

Doesn't adding the .htaccess file and the proposed ls some line above it, have the same purpose? And can someone specify how to place this .htaccess file to dummies like me? Can someone more knowledgeable work on it? --Decio 18:49, 19 Aug 2006 (PDT)


I've tried the cron script but it didn't work. Looking up in the Crontab page, it seemed to me that it lacks the path: /usr/local/bin/perl. Can someone more knowledgeable add it? --Decio 18:35, 19 Aug 2006 (PDT)

try the script in the command line first, that will show you your errors. My wouldn't work untill i changed the directory permissions from 755 to 777. I know that isn't right, but its the only way i could get it to work.


Could someone more knowledgeable tell briefly about the differences? The first builds static pages that may be better for CPU consumption, right? Also, command "mv wwwroot/cgi-bin ." should probably be "mv wwwroot/cgi-bin/* .". Mandrl

Well, you could do it yourself, I did it based on general examples I have used that worked. If it doesn't work, then it should be corrected so that it does work. Santosj 07:36, 16 Feb 2006 (PST)

The alternative removes some files and keeps only the wwwroot. I believe that the second completely rebuilds the pages, but I'm unsure about that. The alternative is simple, while the first is a little bit more work.Santosj 08:13, 16 Feb 2006 (PST)


This page needs wikifying and de-personalizing.

-- agreed. -- Jazzle 03:41, 2 Feb 2006 (PST)

Done this, and added the alternative installation guide to this one. Santosj 03:04, 15 Feb 2006 (PST)

The guide also needs to make it clear about the installations and include a few plugins for making the design better. Santosj 06:20, 9 May 2006 (PDT)

other troubleshooting

You may get the message 'Never Updated' at the top of your stats page: Do read the /docs/awstats_setup.html#BUILD_UPDATE page, and do as suggested there. -- Jazzle 03:41, 2 Feb 2006 (PST)

-- another

755 as a permission for the folders wouldn't allow the script to build the pages or access statistics for the first time, the browser returned a message permission was denined.


I've recently done an edit that only deals with the file structure of the most recent build.. I thought that was applicable because people following this from the beginning don't want to be looking at 2 examples of a path and wondering which they aught to use. Oli


I tried to follow all instruction here and when I execute perl script, I got an error: LogFormat is not defined. Did I miss anything on the steps?


In the awstats/cgi-bin/ folder (if you're not there already), copy awstats.model.conf to, where "" is actually your website domain.

users were previously instructed to all files in cgi-bin to awstats then ls -o from cgi-bin. files wouldn't be in cgi-bin to ls

In the awstats/cgi-bin/ folder (if you're not there already), copy awstats.model.conf to, where "" is actually your website domain.

same problem. file would be in the awstats directory.

0 3 * * * perl /home/yourusername/awstats/tools/ -update -awstatsprog=/home/yourusername/awstats/cgi-bin/ -dir=/home/yourusername/

same problem. was instructed to be moved to but is listed in these pages as in cgi-bin/

Multiple sites

Wouldn't it be more efficient to use symbolic links for everything other than the config file if monitoring multiple sites?

Really a decent web stats package is a basic feature that ought to be provided by Dreamhost. Support for awstats and webaliser is 5 points suggestion in Control Panel\Home\Suggestions; I suggest that anyone who reads this page votes for it. --Kingboyk 09:56, 13 Nov 2006 (PST)

access.log file

Shouldn't the cron job refer to access.log.0 instead of access.log? If the cron runs at 3am, and the log is archived every day (presumably at midnight), you would only be importing 3 hours with of data. How does this work exactly?

Config files: include for multiple sites

I found for managing awstats for many sites that you can use the include directive at the bottom of the config file of each individual site to include a global config file. The per site config files can then be stripped down to only a handful of lines to make them easier to change. The global config file can be used to configure the basics for all site files at once then. Don't know if this would be worth mentioning on the page or not.--Tobymackenzie 11:27, 19 October 2009 (UTC)