Error Log

This is a collection of errors produced by the Apache HTTP Server and written to the error log. When you receive an error in your browser, always check the error log for more details on the problem. If you can't find your error log, try consulting DistrosDefaultLayout.

A comprehensive database of all 3000+ error messages (and, in many cases, how to fix them) is at httpd.rcbowen.com/errors.

Click on each link for more information about each of these error messages

A


AcceptEx Failed


AcceptExFailed



Attempt to invoke directory as script


DirectoryAsScript

C


Client denied by server configuration


ClientDeniedByServerConfiguration



Could not determine the server's fully qualified domain name...


CouldNotDetermineServerName



Could not bind to address 0.0.0.0:80


CouldNotBindToAddress

E


(8)Exec format error: exec of '...' failed


ExecFormatError

F


File does not exist: /usr/local/apache/htdocs/favicon.ico


Favicon



(38)Function not implemented: core_output_filter: writing data to the network


SendfileNotImplemented

I


Invalid argument: core_output_filter: writing data to the network


InvalidArgumentCoreOutputFilter



Invalid command 'AuthDigestFile', perhaps misspelled...


InvalidCommandAuthDigestFile



Invalid method in request \x80j\x01\x0\


InvalidMethodHTTPSonHTTP

M


Mixing ports (* and non-* ports)


VirtualHostsMixingPorts

N


(28)No space left on device: Cannot create SSLMutex


IPCExhaustion



(2)No such file or directory: Failed to enable the ‘httpready’ Accept Filter


HttpreadyAcceptFilter

P


(13)Permission denied


13PermissionDenied



(13)Permission denied: /.../.htaccess pcfg_openfile: unable to check htaccess file, ensure it is readable


PcfgOpenfile



Premature End of Script Headers


PrematureEndOfScriptHeaders



proxy: ap_get_scoreboard_lb(1) failed...


ApGetScoreboardLb



proxy: No protocol handler was valid for the URL...


NoProtocolHandlerForURL

S


Session Cache is not configured


SSLSessionCache

Access Log

Some things you may see in your access log, linked to their explanations:

Startup Failure

Be aware that if httpd cannot access its log directory (perhaps /var/log/httpd or a symlink in /etc/httpd/logs) it will not start up or even log a message.

  • No labels