Free Hosting With PHP FTP MYSQL cPanel

Free Hosting Unlimited Bandwidth

3000MB Free Hosting

Support	Tickets
Uptime	99%
PHP
Perl
Cron Jobs
FrontPage
Web Mail
POP3 Server
IMAP Support
SMTP Server
Custom Error Pages
AWStats (Real Time Stats)
Webalizer Stats

File size limit	8MB
CGI Access
Zend Optimizer
IonCube Loader
File Uploads
PHP mail() and Sendmail
fopen() and PHP sockets
safe_mode OFF
Latest phpMyAdmin
Unlimited MySQL database size!
.Htaccess Support
GD Library
Curl Support

Accessing Awstats from outside the control panel is easy.

Step 1.
Download awstats from http://awstats.sourceforge.net

Step 2.
Uncompress awstats-5.6.tgz

Step 3.
Copy the contents of the uncompressed cgi-bin folder from your hard drive to the user cgi-bin directory (this includes awstats.pl, awstats.model.conf, and the lang, lib and plugins sub-directories).

Step 4.
If necessary (should not be needed with most setups), edit the first (top-most) line of awstats.pl file that is
#!/usr/bin/perl
to reflect the path were your Perl interpreter is installed. Default value works for most of Unix OS, but it also might be #!/usr/local/bin/perl

Step 5.
Move AWStats icon sub-directories and its content into a directory readable by your web server, for example /home/users/public_html/icons

Step 6.
Copy awstats.model.conf file into a new file named awstats.myvirtualhostname.conf. This new file must be stored in /home/user/public_html/cgi-bin.

Step 7.
Edit this new config file with your own setup :
- Change LogFile value with full path of your web server log file (The path is: LogFile=”/usr/local/apache/domlogs/domain.com”).
- Check if LogFormat has the value “1″ (it means “NCSA apache combined/ELF/XLF log format”).
- Change DirIcons parameter to reflect relative path of icon directory. (DirIcons=”/icons”)
- Edit SiteDomain parameter with the main domain name or the intranet web server name used to reach the web site to analyze (Example: www.mydomain.com).

IMPORTANT!
- Change DirData to use the same Statics file than Cpanel Awstats and do not loose any entry.
(DirData=”/home/user/tmp/awstats/”)

Step 8.
Access AwStats by the URL:
www.yourdomain.com/

AWstats和Google Analytics目前都不支持用Title显示URL信息，以Drupal网站为例，经常看到一堆node/1, term/32之类没有意义的东西出现的排行榜，或是出口、入口地址，非要点击过去才能知道是什么。

所以最好利用Path Auto模块自动生成URL Alias，把Title自动映射为URL，便于在日志统计分析中一目了然。

可是，结果出现的确是以%B4%A3这样的Plain Text。

为此研究了一下awstats.pl的源代码，修改一下ShowURLInfo函数：

前几行改为

my $nompage;
if ($PluginsLoaded{‘DecodeURL’}{‘decodeutfurl’}) {
$nompage = CleanXSS(
DecodeURL_decodeutfurl($url, $PageCode || ‘gb2312′));
}
else {
$nompage = CleanXSS($url);
}

然后修改Awstats的配置文件，加入

LoadPlugin=”decodeutfurl.pm”

并且把这个decodeutfurl.pm文件放到/plugin目录下，就应该OK了。

刷新一下看看，enjoy。

现在AWStats除了无法显示单个用户访问明细，其他的效果还是不错的

首先，目录的安全性设置不好，解压缩后，需要在当前目录下

find . -type -d -print | xargs chmod 755

find . -type -f -print | xargs chmod 644

我把它放到/usr/local/awstats/wwwroot/jawstats下，并相应配置NGINX，添加一个php的入口

其他的都可以参照文档，唯一发现问题是启动后白屏，查一查error.log说undefined function Lang(）。

搜了一下论坛，发现是个已知的Bug，不知道怎么又出现在发行版。

vim一下 index.php, shift-g末尾，用问号向前搜<?, 第一个改为<?php， 保存退出，刷新就OK了。

1. 为了支持UTF decode

perl -MCPAN -e ‘install “Encode”‘
perl -MCPAN -e ‘install “URI::Escape”‘

然后可以打开LoadPlugin=”decodeutfkeys”

2. 打开LoadPlugin="tooltips"， 这个不需要添加而外的Perl 模块了


3. 去maxmind.com上下载最新的GeoIP C API, 并编译安装，虽然出于安全考虑，一般不愿意编译非Ubuntu源的第三方程序，但考虑它是开源，又广为传播，其模块甚至写道了awstats的默认配置文件了，应该不会有太大问题。此外FreeBSD也有了Port，那就随大流吧。

cd /usr/local/src
wget http://geolite.maxmind.com/download/geoip/api/c/GeoIP.tar.gz
tar zxf GeoIP.tar.gz
cd GeoIP-1.4.6
./configure
make
make install

Install后，就在/usr/local/share/GeoIP下生成了GeoIP.dat
然后下载最新的3个IP库

cd /usr/local/share/GeoIP/
wget -t 5 http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz
wget -t 5 http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
wget -t 5 http://geolite.maxmind.com/download/geoip/database/asnum/GeoIPASNum.dat.gz
gzip -d *

再安装必须的Perl模块

perl -MCPAN -e 'install "Geo::IP"'

最后修改Awstatus配置文件

LoadPlugin="geoip GEOIP_STANDARD /usr/local/share/GeoIP/GeoIP.dat"
LoadPlugin="geoip_city_maxmind GEOIP_STANDARD /usr/local/share/GeoIP/GeoLiteCity.dat"
LoadPlugin="geoip_org_maxmind GEOIP_STANDARD /usr/local/share/GeoIP/GeoIPASNum.dat"
#百万级以上网址使用：LoadPlugin="hashfiles"

4. 加载QQIP地址库

这里要用到2个第三方的Perl脚本
http://www.ieasy.org/download/qqhostinfo.pm
http://www.ieasy.org/download/qqwry.pl

看了一下源代码，比较简单，应该没有安全问题，也可以去刘辉的blog下载这两个文件

下载完成后，将文件保存到/usr/local/awstats/wwwroot/cgi-bin/plugin下

修改qqwry.pl，把

my $ipfile=”./QQWry.Dat”;
修改为：
my $ipfile=”/usr/local/share/GeoIP/QQWry.Dat”;

然后

cd /usr/local/share/GeoIP
wget http://update.cz88.net/soft/qqwry.rar

apt-get install unrar
unrar e qqwry.rar

在把除了QQWry.dat之外的文件全部删除

在/etc/awstats/awstats.yoursite.com.conf中，添加

LoadPlugin=”qqhostinfo”

应该就可以了

6. 创建GeoIP自动更新脚本

在/usr/local/share/GeoIP下，创建GeoIP_update.sh

#!/bin/sh

wget -q -t 5 -O /usr/local/share/GeoIP/GeoIP.dat.gz http://geolite.maxmind.com/download/geoip/database/GeoLiteCountry/GeoIP.dat.gz
wget -q -t 5 -O /usr/local/share/GeoIP/GeoLiteCity.dat.gz http://geolite.maxmind.com/download/geoip/database/GeoLiteCity.dat.gz
wget -q -t 5 -O /usr/local/share/GeoIP/GeoIPASNum.dat.gz http://geolite.maxmind.com/download/geoip/database/asnum/GeoIPASNum.dat.gz

gzip -df /usr/local/share/GeoIP/GeoIP.dat.gz
gzip -df /usr/local/share/GeoIP/GeoLiteCity.dat.gz
gzip -df /usr/local/share/GeoIP/GeoIPASNum.dat.gz

然后 chmod +x GeoIP_update.sh

crontab -uwww-data -e

27 3 5 * * /usr/local/share/GeoIP/GeoIP_update.sh

在每月5日3点21分，自动更新IP数据库

虽然AWStats现在已经支持输出静态网页形式的分析结果，但是页面布局没有用Perl生成的动态网页方便，而且用自带的用Perl编写的转换工具稍微有点慢，在流量不大的情况下，还是在Perl+Fast CGI上运行更舒服一些。

首先要参考之前的文章，建立好PERL+FCGI的运行环境，这步准备工作就够费劲的。

然后开始切入正题：

1. 下载最新版的AWStats，基本就是Perl包，所以没必要用apt-get，解压缩到/usr/local/awstats下

wget http://prdownloads.sourceforge.net/awstats/awstats-6.95.tar.gz
tar -xzf awstats-6.95.tar.gz
mv awstats-6.95 /usr/local/awstats

2. 创建一个存放awstats分析数据的目录
mkdir /var/lib/awstats
chown www-data /var/lib/awstats  //这是为了让awstats页面上能直接刷新最新数据

3. 自动配置awstats

cd /usr/local/awstats/tools
perl awstats_configure.pl

除了第一步因为是Ngin服务器的关系，所以要选none，其他基本按照提示选默认值

4. 手工编辑配置文件

1) 修改LogFile路径

LogFile = “/var/log/nginx/access.log”

如果是压缩格式的日志，可以用LogFile = “zcat /var/log/nginx/%YYYY-24%MM-24%DD-24.gz|"。这里用zcat是因为其使用管道输出，对系统资源消耗比较小，千万不要忘了最后的管道操作符！


假设原来/etc/nginx/nginx.conf中关于log部分是如此定义的：（要小变量心空格，不能少，否则awstats就不认了）

log_format  main  ‘$remote_addr $remote_user [$time_local] “$request” $status ‘
‘$host $body_bytes_sent $gzip_ratio “$http_referer” ‘
‘”$http_user_agent” “$http_x_forwarded_for”‘;

很容易知道，对应awstats配置文件中，LogFormat应该设置为
LogFormat= “%host %logname %time1 %methodurl %code %host_r %bytesd  %gzipratio %refererquot %uaquot %otherquot”

最后一个选％otherquot是应为$http_x_forwarded_for在AWstats 6.95中还不认识

3) 将AllowToUpdateStatsFromBrowser=1，便于浏览器中即时刷新数据

5. 更新Awstats的分析记录，测试一下刚才的配置
/usr/local/awstats/wwwroot/cgi-bin/awstats.pl -update -config=yousite.com

如果一切正常，应该看到类似以下的结果：
Create/Update database for config “/etc/awstats/awstats.yoursite.com.conf” by AWStats version 6.95 (build 1.943)
From data in log file “/var/log/nginx/access.log”…
Phase 1 : First bypass old records, searching new record…
Searching new records from beginning of log file…
Phase 2 : Now process new records (Flush history on disk after 20000 hosts)…
Jumped lines in file: 0
Parsed lines in file: 1234
Found 0 dropped records,
Found 0 corrupted records,
Found 0 old records,
Found 1234 new qualified records.

6. 修改logrotate.d下的nginx配置文件，在每天切割日志前，更新awstats状态

/var/log/nginx/*.log {
daily
missingok
rotate 7
compress
delaycompress
notifempty
create 640 www-data www-data
dateext
sharedscripts
prerotate
/usr/local/awstats/wwwroot/cgi-bin/awstats.pl -update -config=yoursite.com
sleep 59
endscript
postrotate
if [ -f /var/run/nginx.pid ]; then
kill -USR1 `cat /var/run/nginx.pid`
fi
endscript
}

7. 接下来是最关键的NGINX配置，

#AWStatus Perl CGI  server
server {
listen       80;
server_name  awstats.yoursite.com;
access_log   /var/log/nginx/awstatus.log main;
root /usr/local/awstats/wwwroot;
auth_basic            “Restricted”;
auth_basic_user_file  /etc/nginx/awstatus.pass;

location = / {
rewrite ^ /awstats.pl?config=freshventure.info;
}

location ~ .*(\.cgi|\.pl?)$ {
gzip off; #gzip makes scripts feel slower since they have to complete before getting gzipped
root /usr/local/awstats/wwwroot/cgi-bin;
fastcgi_pass 127.0.0.1:8000;
fastcgi_index awstats.pl;
fastcgi_param SCRIPT_FILENAME  $document_root$fastcgi_script_name;
include        fastcgi_params;
}

}

好了，测试一下http://awstats.yoursite.com，和前文一样，输入密码后，这次看到的应该就awstats的界面了

8. 如果需要配置静态页面，则可以在logrotate中替换掉上面的awstats.pl, 换成

/usr/local/awstats/tools/awstats_buildstaticpages.pl -update -config=yoursite.com -lang=cn -dir=/usr/local/awstats/wwwroot -awstatsprog=/usr/local/awstats/wwwroot/cgi-bin/awstats.pl。

如果需要更频繁的更新访问情况，则可以把这句命令加入到crontab中，例如crontab -e -uwww-data。

然后nginx相应调整为显示静态网页就可以了

参考文章：

1. 刘辉 － awstats 配置模板 参考

2. 刘辉 － AWStats：示来访者位置 QQ纯真库IP解析插件安装

3. Jeff’s Blog – Awstats安装和设置

4. Jeff’s Blog - NGINX下运行Awstats

5. Jeff’s Blog – IP地址数据库的自动更新

6. 使用 awstats 分析 Nginx 的访问日志

今后拓展阅读

1. 车东 － AWStats的千万级日志解决方案

Il WebMaster e Web Developer per analizzare il traffico di un Sito Web dispongono di vari strumenti. Per alcune di queste applicazioni è sufficiente integrare alcune linee di codice nella (o nelle) pagina principale (index.php, index.asp, o index.html) e l’archiviazione dei dati viene fatta direttamente dal server che offre il servizio.

In molti casi, però, per il WebMaster e Web Developer diventa necessario installare sul server del Sito Web una applicazione che archivi in locale il traffico per ottenere ulteriori riscontri, informazioni, misurazioni, risultati e via di seguito. In questo caso per le installazioni viene richiesto sul server il PHP e il DataBase MySql.

Leggi tutto l’articolo e fai il download su Le 5 Migliori Applicazioni Di Analisi Di un Sito Web In Open Source.

System Requirements
Internet Information Services 6.0
AWStats 6.x installed and configured
Microsoft.NET Framework 2.0

Installation and Setup

1. Download AWStats.Viewer distribution:

AWStats.Viewer 1.5.1 (for DNP 1.5.x)
AWStats.Viewer 1.0 (for DNP 1.0.3)

2. Unpack the contents of “build” folder to “wwwroot” folder of AWStats installation so, “default.aspx” page and “bin” folder of the application are located right inside of “wwwroot” folder. For instance, if you have AWStats instaled in “c:\AWStats” folder and path to its “wwwroot” is “c:\AWStats\wwwroot” then the path to ”default.aspx” will be “c:\AWStats\wwwroot\default.aspx”

3. Open IIS Manager snap-in and open properties window for AWStats web site (or virtual directory).

4. On “ASP.NET” tab select “2.0.50727″ version of the .NET Framework and on “Home Directory” (or “Virtual Directory”) tab specify correct Application Pool for ASP.NET 2.0 applications (different from DefaultAppPool). Click “OK” button to save changes.

5. Open application “web.config” and specify correct application settings (elements inside of
“<appSettings>” element):

AWStats.URL  - URL to “awstats.pl” Perl script. It may be an absolute or relative URL.

AWStats.Username - Username of Windows account used to login when Windows Integrated Security is enabled. If awstats.pl is available for anonymous visitors and doesn’t require Windows authentication you may leave this setting blank.

AWStats.Password - Password for the account above.

AWStats.AuthenticationProvider - Full-quialified name of the type (class inherited from DotNetPark.AWStats.Viewer.AuthenticationProvider) performing authentication of the user.

Authentication Providers

AWStats Viewer comes with 2 pre-compiled providers:

1. “DotNetPanelAuthenticationProvider” provider

Description:
Provider allows to authenticate users against usernames/passwords of the DNP Enterprise Server.

Qualified name:
“DotNetPark.AWStats.Viewer.DotNetPanelAuthenticationProvider, AWStats.Viewer”

Settings:
“AWStats.DotNetPanelAuthenticationProvider.EnterpriseServer” – URL to DNP Enterprise Server, for example “http://localhost/EnterpriseServer”

2. “ConfigFileAuthenticationProvider” provider

Description:
Provider allows to authenticate users against usernames/passwords stored in the awstats.<some-site>.conf file of the corresponding domain.

Provider looks for the following configuration setting in the appropriate .conf file:

SiteUsers=user1=psw1;user2=psw2;…

where “user1=psw1;user2=psw2″ are user/password pairs of users granted to access the statistics of this domain.

Qualified name:
“DotNetPark.AWStats.Viewer.ConfigFileAuthenticationProvider, AWStats.Viewer”

Settings:
“AWStats.ConfigFileAuthenticationProvider.DataFolder” – path to the folder where domain awstats.<some-site>.conf files are stored. It may be a relative path with a “~” at the beginning and  an absolute path on the disk.

Securing AWStats
As soon as all requests to “awstats.pl” Perl script will be passing through AWStats.Viewer application
you should deny direct access to “awstats.pl” script.

We suggest two possible methods of securing “awstats.pl”:

1. Disable “Anonymous Access” and Enable “Windows Integrated Security”.
To do this open IIS Manager snap-in and open properties window for “awstats.pl” file.
On “File Security” tab click “Edit…” button in “Authentication and Access control” group.
Uncheck “Enable Anonymous Access” checkbox and check “Windows Integrated Security” one.
Click “OK” button to save changes.

After disabling anonymous access opening “awstats.pl” right in the browser window will ask for
Windows account credentials. You should provide the credentials of anonymous account under which AWStats web site (or virtual directory) is running.

If your “awstats.pl” script is not available for anonymous visitors you should specify “AWStats.Username” and “AWStats.Password” settings (see above) in web.config of the application.
2. Grant access to “awstats.pl” from local IP addresses only.
To do this open IIS Manager snap-in and open properties window for “awstats.pl” file.
On “File Security” tab click “Edit…” button in “IP address and doname name restrictions” group.
Check “Denied access” radiobutton and add “127.0.0.1″ (or other local IP) to the list of granted IP addresses.

Not found yet.

Logs

* Latest Visitors
This feature that displays information about the last 300 people to visit your site.

* Bandwidth
This feature allows you to see how your bandwidth is being used.

* Webalizer
Here, you can learn more about the Webalizer feature. Webalizer compiles and analyzes information about your web traffic.

* Webalizer FTP
Here, you can learn more about the Webalizer FTP feature. Webalizer FTP compiles and analyzes information about your FTP server.

* AWStats
You can learn about AWStats here. This feature allows you to access web statistics processed by AWStats.

* Raw Access Logs
This feature allows you to see what content has been accessed on your website.

* Analog Stats
Here, you can learn about the Analog Stats feature. This feature allows you to analyze website traffic.

* Error Log
This feature displays the last 300 error encountered by your website.

* Choose Log Programs
This feature allows you to choose what statistical analysis programs you wish to use.

——-

End User Hosting.

I struggled to share the Logfiles directory from our 2008 shared hosting environment to a Unix-based AWSTATS implementation and, in the end, it seemed to make more sense to just host awstats local to the 2008 Server.  AWSTATS, which requires a Perl Interpreter, is a means of aggregating logs and presenting data for a particular site.  Installing this on Windows for IIS is new to me, but here we go.

You’ll need a Perl Interpreter and I’m going to be using ActivePerl which can be downloaded from ActiveState right here.  After the .msi package downloads (17 MB took about 1 minute) conduct the installation which put everything into C:\Perl\.  I accepted all the defaults during this installation.

You will also need to make some minor changes to your IIS Server config within the manager.  In IIS Manager click on the server name, double click on ISAPI and CGI restrictions and Allow the 3 Perl extensions to run.  If you point your browser at http://servername/PerlEx/bm.htm you’ll see one of the Perl Examples running.

Now go to awstats.sourceforge.net and snag the 6.9 .exe for AWSTATS installation.  I installed to C:\awstats\ but you can also use the default.  During the initial configuration, which will appear in a command window, I choose “none” as my web server since I don’t have apache installed – I’m using IIS.  To do this you have to set up the awstats.pl script as a CGI running on the default site (any site actually), and create a default config file which I am associating with the hostname of my Windows 2008 Server.

You will be told that you need to use the Task Scheduler to perform the aggregation, however.  I also created a virtual directory mapping hostname.tld/awstats to the c:\awstats\wwwroot\cgi-bin\ directory.  I am using the awstats_updateall.pl script in the Task Scheduler to perform my nightly aggregation – The script invoked is actually my path to perl.exe and the awstats_updateall.pl is invoked as a command line argument, but it runs at 12:01 am and the log format specifies records from the previous day – this means the awstats data is always going to be current to the previous day.

Quick Edit:  When using awstats_updateall.pl you have to have an awstats.domain.tld.conf file in the cgi-bin directory properly configured for each site you would like aggregated.  I am choosing to only aggregate data for those domains which have unique IP addresses (the shared IP hosts are essentially brochure sites and don’t have much need for access log preservation).

AWSTATS NEDIR?

AWStats, open-source ve ucretsiz bir analiz uygulamasidir. Kabiliyeti ve basarimi oldukca yuksektir. Web(Apache ve IIS) loglarini, Streaming loglarini, Ftp loglarini, Mail Server loglarini analiz edebilir; bunlarin sonuclarini grafiksel olarak sunabilir. Diger muadil yazilimlarla yapilsmis bir ozellik karsilastirma tablosuna bu adresten goz atabilirsiniz.

KURULUM:

AWStats’i http://awstats.sourceforge.net adresinden indirip istedigimiz bir dinizde actiktan sonra, actigimiz dizin icerisinde su adimlarli izleyebiliriz(biz “/usr/local/awstats” altina actigimizi farzederek islem yapalim; boyle yapmayabilirsiniz sorun degil, sadece eger burada olmazsa kuruluma baslarken standart dizinde olmadiginizi ve bu sekilde devam etmek isteyip istemediginizi soracaktir):

# cd /usr/local/awstats/tools
# perl awstats_configure.pl

Ayarlar oldukca anlasilir ve basit.

- Oncelikle sizden httpd.conf adresinizi isteyecektir, Alias tanimalamalari icin gerekli islemleri kendisi yapmak icin.
- Sonrasinda yeni bir config dosyasi olusturmak isteyip istemediginizi soracak, buna olumlu cevap vererek ilk sitemizin config dosyasinin temel ayarlarini bu sekilde yapabiliriz. Bu sorudan sonra artik olusturacagimiz configurasyon icin gereken bilgileri isteyecektir.

Config dosyamizin adini(dolayisiyla bu sitenin AWStats tarafindan taninan adini), sonra da bu config dosyasini nereye olusturacagini sorar(bu yeri default(/etc/awstats mesela) birakmanizda fayda var, aksi taktirde config dosyasini bulamaz update isleminde ve sizin bunu manuel ayarlamaniz gerekir ilgili dosyalarda).

Bu islemlerden sonra AWStats kisaca bilgilendirmesini yapacak ve islem sonlanacaktir.

Bu ayarlari bitirdikten sonra awstats etc dizininde olusan config dosyamizi duzenleyerek devam edebiliriz. Istedigimiz editorle “/etc/awstats/awstats.denemesitesi.conf” (burada denemesitesi bizim sitemizin kurulumda verdigimiz tanimi oluyor) dosyasini acarak sunlari degistirmemiz yeterli:

• LogFile=”analiz_edilecek_log_dosyamizin_adresi (orn: /var/www/log/denemesitesi-access.log)”
• DirData=”analizden_sonra_olusan_verilerin_yazilacagi_dosya_yolu (orn: /var/awstatsdata/denemesitesi)”
• SiteDomain=”log_dosyasindan_parse_islemi_icin_domain_adresi (orn: www.denemesitesi.com)
• HostAliases=”olabilecek_alternatif_domain_bicimleri (orn: denemesitesi.com)”

Dosyamizi kaydettikten sonra;

# cd /usr/local/awstats/wwwroot/cgi-bin/
# perl awstats.pl -config=denemesitesi -update

diyerek denemesitesi isimli domainin bilgilerinin analiz edilerek, config dosyasinda belirttigimiz uzere “/var/awstatsdata/denemesitesi/” altinda “awstatsMMYYYY.denemesitesi.txt” isimli bir dosyaya kendisinin okuyup sekillere dokecegi bilgileri yazmis oluyor(MMYYYY icin -> MM=month, YYYY=year).

Bu asamadan sonra secenegimiz bizim tercihimize gore degisiyor. Olusan bu verilerin nasil grafik olarak goruntulenecegi konusunda 2 tercihimiz var. Biri sayfalari statik HTML olarak olusturup, bu sekilde erismek; digeri sayfalari dinamik olarak Perl vasitasiyla cagirmak. Burada statik olarak tercih sebebiniz guvenlik kaygilari olabilir, ya da bambaska sebepleriniz olabilir. O ya da bu sekilde sonuclari statik olarak almak ve boyle incelemek isterseniz AWStats bunun icin gerekli araci barindiriyor.

SONUC GORUNTULEME / YONTEM 1: STATIC ICERIK

# cd /usr/local/awstats/tools
# perl awstats_buildstaticpages.pl -config=denemesitesi -update -lang=tr -dir=”/var/www/html/awstats/denemesitesi/” -awstatsprog=”/usr/local/awstats/wwwroot/cgi-bin/awstats.pl”

diyerek sonuclari web server araciligiyla erisebilecegimiz bir yere kaydettirmis olduk(siz boyle tercih etmeyerek web arabirimden erisilmesini istemeyebilirsiniz, bunun icin goruldugu gibi -dir parametresine ne verirseniz sonuc dosyalari oraya yaratilacaktir). Apache icin “DocumentRoot” taniminin “/var/www/html” oldugunu varsayarsak; bu sonuclara “http://server_ip_hostname/awstats/denemesitesi/awstats.denemesitesi.html” adresinden erisilebilir. Burada baska .html dosyalari da var, bu dosyalara da bu belirttigimiz index dosyasindan GUI araciligiyla erisebilir olacaksiniz.

SONUC GORUNTULEME / YONTEM 2: DYNAMIC ICERIK

Bunun icin ekstra islem yapmamiz gerekmiyor esasinda. AWStats kurulumunda httpd.conf dosyamizi dogru gosterdiysek bizim icin Alias ve ScriptAlias tanimlarini yapmis olacak zaten. Bu sekilde erisim icin “http://server_ip_hostname/awstats/awstats.pl?config=denemesitesi” adresinden erisilebilir(httpd.conf icerisinde ScriptAlias tanimini degistirmediginiz varsayilarak, cunku AWStats bunu “awstats” olarak tanimlar).

Karsimiza gelen sayfa static icerige gore artilar ve eksiler barindirmakta elbette. Temel olarak static icerik kadar hizli olmamasi eksi denebilir; arti olarak ilk goze carpan suzgec secenegine sahip olmamiz. Bu secenek sayesinde YIL ve AY secerek ilgili tarihteki grafikleri edinebiliyoruz.

Birden fazla site kullanacaksaniz, config dosyasini kopyalayarak icerisinde gerekli duzenlemeleri yapabilir ve kullanabilirsiniz. Config dosyamizin adinda bulunan ifade bizim AWStats tarafindan taninan config adimiz oluyor gordugunuz gibi. Yani “awstats.denemesitesi.conf” dosyasini “awstats.yenisite.conf” olarak kopyalayip duzenledikten sonra(en basta belirtilen LogFile/Dirdata vs. ifadelerini) “-config=yenisite” denildiginde AWStats bu domain icin istedigi bilgileri etc dinizinde “awstats.yenisite.conf” dosyasinda arar ve buldugunda o ayarlara gore islemini yapar; baskaca bir yerde kayit tutmaz.

OTOMATIK UPDATE:

Dirdata icerisinde yer alan bilgilerin guncellenmesi islemini otomatiklestirmek istersek basitce cron ile yapabiliriz. Cron‘a soyle bir tanim girerek her gun saat gece yarisindan 10 dakika once(23:50) ilgili domainimiz icin guncelleme yaptirabiliriz:

50 23 * * * /usr/local/awstats/wwwroot/cgi-bin/awstats.pl -config=denemesitesi -update &> /dev/null

Cok domain analiz ediyorsaniz her domainle tek tek ugrasmak istemeyebilirsiniz. Bunun icin de yine AWStats ile gelen bir scripti kullanarak tum domainleri tek harekette update edebilirsiniz:

50 23 * * * /usr/local/awstats/tools/awstats_updateall.pl now -awstatsprog=/usr/local/awstats/wwwroot/cgi-bin/awstats.pl &> /dev/null

Static icerik olusturarak kullanacaksaniz o islemi de otomatik yapmaniz gerekecektir, yine yukarida gordugumuz bu islemin yontemini ayni sekilde cron‘a ekleyebilirsiniz. Tabi bu islemi Dirdata guncellendikten sonra yapmak mantikli olacaktir, guncel html sayfalari olusturmak icin.

55 23 * * * /usr/local/awstats/tools/awstats_buildstaticpages.pl -config=denemesitesi -update -lang=tr -dir=”/var/www/html/awstats/denemesitesi/” -awstatsprog=”/usr/local/awstats/wwwroot/cgi-bin/awstats.pl”

Static degil dynamic icerik kullaniyorsaniz zaten buna gerek yok, ilgili web sayfasina her girisinizde veriler zaten Dirdata icinden okunarak size oyle sunulacaktir.

Hizlica ve temel kavramlarla AWStats kurulumu bu sekilde basitce yapilabilir.

—–
Iyi Calismalar…

Googles gratis besöksstatistik Google Analytics har inneburit en smärre revolution. Alla webbplatsägare ska använda, och använder det idag. Får ni som kund inte ett erbjudande om Google Analytics, om ni inte har en väl kompletterande tjänst, bör ni ifrågasätta vems intresse er leverantör sätter främst. Nästan hälften av alla svenska sajter, med en budget och redaktion, bedöms använda Google Analytics för webbanalys idag.

Det syntes t ex i IW:s Topp 100 undersökning där 50 % hade fått kodsträngen inlagd inom <head> taggarna på sin sajt. Mer än så krävs inte. Dessutom kan sajter med AdWords koppa de två Googletjänsterna mot varandra. Och vill ni visa upp er (kostar pengar) är numera även Google Analytics godkända av KIA som leverantör av officiella unika webbläsare, sessioner och sidvisningar.

Så varför skulle någon välja att betala för en statistiktjänst idag? Troligtvis för ni har extremt höga krav på demografisk uppdelning, e-handelsstatistik eller automatiskt skräddarsydda rapporter. Det erbjuder tidigare populära betaltjänster som Webtrends Analytics 8.6, Omniture SiteCatalyst, Omniture HBX Analytics/Visual Sciences (WebSideStory), SiteStat, Site Census (Nielsen/Netratings), Insight XE (Sifo Research International) och delvis Open Source loggläsningsverktyget AWStats. Alla är de tidigare mycket populära statistikprodukter som sedan Google Analytics framfart 2006 fått stryka på foten.

En sak ska jag passa på att ta upp. Samma år, 2006, lade jag in Analytics åt kunder. Där upplevde vi sedan en märkbar inladdningsfördröjning av hela sajten. Det kunde ta 10-15 sekunder extra då sajterna skulle ladda mot Googles Urchinserver. Givetvis en katastrof. Detta problem var tidigare debatterat då en delokaliserad statistiktjänst, istället för en webbloggläsare, är beroende av en extern server. Men detta har sökjätten styrt upp sedan dess. Jag har inte hört att det ska ha orsakat några fortsatta problem.

Svenskt statistikval nummer två på samma lista är betaltjänsten Omnitures uppköpta verktyg SiteCatalyst och HBX Analytics/Visual Sciences.

Bài viết này sẽ hướng dẫn các bạn thực hiện việc setup Awstats.

1. Giới thiệu

Awstats là gì? Là một công cụ thống kê, xem thông tin Log rất hiệu quả. Hổ trợ log Web, Ftp, Mail..

Phạm vi bài này chỉ hướng dẫn các bạn setup Awstats với web log httpd apache.

2. Chuẩn bị và cài đặt

Phải có web server, ở đây các bạn có thể build một web server riêng chạy tách biệt với web server cần xem log, và bài này cũng hướng dẫn setup trên một web server khác. Vậy chúng ta có 02 web server: 01 chạy awstats, và 01 là web cần xem log.

Tại sao như vậy? Vì LM sử dụng awstats như là một tracking tool, vì thế khi web server chính có sự cố, thì mình vào web phụ này xem awstats.

Thư mục documentroot của web server chứa awstats ví dụ là: /home/websites/

OK, download awstats về, dạng tar.gz: http://prdownloads.sourceforge.net/a…ats-6.7.tar.gz

Xả nén:

tar zxvf awstats-6.7.tar.gz
mv awstats-6.7.tar.gz awstats
mv awstats /home/websites/

Tiếp:

cd /home/websites/awstats/tools
./awstats_configure.pl

Từng bước điền các thông số theo hướng dẫn của script, lưu ý là bạn điền thông tin về file cấu hình httpd.conf, thì file này là file câú hình của Web server cần xem log. và set domain cần xem log, bước này mình nhập đại cái gì cũng được, don’nt care , ví dụ là testvnlamp.com

OK, sau khi done, kiểm tra trong thư mục /etc/awstats, thấy có file awstats.testvnlamp.com.conf, đổi tên nó thành awstats.conf

Sau đó edit file đó awstats.conf

Dòng 51

LogFile thì bạn set về file cần xem ví dụ ở đây là:

LogFile="/var/log/httpd/access_log"

Tiếp dòng 203

DirData="/var/lib/awstats"

Đây là thư mục chứa data, chắc là không có thư mục này, vì mình cài dạng source not RPM nên bắt buộc phải tạo manual.

mkdir /var/lib/awstats/

Vì chúng ta sẽ config chức năng Update thông tin data bằng Web nên owner của folder này phải là user chạy Web server chứa awstats.

chown -R daemon.daemon /var/lib/awstats/
chmod 0777 /var/lib/awstats/

Dòng 153:

SiteDomain=”<domain cần xem log>”

Default awstats sẽ để là /icons nên ta phải chỉnh là, line 222

DirIcons="/awstatsicons"

Để update từ web, ta set dòng 239:

AllowToUpdateStatsFromBrowser=1

OK, các tham số khác, bạn xem mô ta để hiểu thêm.

3. Cấu hình web server chứa awstats và web server cần xem log

NOTE: Server cần xem log, thì không cần chỉnh gì, tuy nhiên nó đã được modify, khi ta chạy script setup astats ở bước 02, nó backup cho mình luôn rồi. Thông số mà nó chỉnh lại là dạng log common sang combined.

Cấu hình webserver chứa awstats

Add thêm cấu hình dưới vào file config của web server.

Alias /awstatsclasses "/home/websites/awstats/wwwroot/classes/"
Alias /awstatscss "/home/websitesawstats/wwwroot/css/"
Alias /awstatsicons "/home/websites/awstats/wwwroot/icon/"
ScriptAlias /awstats/ "/home/websites/awstats/wwwroot/cgi-bin/"
#
# This is to permit URL access to scripts/files in AWStats directory.
#
<Directory "/home/websites/awstats/wwwroot">
Options None
AllowOverride All
Order allow,deny
Allow from all
</Directory>

OK, done, vậy bạn đã xong. Restart 02 web server trên và chạy URL của web server chứa awstats. Ví dụ http://aabbcc.com/awstats/awstats.pl

Để update nhìn cái link UPDATE NOW.

Xong!

NOTE:

Nếu bạn có nhiều domain thì làm thế nào để xem.

Copy file /etc/awstats/awstats.conf thành awstats.<domain>.conf

Ví dụ cần xem thêm test2vnlamp.com thì sửa tên là awstats.test2vnlamp.com.conf và edit các thông số như trên:
- thư mục chứa data awstats
- file log
- domain

URL chạy sẽ lả:

Awstats es una aplicacion hecha en perl que nos brinda estadisticas de nuestro servidor para nuestro caso un servidor web (apache), aunque puede funcionar con otros servicios, para ponerlo en marcha debemos hacer lo siguiente:

• Instalamos:

# USE=”apache2″ emerge -va awstats

• Despues de finalizada la instalación nos muestra informacion de como usar autenticacion en awstats y aparte nos crea un directorio denominado awstats en nuestro directorio de publicacion de apache(/var/www/localhost/htdocs)

• Agregamos las siguientes lineas a /etc/apache2/httpd.conf

Alias /awstats/classes “/usr/share/webapps/awstats/6.9/htdocs/classes/”
Alias /awstats/css “/usr/share/webapps/awstats/6.9/htdocs/css/”
Alias /awstats/icon “/usr/share/webapps/awstats/6.9/htdocs/icon/”
ScriptAlias /awstats/ “/usr/share/webapps/awstats/6.9/hostroot/cgi-bin/”
ScriptAlias /awstats “/usr/share/webapps/awstats/6.9/hostroot/cgi-bin/awstats.pl”

<Directory “/usr/share/webapps/awstats/6.9/htdocs”>
Options None
AllowOverride None
#    <IfModule mod_access.c>
Order allow,deny
Allow from all
#    </IfModule>
</Directory>

<Directory “/usr/share/webapps/awstats/6.9/hostroot/cgi-bin”>
Options ExecCGI
AllowOverride None
#    <IfModule mod_access.c>
Order allow,deny
Allow from all
#    </IfModule>
</Directory>

• Reiniciamos apache:

# /etc/init.d/apache2 restart

• Creamos el archivo de configuracion de awstats para nuestro host:

# cp /etc/awstats/awstats.model.conf /etc/awstats/awstats.NroIPServer.conf

• Editamos nustro archivo /etc/awstats/awstats.NroIPServer.conf y seteamos algunos parametros

LogFormat=4 (formato de la NCSA)
SiteDomain=”NroIPServer”
Lang=”es”

• Actualizamos:

/usr/share/webapps/awstats/6.9/hostroot/cgi-bin/awstats.pl -config=NroIPServer -update

• Programamos para que genera reportes cada hora mediante cron

# crontab -e

y agregamos

0 * * * * /usr/share/webapps/awstats/6.9/hostroot/cgi-bin/awstats.pl -config=NroIPServer -update >/dev/null

One of the more irritaing things you see when you look at your AWSTATS totals each day is seeing how many other people are also looking at your stats.

If you’re running an Apache server on Mac OS 10.5.5 (or earlier), inlcuding your own personal server, there is a way to password-protect your AWSTATS folder, using your htpasswd and your httpd.conf file. This should also work for earlier versions of Mac OS X. For our model, we’re running Apache 2.8.

This is a three-step procedure, that you will perform in Terminal:

1. Creating a htpasswd file. This file will contain a user name and password, and that password will be MD5-encypted.

2. Creating a directive in the /etc/apache2/httpd.conf file. Don’t worry; it’s painless. Just be sure you backup your httpd.conf before editing it … just in case.

3. Rebooting Apache.

Step 1: Creating the htpasswd file

In terminal, either as sudo or superuser, type this, subsituting your information for the example data:

> htpasswd -cm /users/yourmacusername/.htpasswd usernameforthefile

In the example above, the -c stands for “create a file” and the “m” stands for “encrypt the password with MD 5 encryption. To sum up, we’re telling OS X to create a htpassword file, put it in the /users folder under your Mac user name, name that file “.htpassword”, and use the user name you specified. Once you enter the information above, using your own information, you will be prompted to enter a password, and you will be asked to type it again. Your file is created. Not so bad, huh? Before you ask: Yes, you can put the file anywhere you want — just don’t put it in the Apache root, or anywhere that can be reached with a web browser. If you put it in /etc/, be sure to also change the group to either “www” or “wheel.” ‘Nuff said.

Step 2: Creating the directive in /etc/apache2/httpd.conf

The httpd.conf file is a whole lot easier to read if you have a text program that can read line numbers, such as TextWrangler (free) or Smultuon (free). You can also use TextEdit, but you won’t have line numbers. And of course, you can also use the Unix text processors such as vi, pico, or Joe. Rather than give a lesson on how to use these text editors, I will just tell you what needs to be done, and you can figure out how to do it, using the text editor of your choice.

We will assume your awstats folder is in: /Library/WebServer/CGI-Executables/awstats. We will further assume that you have only put the stuff that was in the original AWSTATS wwwroot folder into that folder. In other words, we won’t have to have a complicated folder structure just to view your AWSTATS data. However, if your setup is different, just adjust the instructions below.

Open up the httpd.conf file with your text editor. If you have line numbers, you can look for Line #343. If you don’t have line numbers in your editor, search for this term (sorry, WordPress won’t let me give the exact wordage here):
CGI-Executables

Go down past that directive, which ends in /Directory (sorry, WordPress again), and add these lines. Include the lines that begin with #, which are comment lines, so you can find the section again, and know what this directive does (sorry, WordPress won’t let me use brackets to enclose the opening and closing “Directory” entries below):

# Next directive protects awstats directory
#

Directory

AllowOverride None
Options None
Order allow,deny
Allow from all
Authname “Restricted”
AuthType Basic
AuthUserFile /users/yourmacusername/.htpasswd

Require valid-user

/Directory
#
Note we did not include your password after the term “.htpasswd” in the directive above, because the user name and password are inside that file. Thus, all you need to stipulate is the file name, which is “.htpasswd”.

Step 3: Reboot Apache

Using either sudo or su, in Terminal, type:

>apachectl graceful

That’s it. You’re all done. Now, when you request AWSTATS from your server’s CGI-bin, you’ll be presented with a log-in screen where you will enter the user name and password that are in your htpasswd file. Once you enter that informaton, you will see your AWSTATS data. For security’s sake, make sure you rotate passwords, and try to use letters, numbers, etc., in your passwords so it will be extremely difficult for others to guess your password.

Now, at last, only you will see your AWSTATS data. You can, of course, also add other users to you htpasswd reparte.

These instructions should also work for those running on UNIX/Linux or Windows servers (with some modifications). The concepts are the same.

Se você está desejando tornar o AWSTATS em PT_BR para seu pessoal, acesse o arquivo:

/usr/local/cpanel /etc/awstats.conf

Procure pela linha aonde a liguagem está como “en”;

Modifique para br;

Fonte autêntica: SIERTI, Gerenciados

首先是下载awstats，这个现在是有中文网站了
解压后后放到/usr/local下
然后运行tools/awstats_configure.pl
按照提示进行配置，主要是网站的名字配置

然后是是nginx进行配置，如果是APACHE或者是IIS就不用这样麻烦了。
首先是配置nginx的日志格式

    log_format main '$remote_addr - $remote_user [$time_local] "$request" '
                      '$status $body_bytes_sent "$http_referer" '
                      '"$http_user_agent" $http_x_forwarded_for';

这个要注意其中的标点和空格。

在nginx上跑awstats需要支持fastcgi和perl才可以
fastcgi这个安装方法很多，一般是编译php5的时候直接放进去就可以了。当然我们现在为了方便就直接使用nginx-fcgi脚本http://www.nginx.eu/nginx-fcgi.html

使用脚本前需要安装下列perl模块

perl -MCPAN -e 'install "FCGI“
perl -MCPAN -e 'install "Getopt::Long"'
perl -MCPAN -e 'install "IO::All"'
perl -MCPAN -e 'install "Socket"'

然后用nginx用户执行下列命令

/usr/bin/perl /usr/local/nginx/sbin/nginx-fcgi -S /tmp/fastcgi.sock -l /home/nginx/logs/nginx-cfgi.log -pid 100005

现在新的版本需要提供pid号才可以运行，这个可以自我进行设定。

配置fastcgi_params文件，perl_fastcgi_params同fastcgi_params

vi /usr/local/nginx/cconf/fastcgi_params
fastcgi_param QUERY_STRING       $query_string;
fastcgi_param REQUEST_METHOD     $request_method;
fastcgi_param CONTENT_TYPE       $content_type;
fastcgi_param CONTENT_LENGTH     $content_length;

fastcgi_param SCRIPT_FILENAME    $document_root$fastcgi_script_name;
fastcgi_param SCRIPT_NAME        $fastcgi_script_name;
fastcgi_param REQUEST_URI        $request_uri;
fastcgi_param DOCUMENT_URI       $document_uri;
fastcgi_param DOCUMENT_ROOT      $document_root;
fastcgi_param SERVER_PROTOCOL    $server_protocol;

fastcgi_param GATEWAY_INTERFACE CGI/1.1;
fastcgi_param SERVER_SOFTWARE    nginx/$nginx_version;

fastcgi_param REMOTE_ADDR        $remote_addr;
fastcgi_param REMOTE_PORT        $remote_port;
fastcgi_param SERVER_ADDR        $server_addr;
fastcgi_param SERVER_PORT        $server_port;
fastcgi_param SERVER_NAME        $server_name;

# PHP only, required if PHP was built with --enable-force-cgi-redirect
fastcgi_param REDIRECT_STATUS    200;

然后是awstats在nginix网站配置

   server {
                listen 8000;
                root /usr/local/awstats/wwwroot;
                index index.php;

                location ~* .php$ {
                        fastcgi_pass 127.0.0.1:9000;
                        access_log /home/nginx/logs/host.access.log main;
                        include fastcgi_params;
                }

                location ~* .pl$ {
                        fastcgi_pass unix:/tmp/fastcgi.sock;
                        access_log /home/nginx/logs/host.access.log main;
                        include perl_fastcgi_params;
                }

        }

最后如果执行以下命令没有错误就可以了。有错误就根据提示来进行修正。

/usr/local/awstats/wwwroot/cgi-bin/awstats.pl -update -config=www.zauc.com

最后浏览器的访问地址是
http://IP:8000/cgi-bin/awstats.pl?config=www.zauc.com

Last August 10, 2008 – The leading SEO World Cup Challenge in Australia entry pogung177.com was hack anonymously by proxy server  or maybe from team competitors who are out there to pin down pogung177.com in order to stop him to win Busby SEO Challenge.

Busby SEO Challenge awstats of pogung77.com hack

Nobody’s responsible for the attack of pogung177.com website the leader of Busby SEO Challenge in Perth, Australia. The attacked happen August 10 to 15, 2008 pogung177.com said the bot of google.com bomb them and exceeded the bandwidth limit. But that week when we click pogung177.com it redirects to google france site ‘google.fr’.

In my personal opinion, the france team ’sphereteam.com’ a top contender of Busby SEO Challenge are massive and capable of doing unfair techniques. And, they can’t accept the things happen in the challenge that pogung177.com is leading now the SEO World Cup Challenge. Or maybe other teams too could be the perpetrator of hacking pogung177.com in the Busby SEO Challenge.

Sphereteam.com didn’t realized that they over optimized of getting inbound links from France, Europe, Australia and UK site location. The query of Busby SEO Challenge are based in California, USA datacenter of google.com. Now, the algorithm of google.com search results are very smart to weight and detect relevant results base on query string like Busby SEO Challenge keyphrase.

In Beijing, China – Olympics 2008 Phelps of USA swimming team wins eight (8) golds. He landed in Olympic history as the highest win golds for individual events.

phelps win 8 olympic golds

Find more ideas on Busby SEO Challenge hacking in Australia.

Find more on Phelps swimming update.

Setting message size in webmail

Message size limit is usually not specified in exim. Its by default 50M.

You can set message size limit to, say 60M, in /etc/exim.conf as

message_size_limit = 60M

This may not work when sending mail using webmail. Then, you need to set message size for webmail too.

In webmail, by default message size limit is 2M. You can set it to, say 60M, in /usr/local/cpanel/etc/neomail.conf as

$attlimit = 60;

That’s it.

Sharing drives using Remote Desktop Connection

To access drives of another server using Remote Desktop Connection do the following :

1. Click Start >> All Programs >> Accessories >> Communications >> Remote Desktop Connection
2. Enter the IP of the server to which you want to have connection in the box near 'Computer'.
3. Options >> Local Resources tab
4. Under 'Local Devices' click 'Disk Drives' >> Connect 

5. Click 'Ok' if you get the warning prompt.

When you click connect all the information is stored in a file Default.rdp.

In this way you can transfer files very easily from one server to another server as you are doing in a single server.

Just Copy, then Paste.

Unique visits in stats

The statistics softwares like Awstats and Google Analytics show “unique visits”. What is this unique visit ?

In an absolute sense, you could define a “unique” as a visit to the site (and nothing more) that never occurred before.

The part “that never occurred before” would present some concern for the analysis because it would need to have a history of previous visits to reference. Something that could be impractical from a storage perspective. The other problem is how you would clearly identify a “unique”, except by way of a cookie which is in itself problematical considering that cookies can be turned off or eradicated before subsequent visits.

Awstats measures “unique” visit as : A unique visitor is a host that has made at least 1 hit on 1 page of your web site during the current period shown by the report. If this host make several visits during this period, it is counted only once.

Google Analytics tracks it a different way. In Analytics,the “initial session by a user during any given date range is considered to be a unique visit”. Any additional visits during the selected time period are counted as visits, but not as unique visits.

Php error

You may get the error that is given below while accessing a php page.

Warning: require() [function.require]: URL file-access is disabled in the server configuration in /home/username/public_html/index.php on line 6

Warning: require(http://www.domain.com/includes/header.php) [function.require]: failed to open stream: no suitable wrapper could be found in /home/username/public_html/index.php on line 6

Fatal error: require() [function.require]: Failed opening required 'http://www.domain.com/includes/header.php' (include_path='.:/usr/lib/php:/usr/local/lib/php') in /home/username/public_html/index.php on line 6

Create a php.ini file in all the directories of the domain with following lines:

allow_url_include = On

allow_url_fopen = On

Otherwise, set it globally in the server.

Thats it. This should work.

Unable to login to PhpMyAdmin

If you are not able to login to PhpMyAdmin using root or user’s login details you can try doing these options :

1. Give privileges to ‘root’ user in mysql.

mysql --user=root mysql -p
mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'localhost' IDENTIFIED BY 'xxxx' WITH GRANT OPTION;
mysql> GRANT ALL PRIVILEGES ON *.* TO 'root'@'%' IDENTIFIED BY 'xxxx' WITH GRANT OPTION;

2. Give privileges to customer’s ‘username’ in mysql.

mysql> GRANT ALL PRIVILEGES ON *.* TO 'username'@'localhost' IDENTIFIED BY 'xxxx' WITH GRANT OPTION;
mysql> GRANT ALL PRIVILEGES ON *.* TO 'username'@'%' IDENTIFIED BY 'xxxx' WITH GRANT OPTION;

3. If both do not allow you to login in PhpMyadmin, check the conf file of phpMyadmin, /var/www/html/phpMyAdmin/config.inc.php. Check the line

$cfg['Servers'][$i]['user']            = 'phpmyadminusername';
$cfg['Servers'][$i]['password']        = 'xxxxx';

Give privileges to ‘phpmyadminusername’ in mysql.

mysql> GRANT ALL PRIVILEGES ON *.* TO 'phpmyadminusername'@'localhost' IDENTIFIED BY 'xxxx' WITH GRANT OPTION;
mysql> GRANT ALL PRIVILEGES ON *.* TO 'phpmyadminusername'@'%' IDENTIFIED BY 'xxxx' WITH GRANT OPTION;

This should work.

Installing awstats is little complex in centOS whereas i’ve installed awstats easily in my FC9 following this instruction but failed to do the same in centOS. So here is the whole process to follow and setup awstats in centOS .

Step 1: Download the awstats rpm (awstats-6.6-1.el5.rf.noarch.rpm) from here and place it in your server
Step 2: Login to the server with SSH and run awstats from command prompt. To run awstats, go to that directory where you have placed the awstats rpm and type
rpm -ivh awstats-6.6-1.el5.rf.noarch.rpm

Step 3: Now go to the /etc/awstats/ directory and copy the file named awstats.localhost.localdomain.conf and paste it in the same directory with different name. The file name should be awstats.your_domain_name.conf. (let’s consider mine one is awstats.abc.conf). In order to do this, go to that specific directory and type

cp awstats.localhost.localdomain.conf /etc/awstats/awstats.Your_domain_name.conf

Step 4: Now Open that file and find the word “SiteDomain=”Localhost.Localdomain” in that file and replace the domain name with your domain name. suppose it was abc
SiteDomain = “abc”
Save that file when you are done and go back to command prompt.

Step 5: Now go to /var/www/awstats/ directory and create 2 file named
awstats062008.abc.txt (I.e: modify with current date) &
awstats062008.abc.bak (I.e: modify with current date)

Step 6: After that, run the following command which will create a html file.
perl awstats.pl -config=Your_domain_name -output -staticlinks > awstats.Your_domain_name.html
and finally run the following command in the command prompt.
perl awstats.pl -config=your_domain_name -update

Step 7: Now open a browser and in the URL and type
http://your_server_ip/awstats/awstats.pl?config=your_domain_name

Step 8: If page is not populating with proper records which indicates that your access_log is not populating properly. So open vhosts.conf file which is located in the /etc/httpd/conf.d/ direcotry and comment out 2 lines about access_log and error_log of that specific domain. Save and close that file and follow step6 again. Hope, everything will work properly now.

That’s all.