The apache logs can be found in
<code>/usr/local/apache/logs</code>.
The file <code>access_log</code> contains the most
recent accesses.
The file <code>error_log</code> contains the most 
recent errors.
<p>Apache is configure to rotate the logs every night
with <a href="http://www.ford-mason.co.uk/resources/cronolog/">Cronolog</a>
<p> Currently, we are using Accesswatch to
<a href="/accesswatch">analyze the logs</a>.
<p> Every year, we use Webtrends to generate stats
for the GSRC PI, See
<a href="/infrax/faq/168.html">Web site statistics</a>.

<p> For further information about Apache and Accesswatch, see
<a href="/infrax/sysadmin/httpd.htm">The Infrax httpd page</a>

<p>See <a href="/infrax/faq/55.html">Where are the MySQL logs?</a>
for information about the MySQL logs.
<p>See /var/log/php.log contains php log messages.
<p>&nbsp;

JohnR writes:
<blockquote>
    I found what appears to be an interesting bug in Apache,
    which is that it won't start if the rewrite log file
    reaches 2.147something Gigs, a number that sounds to me
    suspiciously close to 2^32 (or is it 2^31?).
    
    This log is useful for debugging purposes, and I think
    it's probably worth keeping around a week's worth or so.
    Christopher, is it easy to rotate logs like this on a
    weekly basis and only keep the last two weeks? This would
    be useful for the database logs as well.
</blockquote>

I finally got around to doing this.
I edited /usr/local/apache/conf/rewrite.conf, and commented out
the old RewriteLog value, and added a new one
<pre>
# Logs are managed by cronolog http://www.ford-mason.co.uk/resources/cronolog
#RewriteLog logs/rewrite.log
RewriteLog "|/usr/local/cronolog/sbin/cronolog -l /usr/local/apache/logs/rewrite_log /usr/local/apache/logs/%Y/%m/%d/rewrite_log"
</pre>

<p>To clean up the files, I added /usr/local/adm/crontab.clean.server,
which removes all rewrite_logs files older than 14 days in 
/usr/local/apache/logs/`date +%Y`

That script is run by a cronjob as root:
<pre>
5 4 * * * /bin/csh /usr/local/adm/crontab.clean.server > /dev/null 2>&1
</pre>

The script does some other cleaning too.