« 关于自动PGA管理的进一步探讨 | Blog首页 | It168急聘 频道主编 »
What's Mean "internal dummy connection"?
作者：eygle | 【转载请注出处】|【云和恩墨 领先的zData数据库一体机 | zCloud PaaS云管平台 | SQM SQL审核平台 | ZDBM 数据库备份一体机】
链接：https://www.eygle.com/archives/2006/04/whats_mean_internal_dummy_connection.html
链接：https://www.eygle.com/archives/2006/04/whats_mean_internal_dummy_connection.html
升级到Apache2.2之后,在Apache的日志中经常看到大量的internal dummy connection日志:
| [root@systest logs]# tail -f access_log.20060409 |grep "internal dummy connection" ::1 - - "GET / HTTP/1.0" 200 68091 "-" "Apache/2.2.0 (Unix) PHP/5.1.2 (internal dummy connection)" ::1 - - "GET / HTTP/1.0" 200 68091 "-" "Apache/2.2.0 (Unix) PHP/5.1.2 (internal dummy connection)" ::1 - - "GET / HTTP/1.0" 200 68091 "-" "Apache/2.2.0 (Unix) PHP/5.1.2 (internal dummy connection)" ::1 - - "GET / HTTP/1.0" 200 68091 "-" "Apache/2.2.0 (Unix) PHP/5.1.2 (internal dummy connection)" ::1 - - "GET / HTTP/1.0" 200 68091 "-" "Apache/2.2.0 (Unix) PHP/5.1.2 (internal dummy connection)" ::1 - - "GET / HTTP/1.0" 200 68091 "-" "Apache/2.2.0 (Unix) PHP/5.1.2 (internal dummy connection)" |
不知道是什么意思?哪位能指点一下,谢谢:)
感谢留言网友的指点，这些信息的含义为:/* Create the request string. We include a User-Agent so that通过修改Apache的配置文件可以在日志中屏蔽这些信息:
* adminstrators can track down the cause of the odd-looking
* requests in their logs.
*/
srequest = apr_pstrcat(p, "GET / HTTP/1.0\r\nUser-Agent: ",
ap_get_server_version(),
" (internal dummy connection)\r\n\r\n", NULL);
SetEnvIf Remote_Addr "::1" dontlog参考链接:
CustomLog "|/usr/local/sbin/cronolog /opt/apache/logs/eygle_access_log.%Y%m%d" combined env=!dontlog
http://www.clusting.com/Apache/ApacheManual/logs.html http://svn.apache.org/viewvc/httpd/httpd/trunk/server/mpm_common.c?view=markup&pathrev=230808
历史上的今天...
>> 2016-04-09文章:
>> 2013-04-09文章:
>> 2012-04-09文章:
>> 2009-04-09文章:
>> 2008-04-09文章:
By eygle on 2006-04-09 16:48 | Comments (5) | Web | 737 |
http://svn.apache.org/viewvc/httpd/httpd/trunk/server/mpm_common.c?view=markup&pathrev=230808
/* Create the request string. We include a User-Agent so that
* adminstrators can track down the cause of the odd-looking
* requests in their logs.
*/
srequest = apr_pstrcat(p, "GET / HTTP/1.0\r\nUser-Agent: ",
ap_get_server_version(),
" (internal dummy connection)\r\n\r\n", NULL);
在日志里屏蔽记录
#cat http.conf
.....
.....
# Mark requests from the loop-back interface
SetEnvIf Remote_Addr "127\.0\.0\.1" dontlog
# Log what remains
CustomLog logs/access_log common env=!dontlog
.....
.....
感谢这位朋友，我增加了如下判断屏蔽了这些信息:
SetEnvIf Remote_Addr "::1" dontlog
CustomLog "|/usr/local/sbin/cronolog /opt/apache/logs/eygle_access_log.%Y%m%d" combined env=!dontlog
不客气,关键是多道处理模块(MPM)的配置,我的服务器采用apache在unix上默认的prefork,
#./httpd -l |grep prefork
prefork.c
如下配置下,这个internal dummy connection提示信息就几乎没有了.
StartServers 50
MinSpareServers 50
MaxSpareServers 100
ServerLimit 2000
MaxClients 1000
MaxRequestsPerChild 1000
我照你这个配置修改了一下，看看是否可以消除这个信息。
Apache也真够强大和复杂的：）