Forum Moderators: phranque

Message Too Old, No Replies

Apache dummy connections

         

cnapsys

7:42 am on Apr 16, 2012 (gmt 0)

10+ Year Member



Hey all,
I'm experiencing something weird.
About a month ago we have completely redesigned one of our clients website.
About 3 days later Apache was down. Checked the err_logs and it showed that MaxClients limit was reached.
Increased it from 256to 1024. This kept the server up for about a week after which it crashed again.
I installed mod_status and initially everything looked fine.
Though I realized 24 hrs later that it was ok initially because I checked it right after a server reboot.
so 24 hrs later I began to see these:

38-0 - 0/0/4 . 0.00 6055 0 0.0 0.00 0.06 ::1 severname.com OPTIONS * HTTP/1.0

where servername.com is the server name assigned by the datacenter.

Lots of them...

I did a bit of research and everyone said these are harmless and they can be ignored as they are just dummy connections from the server itself checking on Apache to see whether it's up or not.
The status of these requests do seem to be "." Open slot with no current process, but what worries me is that they keep stacking up.

After 24 hrs there were only 18, after 48 hrs there were 54, after 72hrs there were 172 of these.
So I'm thinking that these may actually clog apache and cause it to hit its maxclients limit and crash.

The error logs only show when maxclients was reached and crashed nothing else.

Furthermore, I don't think the redesign of the clients website is causing this as the requests coming through that domain seem to process just fine, close and disappear after a couple of minutes.
While these requests that keep staying on seem to be made directly through the server name assigned by the datacenter.

Any idea what may cause this or any suggestions on how to further track this down?

Thank you for your time and have a great day all.

T

lucy24

9:59 am on Apr 16, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member Top Contributors Of The Month



The error logs only show when maxclients was reached and crashed nothing else.

Are you in debug mode (highest detail level)? Not that your server really needs one more thing to tie up its resources, but are you extracting all possible information?

enigma1

1:04 pm on Apr 16, 2012 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



Check the version you have:
In 2.2.6 and earlier, in certain configurations, these requests may hit a heavy-weight dynamic web page and cause unnecessary load on the server

[wiki.apache.org...]

And also check the apache connection timeouts, make sure you don't leave them open for too long. 1024 for the maxclients doesn't sound right. Did you actually calculated the value against your available resources and adjusted the other related directives also, or you put a number there?

About a month ago we have completely redesigned one of our clients website.

It's also possible that some code you added wastes connections.