[NBLUG/talk] How to read logwatch & httpd access_log

Dave Sisley dsisley at sonic.net
Thu Jan 13 08:27:57 PST 2005

Hey, Lugglies:

[warning: this turned out to be a longer post than I thought.  Extra
points for reading the whole thing!] 

Bit by bit, I'm trying to learn to sift through the info that logwatch
sends to me each morning.  I got a lot of useful info from the list
here with figuring out the sshd messages I was getting in logwatch
(thanks!), and now I'm curious about the messages from httpd.

I'm referrring here to a Fedora Core 2 box.  I'm just running logwatch
as it came 'out of the box'; I haven't configured it in any way.

On a fairly regular basis (but not every day), I get an entry in
logwatch that looks like this (in the httpd section):

Connection attempts using mod_proxy: -> : 8 Time(s)

I've been ignoring this since my httpd server isn't running
mod_proxy. Hmmm. Or at least I don't think so.  I see this in my
httpd.conf file:

LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so

Then further down, I see that the Proxy Server directives are all
commented out:

# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#<IfModule mod_proxy.c>
#ProxyRequests On
#<Proxy *>
#    Order deny,allow
#    Deny from all
#    Allow from .your-domain.com

# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
#ProxyVia On

# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
#CacheRoot "/etc/httpd/proxy"
#CacheSize 5
#CacheGcInterval 4
#CacheMaxExpire 24
#CacheLastModifiedFactor 0.1
#CacheDefaultExpire 1
#NoCache a-domain.com another-domain.edu joes.garage-sale.com

# End of proxy directives.

So my first assumption is that mod_proxy is NOT running on my server.

I've also googled and run host on that IP address logwatch entry
( which resolves to proxyscan.freenode.net.  I went to
freenode.net and poked around, and they state that they will probe
machines that use their servers.  This is afterall the server that
hosts (if that's the right word) the NBLUG chat room.

My second assumption is that I don't really need to worry about that
IP address, since it's part of using #nblug.

My real question (finally!) has to do with my access_logs, which
logwatch parses to make its report.  I saw in google that successful
CONNECTs (200) might indicate trouble.  I see plenty of connects from, which I think is okay, but I see a couple like this that
make me nervous:

access_log: - - [09/Jan/2005:19:04:28 -0800] "CONNECT HTTP/1.0" 200 12551 "-" "-"
access_log.1: - - [06/Jan/2005:20:50:47 -0800] "CONNECT HTTP/1.0" 200 12550 "-" "-"
access_log.3: - - [20/Dec/2004:17:09:02 -0800] "CONNECT HTTP/1.0" 200 12596 "-" "-"

Obviously somebody wants to w00t me (or 'own' me, or whatever it is
these hooligans call it).  What's interesting (or scary) is that these
messages are in my log file, but they don't seem to be reported by
logwatch (unless I'm misreading it).

Do I have something to worry about, and if so - what do I do about it?

Thanks in advance for the help!

Dave Sisley
dsisley at sonic.net

More information about the talk mailing list