Apache2.2 Error Logs - File Does Not Exist
On my Apache2.2 error logs for one of my virtual hosts, I am receiving all sorts of "File does not exist" for things like "/blog" which doesn't exist - nor do I want it. What is causing all these files not found? There are A LOT of lines so I will only post some of them. Thanks!
[Mon Oct 08 09:35:44 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:44 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:45 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:45 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:46 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:47 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:47 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:48 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:49 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:49 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:25 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:25 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:26 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:26 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:27 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:27 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:27 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:28 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:12 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:13 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:13 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:14 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:14 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:14 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:15 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:15 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:16 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:16 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:19 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:20 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:20 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:20 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:21 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:44 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:44 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:45 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:45 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:46 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:47 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:47 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:48 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:49 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:35:49 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:25 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:25 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:26 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:26 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:27 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:27 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:27 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 09:40:28 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:12 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:13 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:13 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:14 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:14 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:14 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:15 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:15 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:16 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:16 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:19 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:20 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:20 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:20 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
[Mon Oct 08 10:47:21 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/site_n
Blaz
Someone (or more people or some web crawler programs, ...) is requesting a file/folder that does not exist. He gets an error 404 and the error is also written to the log. Nothing more to it than that.
ASKER
Well, even on my development server which is not public, I have the same errors. There is not a spider or crawler looking at those files... or did I misunderstand you?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Well, the 192.168.*.* is a static IP on the internal LAN... all our internal IPs start that way. I do not run phpmyadmin, mysql, or any of those other "not found" things. My dev server is Windows 2003 Server Edition with tight security. It has backup software, virus scanners, etc. My dev server IP is the 192.168.12.1. Additionally, I only get these errors when I restart Apache (or reboot - start Apache). I am 100% confident that no one is accessing the server other than through HTTP. I access it through Remote Desktop, Shared Folders, or - most commonly - VM Infrastructure as the machine is really just a VM. The only other people who access that server are the project managers who use the HTTP protocol to connect and they aren't searching for things like <root>/blog - trust me.
The development server is behind the corporate firewall which is strict as... well it's strict/annoying. The only users who have security to the server are the administrators (which is our network admins and myself). I also can access it using my network login to the local domain through Shared Folders (i.e. CompanyDomain\UserID).
The "attacks" are on the development server and my redundant "live web servers" in the DMZ. So, there's firewalls infront and behind.
It seems unlikely that it is a "script kiddie", but ... any suggestions?
Thanks!
The development server is behind the corporate firewall which is strict as... well it's strict/annoying. The only users who have security to the server are the administrators (which is our network admins and myself). I also can access it using my network login to the local domain through Shared Folders (i.e. CompanyDomain\UserID).
The "attacks" are on the development server and my redundant "live web servers" in the DMZ. So, there's firewalls infront and behind.
It seems unlikely that it is a "script kiddie", but ... any suggestions?
Thanks!
You didn't quite understand what grahamnonweiler and I were suggesting. OK, because it is happening on the LAN makes it a bit different but anyhow:
- no mater how tight security you have on your server (virus scanners, firewalls, ...) you are letting through all http traffic, right?
- the errors suggest that someone is probing various urls - possibly probing for server vulnerabilities
- the someone could be a virus or spyware on any machine in the network which has http access to this server
- the someone could even be a security vulnerability scanner on your network or some other product.
Could you describe more:
- from which server were the error logs you posted? What IP does it have? Is it in DMZ or on your LAN?
- what does Apache access log say for the times you get that errors?
- no mater how tight security you have on your server (virus scanners, firewalls, ...) you are letting through all http traffic, right?
- the errors suggest that someone is probing various urls - possibly probing for server vulnerabilities
- the someone could be a virus or spyware on any machine in the network which has http access to this server
- the someone could even be a security vulnerability scanner on your network or some other product.
Could you describe more:
- from which server were the error logs you posted? What IP does it have? Is it in DMZ or on your LAN?
- what does Apache access log say for the times you get that errors?
Based on the description from damijim - in that as soon as he starts Apache these entries appear - and that he is running under VMWare - then it is most probably a "security vulnerability scanner" that is being run by the network admins.
If this is the case then the scanner will have access to both "public" and "local" servers - regardless of whether they are virtual or live.
The most important this to understand damijim - is that both Blaz and myself are trying to tell you that this traffic is based on HTTP access to Apache - so if someone typed in http://192.168.12.1/phpMyAdmin then it would show up as a 404 error in your Apache logs.
A security vulnerability scanner sends out these type of requests continually (or a periodic basis) to ensure that no one has created a "security hole" on the company's server. If the scanner is mis-configured it could be running constantly and in which case find the network administrator who installed it and get them to configure it correctly.
If this is the case then the scanner will have access to both "public" and "local" servers - regardless of whether they are virtual or live.
The most important this to understand damijim - is that both Blaz and myself are trying to tell you that this traffic is based on HTTP access to Apache - so if someone typed in http://192.168.12.1/phpMyAdmin then it would show up as a 404 error in your Apache logs.
A security vulnerability scanner sends out these type of requests continually (or a periodic basis) to ensure that no one has created a "security hole" on the company's server. If the scanner is mis-configured it could be running constantly and in which case find the network administrator who installed it and get them to configure it correctly.
ASKER
I appreciate the help you all. I will talk to the network admins and see if they run a "vunerability scanner".
Blaz - I will provide you with the information in about an hour. I'm about to leave for work once I get my new PC up and going. (It's a sweet Core 2 Duo, 2GB 800Mhz DDR2, ASUS mobo, cheap video card, 7200rpm SATA WD. I had to build it on a budget, but it beats my 2 year old Sony Vaio VGN-A290 like crazy. Sorry, had to gloat for a moment... just woke up. ;P)
Blaz - I will provide you with the information in about an hour. I'm about to leave for work once I get my new PC up and going. (It's a sweet Core 2 Duo, 2GB 800Mhz DDR2, ASUS mobo, cheap video card, 7200rpm SATA WD. I had to build it on a budget, but it beats my 2 year old Sony Vaio VGN-A290 like crazy. Sorry, had to gloat for a moment... just woke up. ;P)
ASKER
Blaz -
1) The error logs I posted were from one of the DMZ servers. It's VM-IP is 192.168.12.80, but under network connections in Windows it is assigned the static ip of 65.83.xx.xx . (Sorry for the .xx.xx, but the site is live, but under development and marketing wouldn't like me posting the site yet.)
2) 192.168.12.1 is the Default Gateway for that web server. I'm confused now.
On my development (internal) server.
1) The error logs look a little different, example:
"[Fri Sep 28 09:45:39 2007] [error] [client 172.16.56.44] File does not exist: D:/Apache2.2/htdocs/procor
-which is standard/normal. 172.16.56.44 is my static IP on the LAN/domain.
So, I guess the problem is mainly my DMZ servers.
DMZ Error Log:
[Mon Oct 08 10:47:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:26 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:29 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:29 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:30 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:30 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:31 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
The last line in my access.log is:
192.168.12.1 - - [28/Sep/2007:16:07:18 -0400] "GET / HTTP/1.0" 403 202
192.168.12.1 - - [28/Sep/2007:16:07:20 -0400] "GET / HTTP/1.0" 403 202
192.168.12.1 - - [28/Sep/2007:16:07:22 -0400] "GET / HTTP/1.0" 403 202
192.168.12.1 - - [28/Sep/2007:16:07:34 -0400] "GET / HTTP/1.0" 403 202
Maybe I should review my httpd.conf again or check out the other redundant server in the DMZ.
Any suggestions would be appreciated!
1) The error logs I posted were from one of the DMZ servers. It's VM-IP is 192.168.12.80, but under network connections in Windows it is assigned the static ip of 65.83.xx.xx . (Sorry for the .xx.xx, but the site is live, but under development and marketing wouldn't like me posting the site yet.)
2) 192.168.12.1 is the Default Gateway for that web server. I'm confused now.
On my development (internal) server.
1) The error logs look a little different, example:
"[Fri Sep 28 09:45:39 2007] [error] [client 172.16.56.44] File does not exist: D:/Apache2.2/htdocs/procor
-which is standard/normal. 172.16.56.44 is my static IP on the LAN/domain.
So, I guess the problem is mainly my DMZ servers.
DMZ Error Log:
[Mon Oct 08 10:47:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:23 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:24 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:26 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:29 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:29 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:30 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:30 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
[Mon Oct 08 10:47:31 2007] [error] [client 192.168.12.1] File does not exist: D:/Apache2.2/htdocs/procor
The last line in my access.log is:
192.168.12.1 - - [28/Sep/2007:16:07:18 -0400] "GET / HTTP/1.0" 403 202
192.168.12.1 - - [28/Sep/2007:16:07:20 -0400] "GET / HTTP/1.0" 403 202
192.168.12.1 - - [28/Sep/2007:16:07:22 -0400] "GET / HTTP/1.0" 403 202
192.168.12.1 - - [28/Sep/2007:16:07:34 -0400] "GET / HTTP/1.0" 403 202
Maybe I should review my httpd.conf again or check out the other redundant server in the DMZ.
Any suggestions would be appreciated!
ASKER
Also, I checked the other two DMZ servers that host cobbenergy.com and cobbemc.com that I configured as well, and they do not have the same problem. They have different IPs, but use the same gateway. If that information helps at all. Thanks.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Correct.
So, any ideas why it is searching for paths on my 2 redundant DMZ VM servers? It doesn't do this on the other DMZ VM servers hosting our other sites.
So, any ideas why it is searching for paths on my 2 redundant DMZ VM servers? It doesn't do this on the other DMZ VM servers hosting our other sites.
ASKER
Alright, I talked to IT of our parent company who hosts the VMs/servers. He said it's the load balancer running health checks on the system. Is there anyway to configure httpd.conf to ignore these 404 requests from the 192.168.12.1?
In general - no. But it is quite easy to configure yourself to ignore these 404 errors in the log :-)
Maybe you could do some rewrites to check for these standard probing URLs and redirect them to a page (see mod_rewrite). But probably this would cause an alarm in your IT department - a security leak URL address would respond to the requests.
Maybe you could do some rewrites to check for these standard probing URLs and redirect them to a page (see mod_rewrite). But probably this would cause an alarm in your IT department - a security leak URL address would respond to the requests.
ASKER
yeah, too bad they gave me a Windows 2003 Server edition this time. If I got Linux I could just strip out those lines before reviewing the log.
I want to see the 404 errors incase there really is an issue at some point. Anyway, thanks again for your help! :)
I want to see the 404 errors incase there really is an issue at some point. Anyway, thanks again for your help! :)