1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
|
<?xml version='1.0' encoding='UTF-8' ?>
<!DOCTYPE manualpage SYSTEM "./style/manualpage.dtd">
<?xml-stylesheet type="text/xsl" href="./style/manual.en.xsl"?>
<manualpage>
<relativepath href="."/>
<title>Starting Apache</title>
<summary>
<p>On Windows, Apache is normally run as a service on Windows
NT, or as a console application on Windows 95. For details, see
<a href="platform/windows.html#run">running Apache for
Windows</a>.</p>
<p>On Unix, the <a href="programs/httpd.html">httpd</a> program
is run as a daemon that executes continuously in the
background to handle requests. This document describes how
to invoke <code>httpd</code>.</p>
</summary>
<seealso><a href="stopping.html">Stopping Apache</a></seealso>
<seealso><a href="programs/httpd.html">httpd</a></seealso>
<seealso><a href="programs/apachectl.html">apachectl</a></seealso>
<section id="startup"><title>How Apache Starts</title>
<p>If the <directive module="mpm_common">Listen</directive>
specified in the configuration file is default of 80 (or any other
port below 1024), then it is necessary to have root privileges in
order to start apache, so that it can bind to this privileged
port. Once the server has started and performed a few preliminary
activities such as opening its log files, it will launch several
<em>child</em> processes which do the work of listening for and
answering requests from clients. The main <code>httpd</code>
process continues to run as the root user, but the child processes
run as a less privileged user. This is controlled by the selected
<a href="mpm.html">Multi-Processing Module</a>.</p>
<p>The recommended method of invoking the <code>httpd</code>
executable is to use the <a
href="programs/apachectl.html">apachectl</a> control script. This
script sets certain environment variables that are necessary for
<code>httpd</code> to function correctly under some operating
systems, and then invokes the <code>httpd</code> binary.
<code>apachectl</code> will pass through any command line
arguments, so any <code>httpd</code> options may also be used with
<code>apachectl</code>. You may also directly edit the
<code>apachectl</code> script by changing the <code>HTTPD</code>
variable near the top to specify the correct location of the
<code>httpd</code> binary and any command-line arguments that you
wish to be <em>always</em> present.</p>
<p>The first thing that <code>httpd</code> does when it is
invoked is to locate and read the <a
href="configuring.html">configuration file</a>
<code>httpd.conf</code>. The location of this file is set at
compile-time, but it is possible to specify its location at run
time using the <code>-f</code> command-line option as in</p>
<example>/usr/local/apache2/bin/apachectl -f
/usr/local/apache/conf/httpd.conf</example>
<p>If all goes well during startup, the server will detach from
the terminal and the command prompt will return almost
immediately. This indicates that the server is up and running.
You can then use your browser to connect to the server and view
the test page in the <directive
module="core">DocumentRoot</directive> directory
and the local copy of the documentation linked from that
page.</p>
</section>
<section id="errors"><title>Errors During Start-up</title>
<p>If Apache suffers a fatal problem during startup, it will
write a message describing the problem either to the console or
to the <directive module="core">ErrorLog</directive> before
exiting. One of the most common error messages is "<code>Unable
to bind to Port ...</code>". This message is usually caused by
either:</p>
<ul>
<li>Trying to start the server on a privileged port when not
logged in as the root user; or</li>
<li>Trying to start the server when there is another instance
of Apache or some other web server already bound to the same
Port.</li>
</ul>
<p>For further trouble-shooting instructions, consult the
Apache <a href="faq/">FAQ</a>.</p>
</section>
<section id="boot"><title>Starting at Boot-Time</title>
<p>If you want your server to continue running after a system
reboot, you should add a call to <code>apachectl</code> to your
system startup files (typically <code>rc.local</code> or a file in
an <code>rc.N</code> directory). This will start Apache as
root. Before doing this ensure that your server is properly
configured for security and access restrictions.</p>
<p>The <code>apachectl</code> script is designed to act like a
standard SysV init script; it can take the arguments
<code>start</code>, <code>restart</code>, and <code>stop</code>
and translate them into the appropriate signals to
<code>httpd</code>. So you can often simply link
<code>apachectl</code> into the appropriate init directory. But be
sure to check the exact requirements of your system.</p>
</section>
<section id="info"><title>Additional Information</title>
<p>Additional information about the command-line options of <a
href="programs/httpd.html">httpd</a> and <a
href="programs/apachectl.html">apachectl</a> as well as other
support programs included with the server is available on the
<a href="programs/">Server and Supporting Programs</a> page.
There is also documentation on all the <a
href="mod/">modules</a> included with the Apache distribution
and the <a href="mod/directives.html">directives</a> that they
provide.</p>
</section>
</manualpage>
|
