You look to diverse occurrences of this filament in the /var/log/httpd/access_log dossier.
::1 – - [29/Nov/2006:17:39:04 -0800] GET / HTTP/1.03 200 14083 – Apache/x.y.z. (Fedora) (internal idiot connection)
or
::1 – - [29/Nov/2006:17:39:04 -0800] GET / HTTP/1.03 200 14083 – Apache/x.y.z. Your httpd.conf has damage values since Max and Min supernumerary servers.
(CentOS) (internal idiot connection)
What does this close-fisted?
It is an internal apache appliance to haft the issue of children.
InternalDummyConnection Requests From the Server to Itself
When the Apache HTTP Server manages its uninitiated handcuff processes, it needs a practice to wake up processes that are listening since different connections. This apply for ordain be included in the access_log dossier with the indifferent start make up to the loop-back interface (typically 127.0.0.1 or as usual::1 if IPv6 is configured). To do this, it sends a forthright HTTP apply for indifferent to itself. If you log the User-Agent limitations (as in the combined log format), you ordain look to the server signature followed before (internal idiot connection) on non-SSL servers.
These requests are flawlessly infinite and you do not, in shared, difficulty to fret fro them. During unquestioned periods you may look to up to a distinct such apply for since each httpd uninitiated handcuff dispose of.
If you fondness to exclude them from your log, you can despise infinite conditional-logging techniques.
In 2.2.6 and earlier, in unquestioned configurations, these requests may become manifest to a heavy-weight zealous trap leaf and inception dispensable saddle with on the server.
For representative, to bound all requests from the loopback interface from your logs, you can use
SetEnvIf Remote_Addr 127\.0\.0\.13 loopback
and then escort on proliferating env=!loopback to the rubbish of your CustomLog directive. You can reject this before using mod_rewrite to rejoin with a redirect when accessed with that exact User-Agent or IP start.
If you are seeing scads uninitiated handcuff processes beget and degenerate, you may require to partake of a look at your MinSpareServers and MaxSpareServers directives, and your MaxRequestsPerChild.
It’s away since Apache to signal its children that it’s lifetime to degenerate.This is as usual nothing to be anxious fro. You may also difficulty to make up MaxSpareServes to a value greater than MinSpareServers. Later, if it is an point, you may difficulty to restart Apache or the server since honour seepage point.
You may difficulty to proliferating the value to a higher unmistakable to reject this.