The options available for this directive, in increasing order
of verbosity, are emerg, alert, crit, error, warn, notice, info, and debug. Select only one
of these. Any message that is at least as important as the LogLevel you select will be stored in the
ErrorLog. On a typical server, this is set to warn. You should not set it to any lower than crit,
and you should avoid leaving it set to debug because that can slow down the server and result in
a very large ErrorLog.
As a last resort, you can also try running apache manually to check for crashes or other error
messages:
# /usr/sbin/apache -d /etc/apache -F ; echo $?
The -d flag tells apache where to look for its configuration file, and the -F flag tells it to run in
the foreground. The semicolon separates this command from the echo command, which displays
the return code ($?) from Apache after it exits. In the event that apache crashes during this step,
you can use tools such as gdb and strace to trace the problem.
Access Forbidden and Server Internal Errors
Two common types of errors that you may encounter when attempting to view specific pages on
your server are permission errors and server internal errors. Both types of errors can usually be
isolated using the information in the error log. After making any of the changes described in the
following list to attempt to solve one of these problems, try the request again and then check the
error log to see if the message has changed (for example, to show that the operation completed
successfully).
Pages:
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
1213
1214
1215
1216
1217
1218
1219
1220
1221
1222
1223
1224
1225
1226
1227