1. Make sure your server uses standard or extended log files.

   Currently AccessProbe does not support NT log files.

   If you are not sure what type of server you are using

   contact your service provider.



2. Make sure the path to your log file is correct.

   If you do not know the full path to your log file

   telnet to your server, navigate to your log dir, and type "pwd".

   Usually the log dir is one directory up from your root web dir.

   If you do not have access to your log directory

   contact your service provider.

If you are receiving error messages please consult the Common Errors section of this document.

User Interface menu

What do all these buttons do?
Starting from the top (we'll skip the help button since obviously you found it!)

Relative-Date - Check this radio button if you want to use relative dates to view your stats. Relative Dates make it very simple to view log info for today, yesterday, this week, this month and more. Simply select the relative date you wish to view after checking the relative-date button and press the show stats button.

Date-Range - If you want to view your stats for a date range not covered in the relative-date list use the date range option instead. Check the Date-Range radio button and enter a starting and ending date in the provided fields (Starting date on top). The date range function will display your stats for the starting date up to and including the ending date.
Supported date formats are 11/5/99, 11/05/1999, 11-5-99, Nov 5 1999, 5 november 99 - pretty much every possible date format

Read Type - These radio buttons determine how AccessProbe reads your log file.

> read forward - forces AccessProbe to read your log from the begining to the end. If you have a really large log file and want to see stats for today then reading your log forward wouldn't make much sense. The read forward function is faster than the read backwards option on a per record basis. This option will always display up to the second results.

< read backwards - Normally reading your log backwards is much faster than reading it forward. Reading the log backwards is slower on a per record basis, but usually requires reading less data. For example if your log is 10 days old and grows 5 megs a day, you would have to read 50 megs of data forward but only 5 megs backwards if viewing todays records.
The read backwards function caches data and therefore may not always display up to the second data.
Auto - Tries to determine the fastest way to read your logs based on the current date selection.

Max / all - These two options determine how many records for each of the selected reports is returned. If you want to see 50 items for each of the selected reports, this is how you do it.
Check the all option if you want to see every item in the currently selected reports.
Note: Selecting the all option can generate very large reports.
Changing the max value will not effect the averages contained in the header of each report. The averages for each report are based on every item in the report, not just those being viewed.

Show Stats - Click this button to generate your stats.
CMP - Display a compact report for printing.
currently this option only works for main reports.
Configure - Click this button to change AccessProbe's Configuration.
CleanLog - Click this button to Clean your logfile.

The Reports
Standard Log Format
• Hits per Page - Shows the number of hits for each page on your site.
• Hits per Machine - Shows the number of hits per visitor. Machine hits give a more accurate picture of site activity.
• Hits per Domain - Shows the number of hits per top level domain. Currently AccessProbe does not resolve top level domain names. Most servers will set your log to resolve host names if asked.
• Hits per Week - Displays hits organized by week of year.
• Hits per DayofWeek - Displays hits organized by the day of week: mon,tue,wed, etc.
• Hits per Date - Displays hits organized by date. (what day this week did you recieve the most hits?)
• Hits per Hour - Displays hits organized by hour. (what is the most popular hour for your site?)
• Authenticated Users - If you have httpasswd protected files this will show you who is logging in.
  Requires Extended(Combined) Log format - If you can't see the following ask your ISP for extended logs.
• Referring Pages - Shows you where your hits are coming from.
• Browser - See what Browsers your visitors are using.
• Operating System - See what Operating Systems your visitors are using.
• Query String - This displays The querry info from referring pages (How are visitors finding your site?)

Configuration menu

Image Dir - This is only used if you can't see images in AccessProbe.
Some server configurations do not allow images in the cgi-bin. If your server does not allow images in the cgi-bin, and you are running AccessProbe from the cgi-bin, then you will need to move the APimage directory out of your cgi-bin. After you move the APimage dir to a web directory that supports images type either a relative path to the APimage dir, or an absolute url to the APimage dir in this field.
We recommend placing the APimage dir in your root web directory so that you can simply type your-url.com/APimage do not put a trailing / in this field.

Log File Path - Enter the full server path to your log file here.
This will be something like /usr/home/local/etc/httpd/logs/access_log or /home/u/user/logs/yourdomain.com
The above are just examples, if you do not know where your log directory is contact your ISP.
If you know where your log file is, but do not know the full path:
1. Telnet to your account
2. Navigate to your log directory
3. Type PWD - this will return the full path to the current dir.

Remove List - If there are certain items you do not wish to view, type them here as a comma seperated list.
Do not include spaces between the commas (unless it is part of the search string), and do not put a comma as the first or last character. Putting a comma as the first or last character will remove everything.

Common Errors menu

Below is a list of common errors, meanings, and possible solutions

Internal Server Error - The server encountered an internal error or misconfiguration and was unable to complete your request.
The server cannot execute index.cgi - This usually means that either your server is not running perl 5.004 or the path to perl 5.004 on your server is different than the path to perl contained in index.cgi

1. Verify that you have perl 5.004 running on your server.

   Telnet to your server and type perl -v this will return the

   version of perl your server is running. It is possible to

   have more than one version of perl running on one server,

   so contact your service provider if the version returned by

   perl -v is not version 5.004 and ask if perl 5.004 is running

   on the server.



2. Verify that the first line of index.cgi contains the proper

   path to perl on your server. Telnet to your server and type

   "which perl". This will return the path to perl on your server.

   If you need to modify the path to perl in index.cgi make

   sure that you use a UNIX friendly text editor.

   If you have multiple versions of perl on your server make

   sure you use the path to perl 5.004.

Forbidden - You don't have permission to access /test/accessprobe/index.cgi on this server.
You do not have permission to execute index.cgi

1. Make sure that the accessprobe dir and index.cgi

   are both set to chmod 0755.

   On some servers, executables can only be run in the cgi-bin.

   Try installing accessprobe in your cgi-bin.

   If you keep receiving this error after trying the above,

   contact your service provider.

ERROR: The data Dir is not writable, please chmod to 0744
AccessProbe does not have write access to your accessprobe directory

1. Make sure that the accessprobe dir is readable/writable/executable.

   Chmod your accessprobe dir to 0755.

   If this doesn't work try using 0777 instead of 0755.

   If you can't change permissions for your log file or directory,

   contact your service provider.

ERROR: config.db File is not writable, please chmod to 0744
AccessProbe can't write to the accessprobe/data/config.db file

1. Make sure that the accessprobe dir is readable/writable/executable.

   The first time you run accessprobe a data directory is created

   in your accessprobe directory with read/write access.

   Chmod your accessprobe dir to 0755.

   Chmod your accessprobe/data dir to 0744.

   Chmod your accessprobe/data/config.db file to 0744.

   Note: If the accessprobe dir was not writable then the

           accessprobe/data dir and config.db file will not exist.

           Just chmod the accessprobe dir and re-run index.cgi.

   If this doesn't work try using 0777 instead of 0744 and 0755.

   If you can't change permissions for your log file or directory,

   contact your service provider.

ERROR: Can't open log
AccessProbe does not have read access to your log file

1. Make sure that your log file and log dir are readable/writable.

   Chmod your log file and dir to 0744.

   If this doesn't work try 0777.

   If you can't change permissions for your log file or directory,

   contact your service provider.

ERROR: Couldn't create temp log file - chmod log dir to 0744
AccessProbe will not clean your logs if it can't make a backup.

1. Make sure that your log dir is readable/writable.

   Chmod your log dir to 0744.

   If this doesn't work try 0777.

   If you can't change permissions for your log file or directory,

   contact your service provider.