Request URL /server-status or 404 Page Not Found Apache Error请求网址/服务器的地位或404未找到网页Apache的错误

In Apache web server, when an administrator wants to check the Apache server status with the command “apachectl status” or “service httpd fullstatus” at shell prompt, the following error may occur:在Apache Web服务器，当管理员要检查Apache服务器的地位，与指挥“ apachectl地位”或“服务的httpd fullstatus ”在shell提示符，下面的错误，可能会发生：

Not Found未找到

The requested URL /server-status was not found on this server.所请求的URL /服务器的地位没有被发现在此服务器上。

If you request the Apache status from web page by viewing http://domain_name/server-status link location, a 404 page not found error will be returned by web browser.如果您的要求， Apache的地位，从网页浏览http://domain_name/server-status链接位置， 1 404未找到网页的错误将被退回，由Web浏览器。

There are several reasons why this problem can occurred.有几个原因，这个问题是可以发生。 First thing to check is to ensure that the mod_status status handler is properly setup and loaded in httpd.conf configuration file.第一件事是检查，以确保该mod_status的地位，处理是正确安装和加载在httpd.conf配置文件。 Using APXS, the following 2 lines must exist:使用的apxs ，以下2行必须存在：

LoadModule status_module /path/to/apache/modules/mod_status.so loadmodule status_module /路径/ /阿帕奇/模组/ mod_status.so
AddModule mod_status.c addmodule mod_status.c

If the lines exist, the problem probably lies on virtual host declaration.如果线的存在，问题可能在于对虚拟主机的宣言。 As a side note, you can also check if the status handler is been activated to show more information (but will slow down a busy server) by locating the following line in httpd.conf (default to off):作为一个方面说明，您也可以勾选如果状态处理程序是被激活，以显示更多信息（但会拖慢一个繁忙的服务器）通过查找下面一行在httpd.conf （默认为关闭） ：

ExtendedStatus On extendedstatus对

For virtual host for server-status, ensure that the following line exists in your Apache configuration file:为虚拟主机服务器的地位，确保下面的行存在于你的Apache配置文件：

SetHandler server-status sethandler服务器的地位
Order allow,deny为了让，否认
Deny from all否认所有
Allow from localhost允许从本地

You can change the localhost to your domain name such as .example.com (including dot in front of domain) to allow access from domain address.你可以改变本地，以您的域名如。 example.com （包括点在前面的网域） ，以允许访问由网域位址。 Else localhost restrict access doesn’t allow public access to server-status, and only command shell access locally is possible.否则，本地限制进入不允许公众进入服务器的地位，只有命令外壳进入当地是有可能的。

Note that also if you use NameVirtualHost *:80 directive, or any *:port directive to run multiple name based virtual hosts, this configuration does not allow server-status on any of the publicly accessible addresses.请注意，也如果您使用namevirtualhost * ： 80指令，或任何* ：港口指令运行多个名称为基础的虚拟主机，此配置不容许服务器的地位，任何有关可公开查阅的地址。 The reason is that the first Virtual Host in the directive is considered the “Default Virtual Host”, and any unknown entries on the NameVirtualHost space whenever user or process attempts to access port 80 on any IP address, will go to this virtual host by default.原因是第一虚拟主机在该指令被认为是“默认虚拟主机” ，以及任何未知的参赛作品就namevirtualhost空间，每当用户或进程尝试访问端口80的任何IP地址，将前往这个虚拟主机预设。 Hence the 404 page not found error is returned.因此， 404未找到网页错误是回来了。 Furthermore the server-status configuration cannot be placed inside of a VirtualHost directive to be read from a full domain name.此外，服务器的地位，配置不能置于内的一个虚拟主机指令，读从一个完整域名。

There are 2s solution and workarounds for this scenario, either by making the server listen on an alternative port (such as port 8080), or allowing only internal or local access.有2s的解决方案，并为替代这种情况下，无论是由决策服务器，听取关于替代港口（如港口8080 ） ，或只允许内部或本地访问。

To change to another port, simply adding “Listen 8080″ to the configuration, and you can access the server status from external by using http://domain:8080/server-status in any web browser.要改变到另一个港口，只要加入“倾听8080 ”的配置，您可以访问该服务器的地位，从外部用http://domain:8080/server-status在任何Web浏览器。

To allow only local access for commands such as ‘apachectl status’ or ’service httpd fullstatus’, simply switch each * to the actual IP address to work from, then accessing from localhost (127.0.0.1) will work.只允许本地接入的命令，如' apachectl地位'或'服务的httpd fullstatus ' ，只要开关，每个*实际的IP地址的工作由，然后进入从本地（ 127.0.0.1 ）会的工作。

For example, change from:举例来说，改变由：

NameVirtualHost *:80 namevirtualhost * ： 80

to至

NameVirtualHost 10.0.0.3:80 namevirtualhost 10.0.0.3:80

Once configuration file is modified correctly, restart Apache HTTPD server.一旦配置文件修改正确，请重新启动的Apache的httpd服务器。

IMPORTANT : This is a machine translated page which is provided "as is" without warranty. 重要说明 ：这是一个机器翻译网页是“按原样”提供的担保。 Machine translation may be difficult to understand.机器翻译可能很难理解。 Please refer to请参阅 original English article英文原版的文章 whenever possible.只要有可能。

Share and contribute or get technical support and help at分享和贡献，或取得技术的支持和帮助，在 My Digital Life Forums 我的数字生活论坛 . 。

Related Articles相关文章

• cPanel WHM Failed to Receive Status Information From Apache Error的cPanel的WHM没有收到状态信息从Apache的错误
• Apache Status (whm-server-status) in cPanel WebHost Manager Returns Blank Page Apache的地位（的WHM服务器的地位）在网页主机的cPanel经理回报的空白页
• Running apachectl status Returns lynx: not found Error运行apachectl地位回报猞猁：没有发现错误
• Add Trailing Slash to the End of the URL with .htaccess Rewrite Rules添加斜线到去年底的网址。 htaccess的重写规则
• SEO Friendly Rewrite Method to Move Website URL From Subdirectory to Root Parent Folder徐友好重写方法动议网址从子目录，以根父文件夹
• winnt_accept: Asynchronous AcceptEx failed Error in Apache Log winnt_accept ：异步acceptex失败错误在Apache日志
• WordPress Permalinks Does Not Work in xampp Setup在WordPress永久不工作， xampp安装
• Installing Web Server in FreeBSD 6.0 with Apache 2.2, MySQL 5.0 and PHP 5 - Part 4安装Web服务器在FreeBSD的6.0与2.2的Apache ， MySQL 5.0的和PHP 5 -第4部分
• PHP 5 Unable to Open HTTP Request Stream with fopen or fsockopen Functions PHP 5中无法打开HTTP请求流与fopen或fsockopen职能
• Starting Apache HTTPD Failed Due to Cannot Open or No Such mod_bwlimited, mod_log_bytes or mod_bandwidth Files开始的Apache的httpd失败，由于无法打开，或没有这样的mod_bwlimited ， mod_log_bytes或mod_bandwidth档案

This entry was posted on Monday, April 23rd, 2007 at 1:56 pm and is filed under 此项目被张贴在周一， 2007年4月23日在下午1时56分，并提交下 Webmaster Resources 网站管理员资源 . 。 You can follow any responses to this entry through the 您可以按照任何的反应，此项目通过 RSS 2.0 2.0 feed. 喂养。 You can 您可以 leave a response 留下的回应 , or ，或 trackback Trackback跟踪 from your own site. 从你自己的网站。