Tarotoast’s Stuff

Plesk 7.5 for Windows comes with Awstats, why not Linux version? Who knows, ask the developers. It is said on one of the forum page that Plesk 8.0 for Linux will come with Awstats supported. Again, who knows when it will be out.

So instead of waiting for Plesk to integrate Awstats, I just want it working. Several things to notice while installing Awstats on the FC2 Root Servers that 1&1 is shipping:

1. Extract the source and place them at /usr/local/awstats as the installer will expect itself to be there.
2. When asked to locate httpd.conf, feed it /etc/httpd/conf/httpd.include instead. If you give httpd.conf, changes made will be erased next time you made any change to your domain structures through Plesk.
3. Edit httpd.include and add this block to the awstats’s Directory block:

   	<IfModule mod_perl.c>
   	<Files ~ (\\.pl$)>
   		SetHandler perl-script
   		PerlHandler ModPerl::Registry
   		Options ExecCGI
   		allow from all
   		PerlSendHeader On
   	</Files>
   	</IfModule>
   

   As this will make sure perl scipts runs under 1&1’s and Plesk’s configuration.

4. Logs are located under /home/httpd/vhosts/[domain]/statistics/log/access_log, notice if you’re not running the update script (awstats_updateall.pl whichcalls awstats.pl) as root, you’ll have to chmod o+x on these directories.
5. Awstats expect (by default) to write into /var/lib/awstats so make sure it’s there and writable for update script owner.
6. If you want to import old data, specify the target log file access_log.processed, and update. Then change the target log file back to access_log to keep it current.
7. Because the data get processed by Plesk’s default stats engine, we want to regularily check access_log to keep the data updated (so it won’t be moved into .processed before we access them). Use crontab -e to automate this process every hour.

It’s working on mine now.

Taken directly from Phoenix Labs’ website:

PeerGuardian 2 is Phoenix Labs’ premier IP blocker for Windows. PeerGuardian 2 integrates support for multiple lists, list editing, automatic updates, and blocking all of IPv4 (TCP, UDP, ICMP, etc), making it the safest and easiest way to protect your privacy on P2P.

In this case, however, the platform dealing with is Linux. So here are the steps.

1) PeerGuardian Linux 1.5 beta Source
Grab it from the links on [this thread]
Extract it to a folder and run:
./configure

2) Automake-1.4
As it is required to compile properly, the easiest workaround is to make a symlink to point automake-1.4 to automake-[version] with the command:
ln -s /usr/share/automake-[version]/ /usr/share/automake-1.4

3) libipq.h:
This library is not included in my preconfigured system. Grab the rpm [here]
rpm -iv iptables-devel-1.2.9-1.0.i386.rpm works just fine.

4) curses.h:
This is also missing according to the error message while compiling, so I found it [here]. rpm -iv all the way.

5) Install & Update
Easiest way to get it working is to copy/link the binary into your path, and put the PG.conf under /etc. Here is a [thread] dedicated to this topic.

It should work, and do what you wanted to do with it.