Name

LogLevel

Synopsis

LogLevel level 
Default: error
Server config, virtual host

LogLevel controls the amount of information recorded in the error_log file. The levels are as follows:

emerg

The system is unusable — exiting. For example:

"Child cannot open lock file. Exiting"

alert

Immediate action is necessary. For example:

"getpwuid: couldn't determine user name from uid"

crit

Critical condition. For example:

"socket: Failed to get a socket, exiting child"

error

Client is not getting a proper service. For example:

"Premature end of script headers"

warn

Nonthreatening problems, which may need attention. For example:

"child process 1234 did not exit, sending another SIGHUP"

notice

Normal events, which may need to be evaluated. For example:

"httpd: caught SIGBUS, attempting to dump core in ..."

info

For example:

"Server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers)..."

debug

Logs normal events for debugging purposes.

Each level will report errors that would have been printed by higher levels. Use debug for development, then switch to, say, crit for production. Remember that if each visitor on a busy site generates one line in the error_log, the hard disk will soon fill up and stop the system.