Gentoo Archives: gentoo-doc-cvs

From: Sven Vermeulen <swift@×××××××××××.org>
To: gentoo-doc-cvs@l.g.o
Subject: [gentoo-doc-cvs] cvs commit: apache-troubleshooting.xml
Date: Mon, 01 Aug 2005 14:49:22
Message-Id: 200508011449.j71En4fx014038@robin.gentoo.org
1 swift 05/08/01 14:49:01
2
3 Modified: xml/htdocs/doc/en metadoc.xml
4 Added: xml/htdocs/doc/en apache-troubleshooting.xml
5 Log:
6 #99539 - Apache troubleshooting guide, language improvements and migrating to /doc/en
7
8 Revision Changes Path
9 1.90 +6 -1 xml/htdocs/doc/en/metadoc.xml
10
11 file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.90&content-type=text/x-cvsweb-markup&cvsroot=gentoo
12 plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml?rev=1.90&content-type=text/plain&cvsroot=gentoo
13 diff : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/metadoc.xml.diff?r1=1.89&r2=1.90&cvsroot=gentoo
14
15 Index: metadoc.xml
16 ===================================================================
17 RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v
18 retrieving revision 1.89
19 retrieving revision 1.90
20 diff -u -r1.89 -r1.90
21 --- metadoc.xml 1 Aug 2005 13:06:48 -0000 1.89
22 +++ metadoc.xml 1 Aug 2005 14:49:01 -0000 1.90
23 @@ -1,5 +1,5 @@
24 <?xml version='1.0' encoding="UTF-8"?>
25 -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.89 2005/08/01 13:06:48 swift Exp $ -->
26 +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/metadoc.xml,v 1.90 2005/08/01 14:49:01 swift Exp $ -->
27 <!DOCTYPE metadoc SYSTEM "/dtd/metadoc.dtd">
28
29 <metadoc lang="en">
30 @@ -359,6 +359,7 @@
31 <file id="shb-services">/doc/en/security/shb-services.xml</file>
32 <file id="shb-tight">/doc/en/security/shb-tight.xml</file>
33 <file id="shb-uptodate">/doc/en/security/shb-uptodate.xml</file>
34 + <file id="apache-troubleshooting">/doc/en/apache-troubleshooting.xml</file>
35 </files>
36 <docs>
37 <doc id="name-logo">
38 @@ -979,5 +980,9 @@
39 <memberof>install_other</memberof>
40 <fileid>usb-guide</fileid>
41 </doc>
42 + <doc id="apache-troubleshooting">
43 + <memberof>sysadmin_specific</memberof>
44 + <fileid>apache-troubleshooting</fileid>
45 + </doc>
46 </docs>
47 </metadoc>
48
49
50
51 1.1 xml/htdocs/doc/en/apache-troubleshooting.xml
52
53 file : http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/apache-troubleshooting.xml?rev=1.1&content-type=text/x-cvsweb-markup&cvsroot=gentoo
54 plain: http://www.gentoo.org/cgi-bin/viewcvs.cgi/xml/htdocs/doc/en/apache-troubleshooting.xml?rev=1.1&content-type=text/plain&cvsroot=gentoo
55
56 Index: apache-troubleshooting.xml
57 ===================================================================
58 <?xml version='1.0' encoding="UTF-8"?>
59 <!DOCTYPE guide SYSTEM "/dtd/guide.dtd">
60 <guide link="apache-troubleshooting.xml" lang="en">
61 <title>Troubleshooting Apache</title>
62
63 <author title="Author">
64 <mail link="vericgar@g.o">Michael Stewart</mail>
65 </author>
66 <author title="Contributor">
67 <mail link="beu@g.o">Elfyn McBratney</mail>
68 </author>
69 <author title="Contributor">
70 <mail link="kloeri@g.o">Bryan Østergaard</mail>
71 </author>
72
73 <abstract>
74 This document covers a number of ways to figure out how to fix your Apache
75 installation when things are not working correctly.
76 </abstract>
77
78 <!-- The content of this document is licensed under the CC-BY-SA license -->
79 <!-- See http://creativecommons.org/licenses/by-sa/2.5 -->
80 <license/>
81
82 <version>1.4</version>
83 <date>2005-08-01</date>
84
85 <chapter>
86 <title>Checking the Logs</title>
87 <section>
88 <body>
89
90 <p>
91 If there is something wrong with your Apache, but you have no idea how to
92 figure out what's wrong, your first clues will be in the log files.
93 </p>
94
95 <p>
96 There are a few log files around. All of them are located inside
97 <path>/var/log/apache2/</path>. Not all of the following log files will be
98 on your system: this depends on what modules you have enabled.
99 </p>
100
101 </body>
102 </section>
103
104 <section>
105 <title>access_log</title>
106 <body>
107
108 <pre caption="access_log">
109 67.185.0.236 - - [18/Jun/2005:12:05:50 -0700] "GET / HTTP/1.0" 200 721
110 10.0.1.80 - - [18/Jun/2005:12:11:07 -0700] "GET /~jaspenelle/__journal1.jpg HTTP/1.1" 200 19079
111 66.239.233.163 - - [18/Jun/2005:12:15:06 -0700] "GET /~jaspenelle/avy14.gif HTTP/1.0" 200 1661
112 67.185.60.155 - - [18/Jun/2005:12:18:48 -0700] "GET / HTTP/1.0" 200 721
113 67.185.0.236 - - [18/Jun/2005:12:25:39 -0700] "GET / HTTP/1.0" 200 721
114 10.0.1.80 - - [18/Jun/2005:12:28:04 -0700] "GET /~jaspenelle/avy14.gif HTTP/1.1" 200 1661
115 10.0.1.80 - - [18/Jun/2005:12:28:46 -0700] "GET /~jaspenelle/avy7.png HTTP/1.1" 200 13066
116 </pre>
117
118 <p>
119 This file is simply a listing of every file requested from your server. Unless
120 you have changed the default configuration, it will be in Common Log Format:
121 </p>
122
123 <pre caption="Common Log Format syntax">
124 remotehost rfc931 authuser [date] "request" status bytes
125 </pre>
126
127 <table>
128 <tr>
129 <ti>remotehost</ti>
130 <ti>Remote host name or IP address</ti>
131 </tr>
132 <tr>
133 <ti>rfc931</ti>
134 <ti>The remote log name of the user.</ti>
135 </tr>
136 <tr>
137 <ti>authuser</ti>
138 <ti>The user name as which the user has authenticated himself.</ti>
139 </tr>
140 <tr>
141 <ti>[date]</ti>
142 <ti>Date and time of the request.</ti>
143 </tr>
144 <tr>
145 <ti>"request"</ti>
146 <ti>The request line exactly as it came from the client.</ti>
147 </tr>
148 <tr>
149 <ti>status</ti>
150 <ti>The HTTP status code returned to the client.</ti>
151 </tr>
152 <tr>
153 <ti>bytes</ti>
154 <ti>The content-length of the document transferred.</ti>
155 </tr>
156 </table>
157
158 </body>
159 </section>
160 <section>
161 <title>error_log</title>
162 <body>
163
164 <pre caption="error_log">
165 [Mon Feb 07 23:33:18 2005] [notice] suEXEC mechanism enabled (wrapper: /usr/sbin/suexec2)
166 [Mon Feb 07 23:33:18 2005] [notice] Digest: generating secret for digest authentication ...
167 [Mon Feb 07 23:33:18 2005] [notice] Digest: done
168 [Mon Feb 07 23:33:18 2005] [notice] Apache/2.0.52 (Gentoo/Linux) PHP/4.3.10 configured -- resuming normal operations
169 [Sat Jun 18 13:01:54 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico
170 [Sat Jun 18 13:02:14 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico
171 [Sat Jun 18 13:02:18 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico
172 [Sat Jun 18 13:02:21 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico
173 [Sat Jun 18 13:02:24 2005] [error] [client 10.0.1.80] File does not exist: /var/www/localhost/htdocs/favicon.ico
174 </pre>
175
176 <p>
177 As you can see, this file can contain a lot of stuff, depending on the
178 <c>ErrorLevel</c> directive in your <path>httpd.conf</path> file. It tells you
179 if apache started up correctly, what errors it has run into, ... In general it
180 will tell you what went wrong. If something isn't working right, this should
181 be the first file you check for more information.
182 </p>
183
184 </body>
185 </section>
186 <section>
187 <title>suexec_log</title>
188 <body>
189
190 <pre caption="suexec_log">
191 [2005-02-11 22:33:19]: uid: (1000/vericgar) gid: (1000/1000) cmd: test.cgi
192 [2005-03-11 19:20:13]: uid: (1000/vericgar) gid: (1000/1000) cmd: test.cgi
193 [2005-03-11 19:34:47]: uid: (1000/vericgar) gid: (1000/1000) cmd: test.cgi
194 </pre>
195
196 <p>
197 This file contains a log entry for every time a script is ran using CGI and
198 suexec. If you can't get a script to work with suexec, this log is the one
199 to check as it will generally have a line listing why it wouldn't run a script.
200 </p>
201
202 </body>
203 </section>
204 </chapter>
205
206 <chapter>
207 <title>I installed a module, but it's not working!!!</title>
208 <section>
209 <body>
210
211 <p>
212 Just installing a module is not enough - you have to explicitly turn it on. We
213 do this so that it's easy to turn on and off individual modules, which makes
214 it easy to find which module is causing problems and let's you test
215 modules and disable them easily.
216 </p>
217
218 <p>
219 When you install a module, it should display a message similar to this:
220 </p>
221
222 <pre caption="Post-installation message from emerge">
223 *
224 * To enable mod_layout, you need to edit your /etc/conf.d/apache2 file and
225 * add '-D LAYOUT' to APACHE2_OPTS.
226 *
227 *
228 * Configuration file installed as
229 * /etc/apache2/modules.d/15_mod_layout.conf
230 * You may want to edit it before turning the module on in /etc/conf.d/apache2
231 *
232 </pre>
233
234 <p>
235 This is pretty straightforward. It tells you exactly what you need to do to
236 enable this module.
237 </p>
238
239 <p>
240 If you missed this message, there is another way to find out what you need to
241 add to <c>APACHE2_OPTS</c> in <path>/etc/conf.d/apache2</path>: simply
242 check the configuration file the module installed. The module's
243 configuration file should be added to <path>/etc/apache2/modules.d/</path>.
244 Look for it there and find a line that has <c>IfDefine</c>:
245 </p>
246
247 <pre caption="An excerpt from 15_mod_layout.conf">
248 &lt;IfDefine LAYOUT&gt;
249 &lt;IfModule !mod_layout.c&gt;
250 LoadModule layout_module modules/mod_layout.so
251 &lt;/IfModule&gt;
252 &lt;/IfDefine&gt;
253 </pre>
254
255 <p>
256 The <c>IfDefine</c> block is ran when you add <c>-D LAYOUT</c> to
257
258
259
260 --
261 gentoo-doc-cvs@g.o mailing list