First, the Apache common startup error and resolution method.
1. Apache startup error Resolution when configuring a virtual host:
Warning:documentroot [/application/apache2.2.27/docs/dummy-host.example.com] does not exist
In fact, the main cause of this error is nearly obvious, is your httpd-vhosts.conf in a more than one of the following configuration:
<virtualhost *:80>
ServerAdmin [email protected]
ServerName dummy-host.example.com
Serveralias www.dummy-host.example.com
Errorlog "Logs/dummy-host.example.com-error_log"
Customlog "Logs/dummy-host.example.com-access_log" common
</VirtualHost>
When you configure a virtual host, you cannot have such a template, a workaround: all comments or deletions.
2. The following error occurred while compiling and installing Apache:
Httpd:could not reliably determine the server ' s fully qualified domain name, using 127.0.0.1 for ServerName
Workaround: Open httpd.conf to find #servername www.example.com:80 followed by the following code:
ServerName 127.0.0.1:80servername 127.0.0.1:80
Of course, the above operation will need to check the syntax after restarting the Apache service:
/APPLICATION/APCHE/BIN/APACHECTL-T---Check grammar
/APPLICATION/APACHE/BIN/APACHECTL Graceful---Smooth restart
If 403-forbidden occurs when the domain name is accessed after the configuration of the virtual host is complete, the reason may be:
1) The firewall is not shutting down
2) A separate site directory is not configured in httpd.conf as follows:
<directory "/application/apache2.2.27/htdocs" >
Options-indexes FollowSymLinks
AllowOverride None
Order Allow,deny
Allow from all
</Directory>
Need detailed Apache compilation installation steps click: http://purify.blog.51cto.com/10572011/1772656
This article is from "Wake up your not alarm clock but dream" blog, please be sure to keep this source http://purify.blog.51cto.com/10572011/1789292
Linux under Apache boot problem (dummy-host.example.com does not exist, Could not. 127.0.0.1 for ServerName)