23.4 Messages beginning with AH
This section describes the messages beginning with AH.
-
AH00004
Unable to create scoreboard (anonymous shared memory failure)
- Description
-
The shared memory to be used with the scoreboard could not be secured. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00013
Pre-configuration failed
- Description
-
An error occurred in the processing prior to reading the configuration file. The Web server stops the start processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00014
Configuration check failed
- Description
-
An error is detected during checking of the configuration file. The Web server stops the start processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00015
Unable to open logs
- Description
-
An error occurred during the setup of the log output destination or during the socket generation processing. The Web server stops the start processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00016
Configuration Failed
- Description
-
An error occurred in the processing after reading the configuration file. The Web server stops the start processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00017
Pre-configuration failed
- Description
-
An error occurred in the processing prior to reading the configuration file. The Web server stops the start or restart processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00018
Configuration check failed
- Description
-
An error is detected during checking of the configuration file. The Web server stops the start or restart processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00019
Unable to open logs
- Description
-
An error occurred during the setup of the log output destination or during the socket generation processing. The Web server stops the start or restart processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00020
Configuration Failed
- Description
-
An error occurred in the processing after reading the configuration file. The Web server stops the start or restart processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00023
Couldn't create the aa....aa mutex (file bb....bb)
aa....aa: Type
bb....bb: File name
- Description
-
An attempt to create the exclusive environment has failed. bb....bb might not be output.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00024
Couldn't set permissions on the aa....aa mutex; check User and Group directives
aa....aa: Type
- Description
-
An attempt to set up permissions for the mutual exclusion has failed.
- Action
-
Revise the User and Group directive values according to the detailed information shown in this message.
-
AH00025
configuration error: couldn't aa....aa: bb....bb
aa....aa: Text
bb....bb: Requested URI value
- Description
-
When accessing the requested URI value, the event indicated in aa....aa cannot be performed due to an error in the configuration file settings.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the configuration file according to the contents described in text.
-
AH00031
access to aa....aa failed; stat of 'bb....bb' failed.
aa....aa: Requested URI value
bb....bb: Access file
- Description
-
The file indicated by the requested URI cannot be accessed. Information for the file indicated by the file name could not be acquired.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the access file according to the detailed information shown in this message.
-
AH00032
Symbolic link not allowed or link target not accessible: aa....aa
aa....aa: Access file
- Description
-
The file indicated in aa....aa is not allowed to dereference a symbolic link.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
If SymLinksIfOwnerMatch of the Options directive is enabled, make sure that the owner of the access file or directory is the same as the owner of the symbolic link.
-
AH00033
dir_walk error, path_info aa....aa is not relative to the filename path bb....bb for uri cc....cc
aa....aa: Path information
bb....bb: Directory name
cc....cc: Requested URI value
- Description
-
The path described in the aa....aa is not included under the directory described in the bb....bb.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00034
dir_walk error, could not determine the root path of filename aa....aa for uri bb....bb
aa....aa: File name
bb....bb: Requested URI value
- Description
-
A standard path could not be determined as the path to be specified in the aa....aa.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00035
access to aa....aa denied (filesystem path 'bb....bb') because search permissions are missing on a component of the path
aa....aa: Requested URI value
bb....bb: Access file
- Description
-
An attempt to access the file indicated by the requested URI failed due to the lack of search permissions for the file.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the access file according to the detailed information shown in this message.
-
AH00036
access to aa....aa failed (filesystem path 'bb....bb')
aa....aa: Requested URI value
bb....bb: Access file
- Description
-
The file indicated by the requested URI cannot be accessed.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the access file according to the detailed information shown in this message.
-
AH00037
Symbolic link not allowed or link target not accessible: aa....aa
aa....aa: Access file
- Description
-
The file indicated in aa....aa is not allowed to dereference a symbolic link.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
If SymLinksIfOwnerMatch of the Options directive is enabled, make sure that the owner of the access file or directory is the same as the owner of the symbolic link.
-
AH00038
Forbidden: aa....aa doesn't point to a file or directory
aa....aa: Access file
- Description
-
The access file is neither a file nor a directory.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the attribute of the access file.
-
AH00045
child process aa....aa still did not exit, sending a SIGTERM
aa....aa: Process ID
- Description
-
The SIGTERM signal will be sent because the server process described in the aa....aa has not terminated. The Web server continues the termination or restart processing.
- Action
-
Make sure that the SIGTERM signal is not blocked for the server process, and wait until the server process terminates.
-
AH00046
child process aa....aa still did not exit, sending a SIGKILL
aa....aa: Process ID
- Description
-
The SIGKILL signal will be sent because the server process described in the aa....aa has not terminated. The Web server continues the termination or restart processing.
- Action
-
Wait until the server process terminates.
-
AH00047
could not make child process aa....aa exit, attempting to continue anyway
aa....aa: Process ID
- Description
-
The server process specified in the aa....aa could not be terminated. The termination or restart processing of the server will continue after ignoring the un-terminated server process.
- Action
-
An un-terminated server process exists. Investigate the cause due to which the server does not terminate, and if it is necessary to terminate the server, send a signal and terminate forcibly.
-
AH00050
Child aa....aa returned a Fatal error... Server is exiting!
aa....aa: Process ID
- Description
-
The server process terminated because of an error due to which the process could not be continued. The Web server will shut down.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00051
child pid aa....aa exit signal bb....bb (cc....cc), possible coredump in dd....dd
aa....aa: Process ID
bb....bb: Signal meaning
cc....cc: Signal number
dd....dd: Core output destination directory
- Description
-
The server process terminated with the signal specified in the cc....cc. If possible, output the core in the dd....dd. The Web server continues the processing.
-
AH00052
child pid aa....aa exit signal bb....bb (cc....cc)
aa....aa: Process ID
bb....bb: Signal meaning
cc....cc: Signal number
- Description
-
The server process terminated with the signal specified in the cc....cc.
The Web server continues the processing.
-
AH00053
write pipe_of_death
- Description
-
An attempt to write in the pipe to be used in the request for terminating the server process has failed. The request of terminating the server process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00054
get socket to connect to listener
- Description
-
An attempt to generate the socket to be used in the request for terminating the server process has failed. The request of terminating the server process will now stop.
- Action
-
Revise the specification according to the detailed information about socket() shown in this message.
-
AH00055
set timeout on socket to connect to listener
- Description
-
An attempt to set up a timeout for the socket to be used in the request for terminating the server process has failed. The request of terminating the server process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00056
connect to listener on aa....aa:bb....bb
aa....aa: Web server address
bb....bb: Port number
- Description
-
An attempt to connect to the Web server during the processing of the server process termination request has failed. The request of terminating the server process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00057
sending signal to server
- Description
-
An attempt to send a signal to the Web server has failed.
- Action
-
Revise the specification according to the detailed information about kill() shown in this message.
-
AH00058
Error retrieving pid file aa....aa
aa....aa: PID storage file name
- Description
-
An attempt to search the PID storage file has failed. The process of sending a signal to the Web server will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00059
Remove it before continuing if it is corrupted.
- Description
-
If the PID storage file is corrupted, you must delete it.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00060
seg fault or similar nasty error detected in the parent process
- Description
-
The signal for terminating the control process was received. The control process terminates.
-
AH00061
sigaction(SIGSEGV)
- Description
-
An error occurred when the action for the SIGSEGV signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00062
sigaction(SIGBUS)
- Description
-
An error occurred when the action for the SIGBUS signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00063
sigaction(SIGABORT)
- Description
-
An error occurred when the action for the SIGABORT signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00064
sigaction(SIGABRT)
- Description
-
An error occurred when the action for the SIGABRT signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00065
sigaction(SIGILL)
- Description
-
An error occurred when the action for the SIGILL signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00066
sigaction(SIGFPE)
- Description
-
An error occurred when the action for the SIGFPE signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00067
make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (SO_REUSEADDR)
aa....aa: Web server address
bb....bb: Port number
- Description
-
An error occurred during the setup of the socket level option SO_REUSEADDR. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about setsockopt() shown in this message.
-
AH00068
make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (SO_KEEPALIVE)
aa....aa: Web server address
bb....bb: Port number
- Description
-
An error occurred during the setup of the socket level option SO_KEEPALIVE. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about setsockopt() shown in this message.
-
AH00069
make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (IPV6_V6ONLY)
aa....aa: Web server address
bb....bb: Port number
- Description
-
An error occurred during the setup of the socket level option IPV6_V6ONLY. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about setsockopt() shown in this message.
-
AH00072
make_sock: could not bind to address aa....aa: bb....bb
aa....aa: Web server address
bb....bb: Port number
- Description
-
An error occurred during address binding to the socket. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about bind() shown in this message.
-
AH00073
make_sock: unable to listen for connections on address aa....aa: bb....bb
aa....aa: Web server address
bb....bb: Port number
- Description
-
An error occurred when preparing to receive connections on the socket. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about listen() shown in this message.
-
AH00074
make_sock: for address aa....aa: bb....bb, apr_socket_opt_set: (SO_REUSEADDR)
aa....aa: Web server address
bb....bb: Port number
- Description
-
An error occurred during the setup of the socket level option SO_REUSEADDR. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about setsockopt() shown in this message.
-
AH00077
alloc_listener: failed to set up sockaddr for aa....aa
aa....aa: IP address
- Description
-
The socket information concerning the aa....aa could not be acquired. The Web server stops the start processing.
- Action
-
Revise according to the aa....aa specified in the Listen directive.
-
AH00078
alloc_listener: failed to get a socket for aa....aa
aa....aa: IP address
- Description
-
An error occurred during the creation of the socket terminal. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about socket() shown in this message.
-
AH00089
Couldn't start ErrorLog process 'aa....aa'.
aa....aa: Value specified in the ErrorLog directive in the pipe specification.
- Description
-
An attempt to generate a process for the output of the error log has failed. The Web server stops the start processing.
- Action
-
Revise the ErrorLog directive according to the detailed information shown in this message.
-
AH00090
aa....aa: Invalid error log path bb....bb.
aa....aa: Command name
bb....bb: File name
- Description
-
The file path specified in the ErrorLog directive is invalid. The Web server stops the start processing.
- Action
-
Revise the ErrorLog directive according to the detailed information shown in this message.
-
AH00091
aa....aa: could not open error log file bb....bb.
aa....aa: Command name
bb....bb: File name
- Description
-
The error log file could not be opened. The Web server stops the start processing.
- Action
-
Revise the ErrorLog directive according to the detailed information shown in this message.
-
AH00092
unable to replace stderr with error_log
- Description
-
The file descriptor of standard error output cannot be copied in the file descriptor of the error log. The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00093
unable to replace stderr with /dev/null
- Description
-
The standard error output cannot be replaced with /dev/null. The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information about freopen() shown in this message.
-
AH00094
Command line: 'aa....aa'
aa....aa: Command line
- Description
-
The server started with the command indicated by the command line. The Web server continues the start processing.
-
AH00095
failed to remove PID file aa....aa
aa....aa: File name
- Description
-
An attempt to delete the file that stores the control process ID failed. The Web server continues the termination processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00096
removed PID file aa....aa (pid=bb....bb)
aa....aa: File name
bb....bb: Control process ID
- Description
-
The file that stores the control process ID was deleted.
The Web server continues the termination processing.
-
AH00097
Invalid PID file path aa....aa, ignoring.
aa....aa: File name
- Description
-
The file name that stores the process IDs is invalid.
The Web server continues the startup processing.
- Action
-
Revise the PidFile directive according to the detailed information shown in this message.
-
AH00098
pid file aa....aa overwritten -- Unclean shutdown of previous server run?
aa....aa: File name that stores process IDs
- Description
-
The file that stores process IDs is overwritten. The Web server might not have been shut down properly the last time. When the Web server is shut down properly, the file that stores process IDs is deleted.
The Web server continues the start processing.
- Action
-
Make sure that no un-terminated Web server exists. The process ID of the control process is saved in the file specified in the PidFile directive, when the Web server is started. This message will be output even when the file specified in the PidFile directive is duplicated in more than one Web server. Make sure that the file is not shared among multiple Web servers.
-
AH00099
could not create aa....aa
aa....aa: File name that stores process IDs
- Description
-
The file that stores the process IDs could not be created.
The Web server stops the start processing.
- Action
-
Revise the file specified in the PidFile directive according to the detailed information shown in this message.
-
AH00100
aa....aa: could not log pid to file bb....bb
aa....aa: Command name
bb....bb: File name that stores process IDs
- Description
-
An attempt to record a process ID in the bb....bb has failed. The Web server stops the start processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH00101
Invalid PID file path aa....aa, ignoring.
aa....aa: File name that stores process IDs
- Description
-
The file name that stores the process IDs is invalid. The Web server continues the start processing.
- Action
-
Revise the PidFile directive according to the detailed information shown in this message.
-
AH00103
piped_log_spawn: unable to setup child process 'aa....aa'
aa....aa: Log output program
- Description
-
The initial setup of properties of the process for the output of the log could not be performed. The processing for the generation of the process for log output will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00104
unable to start piped log program 'aa....aa'
aa....aa: Log output program
- Description
-
The log output based on the aa....aa could not be started. The processing for the generation of the process for log output will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00106
piped log program 'aa....aa' failed unexpectedly
aa....aa: Log output program
- Description
-
An unexpected error occurred in the log output program. The process for log output will be regenerated.
-
AH00107
piped_log_maintenance: unable to respawn 'aa....aa'
aa....aa: Log output program
- Description
-
An attempt to regenerate the process for log output has failed. The processing for the generation of the process for log output will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00112
Warning: DocumentRoot [aa....aa] does not exist
aa....aa: Directory name
- Description
-
The directory specified in the DocumentRoot directive cannot be found. The Web server continues the startup processing.
- Action
-
Revise according to the DocumentRoot directive specified in the <VirtualHost> block.
-
AH00113
aa....aa:bb....bb cannot use a full URL in a 401 ErrorDocument directive --- ignoring!
aa....aa: File name
bb....bb: Line number
- Description
-
The full URL cannot be specified when 401 is specified as the error status code in the ErrorDocument directive.
- Action
-
When 401 is specified as the error status code, specify the text or local URL.
-
AH00114
Useless use of AllowOverride in line aa....aa of bb....bb.
aa....aa: Line number
bb....bb: File name
- Description
-
The AllowOverride directive cannot be specified in the <Location> or <Files> block. The Web server continues the startup processing.
- Action
-
Delete the AllowOverride directive in the <Location> or <Files> block.
-
AH00117
Ignoring deprecated use of DefaultType in line aa....aa of bb....bb.
aa....aa: Line number
bb....bb: File name
- Description
-
The DefaultType directive cannot be used.
- Action
-
Delete the DefaultType directive.
-
AH00124
Request exceeded the limit of aa....aa internal redirects due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
aa....aa: Limit value
- Description
-
The number of internal redirects of a request has reached the limit value (10).
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Check the settings to make sure that the internal redirect is not iterated unnecessarily.
-
AH00125
Request exceeded the limit of aa....aa subrequest nesting levels due to probable configuration error. Use 'LimitInternalRecursion' to increase the limit if necessary. Use 'LogLevel debug' to get a backtrace.
aa....aa: Limit value
- Description
-
The number of sub request nesting of a request has reached the limit value (10).
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Check the settings to make sure that the sub request is not iterated unnecessarily.
-
AH00126
Invalid URI in request aa....aa
aa....aa: Request
- Description
-
The URI in the request is invalid.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the URI in the request.
-
AH00128
File does not exist: aa....aa
aa....aa: File name
- Description
-
The requested file cannot be found.
The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the requested file name.
-
AH00129
Attempt to serve directory: aa....aa
aa....aa: Directory name
- Description
-
Cannot send a request to the aa....aa.
The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the URI in the request.
-
AH00130
File does not exist: aa....aa
aa....aa: File name
- Description
-
The requested file cannot be found.
The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the requested file name.
-
AH00131
This resource does not accept the aa....aa method.
aa....aa: Method name
- Description
-
A request was sent to the source by a method that is not allowed.
The status code 405 Method Not Allowed will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the method in the request.
-
AH00132
file permissions deny server access: aa....aa
aa....aa: File name
- Description
-
There is no permission to access the required file.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the requested file according to the detailed information shown in this message.
-
AH00135
Invalid method in request aa....aa
aa....aa: Request line
- Description
-
The method in the request is invalid.
The status code 501 Method Not Implemented will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the method in the request.
-
AH00137
apr_socket_addr_get(APR_LOCAL)
- Description
-
The socket information of the Web server could not be acquired. The Web server stops the request processing.
- Action
-
Revise the specification according to the detailed information about getsockname() shown in this message.
-
AH00138
apr_socket_addr_get(APR_REMOTE)
- Description
-
The socket information of the client could not be acquired. The Web server stops the request processing.
- Action
-
Revise the specification according to the detailed information about getpeername() shown in this message.
-
AH00144
couldn't grab the accept mutex
- Description
-
An attempt to acquire the mutual exclusion of accept has failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00146
couldn't release the accept mutex
- Description
-
An attempt to release the mutual exclusion of accept has failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00147
sigaction(SIGTERM)
- Description
-
An error occurred when the action for the SIGTERM signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00148
sigaction(SIGUSR2)
- Description
-
An error occurred when the action for the SIGUSR2 signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00149
sigaction(SIGINT)
- Description
-
An error occurred when the action for the SIGINT signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00150
sigaction(SIGXCPU)
- Description
-
An error occurred when the action for the SIGXCPU signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00151
sigaction(SIGXFSZ)
- Description
-
An error occurred when the action for the SIGXFSZ signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00152
sigaction(SIGPIPE)
- Description
-
An error occurred when the action for the SIGPIPE signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00153
sigaction(SIGHUP)
- Description
-
An error occurred when the action for the SIGHUP signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00154
sigaction(SIGUSR1)
- Description
-
An error occurred when the action for the SIGUSR1 signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00155
Couldn't initialize cross-process lock in child (aa....aa) (bb....bb)
aa....aa: Lock file name
bb....bb: Exclusion identifier name
- Description
-
An attempt to initialize the mutual exclusion used between server processes has failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00162
server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers), spawning aa....aa children, there are bb....bb idle, and cc....cc total children
aa....aa: Number of server processes to be generated
bb....bb: Number of server processes that are idle
cc....cc: Total number of server processes
- Description
-
The Web server is in a busy state due to request processing. Either the value of the StartServers directive must be increased, or the value of the Min/MaxSpareServers directive must be revised. Server processes are generated one by one or in the specified unit (2, 4, 8, 16, or 32) at a time, until the number of server processes that are idle reaches the value specified in the MinSpareServers directive. If the number of processes to be generated reaches 8 or more, this message will be output.
-
AH00163
aa....aa configured -- resuming normal operations
aa....aa: Server name
- Description
-
The startup of the Web server has started.
-
AH00164
Server built: aa....aa
aa....aa: Time when Web server was created
- Description
-
The time of creation of the Web server that is started is displayed.
-
AH00167
long lost child came home! (pid aa....aa)
aa....aa: Process ID
- Description
-
The control process uses the scoreboard file to manage the status of the server process. If the process terminated after restarting with graceful does not correspond to the managed process, this message will be output.
-
AH00168
killpg SIGTERM
- Description
-
To shut down the Web server, the control process sent the signal SIGTERM to the server process with the killpg() function, but an error occurred. The control process will send the SIGTERM signal to each server process after a few seconds, and the server process termination processing will continue.
- Action
-
Revise the specification according to the detailed information about killpg() shown in this message.
-
AH00169
caught SIGTERM, shutting down
- Description
-
The Web server stopped because the SIGTERM signal was received.
-
AH00171
Graceful restart requested, doing restart
- Description
-
A restart of the Web server by graceful was requested. The restart processing will start.
-
AH00172
killpg SIGHUP
- Description
-
To restart the Web server, the control process sent the signal SIGHUP to the server process with the killpg() function, but an error occurred. The control process will send the SIGTERM signal to each server process after a few seconds, and the server process termination processing will continue.
- Action
-
Revise the specification according to the detailed information about killpg() shown in this message.
-
AH00173
SIGHUP received. Attempting to restart
- Description
-
The Web server received a restart request by the signal SIGHUP. The Web server starts the restart processing.
-
AH00264
sigaction(SIGTERM)
- Description
-
An error occurred when the action for the SIGTERM signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00265
sigaction(SIGUSR2)
- Description
-
An error occurred when the action for the SIGUSR2 signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00266
sigaction(SIGINT)
- Description
-
An error occurred when the action for the SIGINT signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00267
sigaction(SIGXCPU)
- Description
-
An error occurred when the action for the SIGXCPU signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00268
sigaction(SIGXFSZ)
- Description
-
An error occurred when the action for the SIGXFSZ signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00269
sigaction(SIGPIPE)
- Description
-
An error occurred when the action for the SIGPIPE signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00270
sigaction(SIGHUP)
- Description
-
An error occurred when the action for the SIGHUP signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00271
sigaction(SIGUSR1)
- Description
-
An error occurred when the action for the SIGUSR1 signal changed. The Web server continues the startup processing.
- Action
-
Revise the specification according to the detailed information about sigaction() shown in this message.
-
AH00272
aa....aa failed before this child process served any requests.
aa....aa: apr_proc_mutex_lock or apr_proc_mutex_unlock
- Description
-
An error occurred during lock or unlock processing. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00273
aa....aa failed. Attempting to shutdown process gracefully.
aa....aa: apr_proc_mutex_lock or apr_proc_mutex_unlock
- Description
-
An error occurred during lock or unlock processing. The server process will end after termination of the request processing being performed.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00274
apr_proc_mutex_unlock failed. Attempting to shutdown process gracefully.
- Description
-
An error occurred during unlock processing. The server process will end after termination of the request processing being performed.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00275
apr_thread_create: unable to create listener thread
- Description
-
An attempt to generate a listener thread failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00277
apr_thread_join: unable to join listener thread
- Description
-
An error occurred during processing to wait for termination of a listener thread. The termination processing of the server process continues.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00278
apr_thread_join: unable to join worker thread aa....aa
aa....aa: Slot number
- Description
-
An error occurred during processing to wait for termination of the server thread. The termination processing of the server process continues.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00279
apr_thread_join: unable to join the start thread
- Description
-
An error occurred during processing to wait for termination of the start thread. The termination processing of the server process continues.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00280
Couldn't initialize cross-process lock in child
- Description
-
An attempt to initialize the mutual exclusion used between server processes has failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00281
Couldn't initialize signal thread
- Description
-
An attempt to set up the signal mask of the thread failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00282
apr_thread_create: unable to create worker thread
- Description
-
An attempt to generate a start thread failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00283
fork: Unable to fork new process
- Description
-
An attempt to generate the server process has failed.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00289
server seems busy, (you may need to increase StartServers, ThreadsPerChild or Min/MaxSpareThreads), spawning aa....aa children, there are around bb....bb idle threads, and cc....cc total children
aa....aa: Number of server processes to be generated
bb....bb: Number of server threads that are idle
cc....cc: Total number of server processes
- Description
-
The Web server is in a busy state due to request processing. The value of the StartServers, ThreadsPerChild, MinSpareThreads, or MaxSpareThreads directive must be revised. Server processes are generated one by one or in the specified unit (2, 4, 8, 16, or 32) at a time, until the number of server threads that are idle reaches the value specified in the MinSpareServers directive. If the number of processes to be generated reaches 8 or more, this message will be output.
-
AH00291
long lost child came home! (pid aa....aa)
aa....aa: Process ID
- Description
-
The control process uses the scoreboard file to manage the status of the server process. If the process terminated after restarting with graceful does not correspond to the managed process, this message will be output.
-
AH00292
aa....aa configured -- resuming normal operations
aa....aa: Server name
- Description
-
The Web server has started.
-
AH00293
Server built: aa....aa
aa....aa: Time when Web server was created
- Description
-
The time of creation of the Web server that is started is displayed.
-
AH00295
caught SIGTERM, shutting down
- Description
-
The Web server stopped because the SIGTERM signal was received.
-
AH00297
SIGUSR1 received. Doing graceful restart
- Description
-
The restart of the Web server by graceful was requested. The restart processing will start.
-
AH00298
SIGHUP received. Attempting to restart
- Description
-
The Web server received a restart request by the signal SIGHUP. The Web server starts the restart processing.
-
AH00300
WARNING: ServerLimit of aa....aa exceeds compile-time limit of
bb....bb servers, decreasing to bb....bb.
aa....aa: Value specified in the ServerLimit directive
bb....bb: Maximum limit of the ServerLimit directive value
- Description
-
The ServerLimit directive value exceeds the maximum limit. The Web server sets the upper limit value for the ServerLimit directive, and then continues the startup processing.
- Action
-
Revise the ServerLimit directive value.
-
AH00301
ServerLimit of aa....aa exceeds compile-time limit of bb....bb, decreasing to match
aa....aa: Value specified in the ServerLimit directive
bb....bb: Maximum limit of the ServerLimit directive value
- Description
-
The ServerLimit directive value exceeds the maximum limit. The Web server sets the maximum limit value for the ServerLimit directive, and then continues processing.
- Action
-
Revise the ServerLimit directive value.
-
AH00304
changing ServerLimit to aa....aa from original value of bb....bb not allowed during restart
aa....aa: Value specified in the ServerLimit directive when restarting the Web server
bb....bb: Value specified in the ServerLimit directive when starting the Web server
- Description
-
The ServerLimit directive value cannot be changed when restarting the Web server. The Web server sets the ServerLimit directive to the value that was specified when the Web server started, and then continues processing.
- Action
-
If you need to change the ServerLimit directive value, stop the Web server, and then restart it.
-
AH00305
WARNING: ThreadLimit of aa....aa exceeds compile-time limit of
bb....bb threads, decreasing to bb....bb.
aa....aa: Value specified in the ThreadLimit directive
bb....bb: Maximum limit of the ThreadLimit directive value
- Description
-
The ThreadLimit directive value exceeds the maximum limit. The Web server sets the maximum limit value for the ThreadLimit directive, and then continues the startup processing.
- Action
-
Revise the ThreadLimit directive value.
-
AH00306
ThreadLimit of aa....aa exceeds compile-time limit of bb....bb, decreasing to match
aa....aa: Value specified in the ThreadLimit directive
bb....bb: Maximum limit of the ThreadLimit directive value
- Description
-
The ThreadLimit directive value exceeds the maximum limit. The Web server sets the maximum limit value for the ThreadLimit directive, and then continues processing.
- Action
-
Revise the ThreadLimit directive value.
-
AH00309
changing ThreadLimit to aa....aa from original value of bb....bb not allowed during restart
aa....aa: Value specified in the ThreadLimit directive when restarting the Web server
bb....bb: Value specified in the ThreadLimit directive when starting the Web server
- Description
-
The ThreadLimit directive value cannot be changed for restarting the Web server. The Web server sets the ThreadLimit directive to the value that was specified when the Web server started, and then continues processing.
- Action
-
If you need to change the ThreadLimit directive value, stop the Web server, and then restart it.
-
AH00310
WARNING: ThreadsPerChild of aa....aa exceeds ThreadLimit of
bb....bb threads, decreasing to bb....bb.
To increase, please see the ThreadLimit directive.
aa....aa: Value specified in the ThreadsPerChild directive
bb....bb: Value specified in the ThreadLimit directive
- Description
-
The ThreadsPerChild directive value exceeds the ThreadLimit directive value. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues the startup processing.
- Action
-
If you need to increase the ThreadsPerChild directive value, you must also change the ThreadLimit directive value.
-
AH00311
ThreadsPerChild of aa....aa exceeds ThreadLimit of bb....bb, decreasing to match
aa....aa: Value specified in the ThreadsPerChild directive
bb....bb: Value specified in the ThreadLimit directive
- Description
-
The ThreadsPerChild directive value exceeds the ThreadLimit directive value. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues processing.
- Action
-
If you need to increase the ThreadsPerChild directive value, you must also change the ThreadLimit directive value.
-
AH00344
accept() failed.
- Description
-
An error occurred in the accept() function. The process of accepting the requests continues.
- Action
-
Revise the specification according to the detailed information about accept() shown in this message.
-
AH00346
getsockname failed
- Description
-
getsockname() has failed. The server thread will be in the request-awaiting state.
- Action
-
Revise the specification according to the detailed information about getsockname() shown in this message.
-
AH00347
getpeername failed
- Description
-
getpeername() has failed. The server thread will continue the request processing without setting up socket information of the client.
- Action
-
Revise the specification according to the detailed information about getpeername() shown in this message.
-
AH00348
Child: Accept thread exiting.
- Description
-
The request reception thread is terminated.
-
AH00350
Child: Failed to create a max_requests event.
- Description
-
The server process has failed to generate an event for the maximum number of requests. The server process terminates.
- Action
-
Revise the specification according to the detailed information about CreateEvent() shown in this message.
-
AH00351
Child: Failed to acquire the start_mutex. Process will exit.
- Description
-
An attempt to acquire the lock for mutual exclusion of server process has failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information about WaitForSingleObject shown in this message.
-
AH00353
Child: Failed to create a qwait event.
- Description
-
The server process failed to generate an event for queue operation. The server process terminates.
- Action
-
Revise the specification according to the detailed information about CreateEvent() shown in this message.
-
AH00354
Child: Starting aa....aa worker threads.
aa....aa: Number of threads
- Description
-
Generation of server threads for the number indicated in aa....aa will start.
-
AH00355
Child: CreateThread failed. Unable to create all worker threads. Created aa....aa of the bb....bb threads requested with the ThreadsPerChild configuration directive.
aa....aa: Number of generated threads
bb....bb: Directive value
- Description
-
An attempt to generate a thread failed during generation of server threads for the number specified in the ThreadsPerChild directive. The server process requests the control process to stop the Web server.
- Action
-
Revise the specification according to the detailed information about CreateThread() shown in this message.
-
AH00356
Child: WAIT_FAILED -- shutting down server
- Description
-
The server process has failed to wait for the termination event, planned termination event, or the event for the maximum number of requests. The server process terminates.
- Action
-
Revise the specification according to the detailed information about WaitForMultipleObjects() shown in this message.
-
AH00360
Child: Failure releasing the start mutex
- Description
-
An attempt to release the lock for mutual exclusion of server process has failed. The server process continues the end processing.
- Action
-
Revise the specification according to the detailed information about ReleaseMutex() shown in this message.
-
AH00362
Child: Waiting aa....aa more seconds for bb....bb worker threads to finish.
aa....aa: Remaining number of seconds to wait for the server threads to terminate
bb....bb: Number of running server threads
- Description
-
The server process will wait for termination of the server threads for aa....aa seconds.
-
AH00363
Child: Terminating aa....aa threads that failed to exit.
aa....aa: Number of server threads that have not terminated
- Description
-
The un-terminated server threads will be terminated forcibly.
-
AH00364
Child: All worker threads have exited.
- Description
-
All server threads have terminated.
-
AH00365
Failure registering service handler
- Description
-
An attempt to register the service control request processing function in the service control manager has failed. The service startup processing stops.
- Action
-
Revise the specification according to the detailed information about RegisterServiceCtrlHandler() shown in this message.
-
AH00366
Error starting service control dispatcher
- Description
-
An attempt to set up the service control dispatcher thread in the service control manager has failed. The service startup processing stops.
- Action
-
Revise the specification according to the detailed information about StartServiceCtrlDispatcher() shown in this message.
-
AH00367
No ConfigArgs registered for aa....aa, perhaps this service is not installed?
aa....aa: Service name
- Description
-
The registry entry ConfigArgs of the service described in the aa....aa does not exist. The Web server continues the startup processing.
- Action
-
Confirm that the service has been installed.
-
AH00382
OpenEvent on aa....aa event
aa....aa: Event name
- Description
-
An attempt to open the event has failed. The Web server stops the termination and restart processing.
- Action
-
Revise the specification according to the detailed information about OpenEvent() shown in this message.
-
AH00383
SetEvent on aa....aa event
aa....aa: Event name
- Description
-
An attempt to report the event has failed. The Web server stops the termination and restart processing.
- Action
-
Revise the specification according to the detailed information about SetEvent() shown in this message.
-
AH00384
Child: Unable to retrieve the ready event from the parent
- Description
-
The start event handle of the server process could not be acquired from the control process. The server process terminates.
- Action
-
Revise the specification according to the detailed information about ReadFile() shown in this message.
-
AH00385
Child: Unable to retrieve the exit event from the parent
- Description
-
The end event handle of the server process could not be acquired from the control process. The server process terminates.
- Action
-
Revise the specification according to the detailed information about ReadFile() shown in this message.
-
AH00386
Child: Unable to retrieve the start_mutex from the parent
- Description
-
The handler for the mutual exclusion could not be retrieved from the control process.
- Action
-
Revise the specification according to the detailed information about ReadFile() shown in this message.
-
AH00387
Child: Unable to access the start_mutex from the parent
- Description
-
The handler for mutual exclusion could not be accessed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00388
Child: Unable to retrieve the scoreboard from the parent
- Description
-
The handler for the scoreboard could not be acquired from the control process. The server process terminates.
- Action
-
Revise the specification according to the detailed information about ReadFile() shown in this message.
-
AH00389
Child: Unable to access the scoreboard from the parent
- Description
-
The scoreboard could not be accessed. The server process terminates.
- Action
-
Revise the specification according to the detailed information about MapViewOfFile() shown in this message.
-
AH00390
Child: Unable to reopen the scoreboard from the parent
- Description
-
The scoreboard could not be opened. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00392
Parent: Unable to duplicate the ready event handle for the child
- Description
-
The start event handle of the server process could not be duplicated. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about DuplicateHandle() shown in this message.
-
AH00393
Parent: Unable to send the ready event handle to the child
- Description
-
The start event handle of the server process could not be sent. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00394
Parent: Unable to duplicate the exit event handle for the child
- Description
-
The end event handle of the server process could not be duplicated. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about DuplicateHandle() shown in this message.
-
AH00395
Parent: Unable to send the exit event handle to the child
- Description
-
The end event handle could not be sent to the server process. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00397
Parent: Unable to duplicate the start mutex to the child
- Description
-
The handle for mutual exclusion could not be duplicated. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about DuplicateHandle() shown in this message.
-
AH00398
Parent: Unable to send the start mutex to the child
- Description
-
The handle for mutual exclusion could not be sent to the server process. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00400
Parent: Unable to duplicate the scoreboard handle to the child
- Description
-
The handle for the scoreboard could not be duplicated. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about DuplicateHandle() shown in this message.
-
AH00401
Parent: Unable to send the scoreboard handle to the child
- Description
-
The handle for the scoreboard could not be sent to the server process. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00404
Child: Unable to read socket data from parent
- Description
-
The socket data from the control process could not be read. The server process terminates.
- Action
-
Revise the specification according to the detailed information about ReadFile() shown in this message.
-
AH00405
Child: WSASocket failed to open the inherited socket
- Description
-
An attempt to open the inherited data has failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information about WSASocket() shown in this message.
-
AH00406
Child: SetHandleInformation failed
- Description
-
An attempt to set up properties for the object handle has failed. The server process continues the initialization processing.
- Action
-
Revise the specification according to the detailed information about SetHandleInformation() shown in this message.
-
AH00409
Parent: WSADuplicateSocket failed for socket aa....aa.
aa....aa: File descriptor (fd) number
- Description
-
The control process failed to duplicate the socket. The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information about WSADuplicateSocket() shown in this message.
-
AH00410
Parent: Unable to write duplicated socket aa....aa to the child.
aa....aa: File descriptor (fd) number
- Description
-
The control process failed to write the duplicated socket to the server process. The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00412
Parent: Failed to get the current path
- Description
-
An attempt to acquire current thread information has failed. The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00413
Parent: Failed to get full path of aa....aa
aa....aa: Startup command
- Description
-
An attempt to acquire the absolute path of the aa....aa has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00414
Parent: Unable to create child stdin pipe.
- Description
-
An attempt to generate a pipe for sending information to the server process has failed. The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00415
Parent: Could not create ready event for child process
- Description
-
An attempt to generate a start event for the server process has failed. The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information about CreateEvent() shown in this message.
-
AH00416
Parent: Could not create exit event for child process
- Description
-
An attempt to generate an end event for the server process has failed. The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information about CreateEvent() shown in this message.
-
AH00417
Parent: Failed to create the child process.
- Description
-
An attempt to generate the server process has failed. The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00418
Parent: Created child process aa....aa
aa....aa: Process ID
- Description
-
A server process was created.
-
AH00419
master_main: create child process failed. Exiting.
- Description
-
The control process failed to generate the server process. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00420
master_main: WaitForMultipleObjects WAIT_FAILED -- doing server shutdown
- Description
-
The control process has failed to wait for the termination event, planned termination event, or restart event. The Web server will shut down.
- Action
-
Revise the specification according to the detailed information about WaitForMultipleObjects() shown in this message.
-
AH00421
master_main: WaitForMultipleObjects with INFINITE wait exited with WAIT_TIMEOUT
- Description
-
A timeout occurred when the server process was waiting for the termination event, planned termination event, or restart event, even when INFINETE was specified. The Web server will shut down.
- Action
-
Revise the specification according to the detailed information about WaitForMultipleObjects() shown in this message.
-
AH00422
Parent: Received shutdown signal -- Shutting down the server.
- Description
-
The termination event was reported to the control process. The Web server starts the termination processing.
-
AH00423
ResetEvent(shutdown_event)
- Description
-
The control process failed to release the termination event. The Web server continues the termination processing.
- Action
-
Revise the specification according to the detailed information about ResetEvent() shown in this message.
-
AH00424
Parent: Received restart signal -- Restarting the server.
- Description
-
The restart event was reported to the control process. The Web server starts the restart processing.
-
AH00425
Parent: ResetEvent(restart_event) failed.
- Description
-
The control process failed to release the restart event. The Web server continues the restart processing.
- Action
-
Revise the specification according to the detailed information about ResetEvent() shown in this message.
-
AH00426
Parent: SetEvent for child process event aa....aa failed.
aa....aa: Handle number
- Description
-
The control process has failed to set up a termination event for the server process. The Web server continues the restart processing.
- Action
-
Revise the specification according to the detailed information about SetEvent() shown in this message.
-
AH00427
Parent: child process aa....aa exited with status bb....bb -- Aborting.
aa....aa: Process ID
bb....bb: End code
- Description
-
The server process terminated with the bb....bb. The termination processing of the Web server will start.
- Action
-
Revise according to the cause described in the end code.
-
AH00428
Parent: child process aa....aa exited with status bb....bb -- Restarting.
aa....aa: Process ID
bb....bb: End code
- Description
-
The server process ended with bb....bb. The Web server starts the restart processing.
-
AH00429
Parent: SetEvent for child process event aa....aa failed
aa....aa: Handle number
- Description
-
The control process has failed to set up a termination event for the server process. The termination processing of the Web server will continue.
- Action
-
Revise the specification according to the detailed information about SetEvent() shown in this message.
-
AH00430
Parent: Child process aa....aa exited successfully.
aa....aa: Process ID
- Description
-
The server process ended successfully. The Web server continues the termination processing.
-
AH00431
Parent: Forcing termination of child process aa....aa
aa....aa: Process ID
- Description
-
The control process will forcibly terminate the server process that does not terminate with the specified termination event. The Web server continues the termination processing.
- Action
-
Revise the cause due to which the server process does not terminate.
-
AH00432
Failed to get the full path of aa....aa
aa....aa: Startup command
- Description
-
An attempt to acquire the absolute path of the aa....aa has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00433
aa....aa: Service is already installed.
aa....aa: Service name
- Description
-
An attempt was made to install an already installed service. The service installation processing in the Web server will be interrupted.
- Action
-
Check the service.
-
AH00434
Using ConfigArgs of the installed service "aa....aa".
aa....aa: Service name
- Description
-
The registry entry ConfigArgs of the service specified in the aa....aa is used in the startup option.
-
AH00435
No installed ConfigArgs for the service "aa....aa", using Server defaults.
aa....aa: Service name
- Description
-
The default settings will be used for startup because the contents of the registry entry ConfigArgs of the service specified in the aa....aa cannot be acquired. The Web server continues the start processing.
- Action
-
Make sure that the registry entry ConfigArgs exists below the registry key of the aa....aa.
-
AH00436
No installed service named "aa....aa".
aa....aa: Service name
- Description
-
An uninstalled service is specified. The Web server stops the start processing.
- Action
-
Check the service.
-
AH00437
No installed service named "aa....aa".
aa....aa: Service name
- Description
-
An uninstalled service is specified. The Web server stops the start processing.
- Action
-
Check the service.
-
AH00438
aa....aa: Unable to start the service manager.
aa....aa: Service name
- Description
-
An attempt to start the service has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00444
WARNING: ThreadsPerChild of aa....aa exceeds ThreadLimit of
bb....bb threads, decreasing to cc....cc.
To increase, please see the ThreadLimit directive.
aa....aa: Value specified in the ThreadsPerChild directive
bb....bb: Value specified in the ThreadLimit directive
cc....cc: Value specified in the ThreadLimit directive
- Description
-
A value exceeding the specifiable maximum limit is specified for the ThreadsPerChild directive. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues the startup processing.
- Action
-
Revise the ThreadsPerChild directive and ThreadLimit directive values.
-
AH00445
ThreadsPerChild of aa....aa exceeds ThreadLimit of bb....bb, decreasing to match
aa....aa: Value specified in the ThreadsPerChild directive
bb....bb: Value specified in the ThreadLimit directive
- Description
-
A value exceeding the specifiable maximum limit is specified for the ThreadsPerChild directive. The Web server sets the ThreadLimit directive value for the ThreadsPerChild directive value, and then continues the startup processing.
- Action
-
Revise the ThreadsPerChild directive and ThreadLimit directive values.
-
AH00446
WARNING: ThreadsPerChild of aa....aa not allowed, increasing to 1.
aa....aa: Specified value
- Description
-
An invalid value is specified in ThreadsPerChild directive. 1 will be set up for the ThreadsPerChild directive value of the Web server, and the startup processing will continue.
- Action
-
Revise the ThreadsPerChild directive value.
-
AH00448
Parent: Cannot create shutdown event aa....aa
aa....aa: Event name
- Description
-
The control process has failed to generate the termination event. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about CreateEvent() shown in this message.
-
AH00449
Parent: Cannot create restart event aa....aa
aa....aa: Event name
- Description
-
The control process has failed to generate the restart event. The Web server stops the restart processing.
- Action
-
Revise the specification according to the detailed information about CreateEvent() shown in this message.
-
AH00450
aa....aa: Unable to create the start_mutex.
aa....aa: Service name
- Description
-
An attempt to generate an executive handler has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information about CreateMutexW() shown in this message.
-
AH00451
no listening sockets available, shutting down
- Description
-
There is no socket in the listen status. The Web server stops the start processing.
- Action
-
Based on the Listen directive, make sure that the cause of occurrence is not the failure to generate a socket.
-
AH00455
aa....aa configured -- resuming normal operations
aa....aa: Server name
- Description
-
The startup of the Web server has started.
-
AH00456
Server built: aa....aa
aa....aa: Time when Web server was created
- Description
-
The time of creation of the Web server that is started is displayed.
-
AH00526
Syntax error on line aa....aa of bb....bb:
cc....cc
aa....aa: Line number
bb....bb: File name
cc....cc: Error message
- Description
-
A syntax error exists at the position specified in the bb....bb and aa....aa. The Web server stops the start processing.
- Action
-
Based on cc....cc, revise the line in which the syntax error occurred.
-
AH00529
aa....aa pcfg_openfile: unable to check htaccess file, ensure it is readable and that 'bb....bb' is executable
aa....aa: Access control file name
bb....bb: File name
- Description
-
The access control file cannot be read.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the access control file according to the detailed information shown in this message.
-
AH00532
Invalid config file path aa....aa
aa....aa: Config file name
- Description
-
The path of the configuration file is invalid. The Web server stops the start processing.
- Action
-
Revise according to the path specified in aa....aa.
-
AH00534
httpsd: Configuration error: aa....aa
aa....aa: No MPM loaded., More than one MPM loaded., or The MPM cannot be changed during restart.
- Description
-
An error exists in the specification for loading the MPM module. The Web server stops the startup or restart processing.
- Action
-
Revise the LoadModule directive concerning the MPM module.
-
AH00542
apr_socket_opt_set: (TCP_NODELAY)
- Description
-
An error occurred during the setup of the IP protocol-level option TCP_NODELAY. The Web server continues the start processing without the setup of the TCP_NODELAY option. The Nagle buffering algorithm is enabled.
- Action
-
Revise the specification according to the detailed information about setsockopt() shown in this message.
-
AH00543
aa....aa: bad user name bb....bb
aa....aa: Command name
bb....bb: User name
- Description
-
The specified user is not registered in the system. The processing terminates.
- Action
-
Specify the user name registered in the system.
-
AH00544
aa....aa: bad group name bb....bb
aa....aa: Command name
bb....bb: Group name
- Description
-
The specified group is not registered in the system. The processing terminates.
- Action
-
Specify the group name registered in the system.
-
AH00547
Could not resolve host name aa....aa -- ignoring!
aa....aa: Virtual host name -
- Description
-
The specification will be ignored because an invalid virtual host is specified. The Web server continues the start processing.
- Action
-
Revise the host name specified in the VirtualHost directive.
-
AH00548
NameVirtualHost has no effect and will be removed in the next release aa....aa:bb....bb
aa....aa: Config file name
bb....bb: Line number
- Description
-
The specified NameVirtualHost directive is ignored. The Web server continues the start processing.
- Action
-
Delete the specified NameVirtualHost directive from the portion shown in the message.
-
AH00549
Failed to resolve server name for aa....aa (check DNS) -- or specify an explicit ServerName
aa....aa: IP address
- Description
-
An attempt to resolve the host name specified in the VirtualHost directive has failed. The virtual host whose host name could not be resolved in the Web server will be ignored, and the startup processing will continue. The virtual host that could not be resolved is not recognized as a virtual host.
- Action
-
Revise the host name specified in the VirtualHost directive.
-
AH00554
Access to file aa....aa denied by server: not a regular file
aa....aa: file name
- Description
-
The Web server denied the access to the file because the file is not a standard file. The Web server stops the start processing.
- Action
-
Check to make sure that the accessed file is a standard file.
-
AH00556
aa....aa: apr_gethostname() failed to determine ServerName
aa....aa: Command name
- Description
-
An attempt to determine ServerName with gethostname() has failed. The Web server address will be assumed as 127.0.0.1.
- Action
-
Revise according to the cause because of which the host name cannot be acquired.
-
AH00558
aa....aa: Could not reliably determine the server's fully qualified domain name, using bb....bb. Set the 'ServerName' directive globally to suppress this message
aa....aa: Command name
bb....bb: Web server name
- Description
-
The Web server name will be used as the ServerName because the complete domain name of the server could not be resolved. The Web server name will be used as ServerName.
-
AH00562
Request header exceeds LimitRequestFieldSize after folding: aa....aa
aa....aa: Request header name
- Description
-
The request header size exceeds the LimitRequestFieldSize directive value.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Make sure that the request header size does not exceed the LimitRequestFieldSize directive value.
-
AH00563
Number of request headers exceeds LimitRequestFields
- Description
-
The number of request headers exceeds the LimitRequestFields directive value.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Make sure that the number of request headers does not exceed the LimitRequestFields directive value.
-
AH00565
request failed: client's request-line exceeds LimitRequestLine (longer than aa....aa)
aa....aa: LimitRequestLine directive value
- Description
-
The length of the request line exceeds the LimitRequestLine directive value.
The status code 414 Request-URI Too Large will be returned to the client, and the request processing will be interrupted.
- Action
-
Check to make sure that the string specified in the request line (URI or HTTP version, including the methods and query strings) does not exceed the LimitRequestLine directive value.
-
AH00567
request failed: error reading the headers
- Description
-
An error occurred while the request header was being read.
The status code 400 Bad Request or 408 Request Time-out will be returned to the client, and the request processing will be interrupted.
- Action
-
Make sure that a valid request header is specified. Also make sure that the number of request headers does not exceed the maximum limit specified by the server.
-
AH00569
client sent HTTP/1.1 request without hostname (see RFC2616 section 14.23): aa....aa
aa....aa: Requested URI value
- Description
-
The request processing cannot be continued because the client has sent the HTTP/1.1 request without adding the HOST header.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Make sure that the HOST header is added to the HTTP/1.1 request.
-
AH00571
need AuthType to note auth failure: aa....aa
aa....aa: Requested URI value
- Description
-
The authentication type name to be specified in the AuthType directive during user authentication is not specified.
The status code 401 Authorization Required will be returned, and the request processing will terminate.
- Action
-
Specify the AuthType directive when performing user authentication.
-
AH00572
need AuthName: aa....aa
aa....aa: Requested URI value
- Description
-
The realm name to be specified in the AuthName directive during user authentication is not specified.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Specify the AuthName directive when performing user authentication.
-
AH00573
client used wrong authentication scheme: aa....aa
aa....aa: Requested URI value
- Description
-
The type of authentication control of the Authorization header during user authentication is invalid.
The status code 401 Authorization Required will be returned, and the request processing will terminate.
- Action
-
Only Basic can be specified in the Authorization header. Revise the specified value of the Authorization header.
-
AH00574
ap_content_length_filter: apr_bucket_read() failed
- Description
-
An attempt to read the response data has failed.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00648
invalid transfer log path aa....aa.
aa....aa: File name
- Description
-
The log file is invalid. The Web server stops the start processing.
- Action
-
Revise the settings of the TransferLog directive or CustomLog directive.
-
AH00649
could not open transfer log file aa....aa.
aa....aa: File name
- Description
-
Cannot open the log file. The Web server stops the start processing.
- Action
-
Revise the settings of the TransferLog directive or CustomLog directive.
-
AH00652
File does not exist: aa....aa
aa....aa: File name
- Description
-
The requested file cannot be found.
The status code 404 Not Found will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the requested file name.
-
AH00671
The aa....aa directive in bb....bb at line cc....cc will probably never match because it overlaps an earlier dd....dd.
aa....aa: Directive
bb....bb: Config file name
cc....cc: Line number
dd....dd: Directive
- Description
-
A directive that can be applied to the same URL is specified twice. The second specification will not be applicable.
- Action
-
Revise the settings of the directive in the displayed line.
-
AH00674
cannot redirect 'aa....aa' to 'bb....bb'; target is not a valid absoluteURI or abs_path
aa....aa: Request URI
bb....bb: Redirect destination
- Description
-
Cannot redirect to the redirect destination. The specified redirect destination is not a URL.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Make sure that the specified redirect destination is a URL.
-
AH00676
cannot redirect 'aa....aa' to 'bb....bb'; target is not a valid absoluteURI or abs_path
aa....aa: Request URI
bb....bb: Redirect destination
- Description
-
Cannot redirect to the redirect destination. The specified redirect destination is not a URL.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Make sure that the specified redirect destination is a URL.
-
AH00690
no acceptable variant: aa....aa
aa....aa: File name
- Description
-
The client cannot accept the results of content negotiation by the Web server.
The status code 406 Not Acceptable will be returned, and the request processing will terminate.
-
AH00898
aa....aa returned by bb....bb
aa....aa: Message
bb....bb: Request URI
- Description
-
An error indicated in aa....aa occurred.
- Action
-
Check the cause of the message.
-
AH00940
aa....aa: disabled connection for (bb....bb)
aa....aa: Scheme name
bb....bb: Transfer destination host name
- Description
-
The transfer destination host could not be connected.
- Action
-
Make sure that connection with the transmission-destination host specified in the ProxyPass directive is possible.
-
AH00952
aa....aa: error creating fam bb....bb socket for target cc....cc
aa....aa: Scheme name
bb....bb: Address family
cc....cc: Host name
- Description
-
An attempt to create a socket has failed.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00957
aa....aa: attempt to connect to bb....bb:cc....cc (dd....dd) failed
aa....aa: Scheme name
bb....bb: IP address
cc....cc: Port number
dd....dd: Host name
- Description
-
An attempt to connect to the remote Web server failed.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH00959
ap_proxy_connect_backend disabling worker for (aa....aa) for bb....bbs
aa....aa: Host name
bb....bb: Number of seconds
- Description
-
Connection to aa....aa will be disabled for bb....bb seconds.
-
AH01083
error parsing URL aa....aa: bb....bb
aa....aa: URL
bb....bb: Detailed information
- Description
-
An error occurred during the analysis of the URL by the reverse proxy.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the URL specified in the ProxyPass directive according to the cause specified in bb....bb.
-
AH01084
pass request body failed to aa....aa:bb....bb (cc....cc)
aa....aa: IP address
bb....bb: Port number
cc....cc: Host name
- Description
-
The reverse proxy failed to send the request body to the remote Web server.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01087
client aa....aa given Content-Length did not match number of body bytes read
aa....aa: Client address
- Description
-
The size of the request body sent by the client is different from the value of the Content-Length header.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Check to make sure that the value of the Content-Length request header is correct.
-
AH01088
Request body is larger than the configured limit of aa....aa
aa....aa: LimitRequestBody directive value
- Description
-
A body of a size larger than the aa....aa was read.
The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specified value of the LimitRequestBody directive. Specify 0 if no upper-limit value is set up for the request body size.
-
AH01089
search for temporary directory failed
- Description
-
The reverse proxy failed to search the directory that temporarily stores the request body.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01090
creation of temporary file in directory aa....aa failed
aa....aa: Directory name
- Description
-
The reverse proxy failed to create the file that temporarily stores the request body.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01091
write to temporary file aa....aa failed
aa....aa: File name
- Description
-
The reverse proxy failed to write in the file that temporarily stores the request body.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01092
no HTTP 0.9 request (with no host line) on incoming request and preserve host set forcing hostname to be aa....aa for uri bb....bb
aa....aa: Host name
bb....bb: URI
- Description
-
The Host header is not included in the request header received from the client.
The processing will continue by sending the Host header created in the reverse proxy to the remote Web server.
- Action
-
Revise the client settings.
-
AH01093
aa....aa Transfer-Encoding is not supported
aa....aa: Transfer-Encoding header value
- Description
-
The Transfer-Encoding header value sent by the client is not supported.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Specify chunked for the Transfer-Encoding header value.
-
AH01095
prefetch request body failed to aa....aa:bb....bb (cc....cc) from dd....dd (ee....ee)
aa....aa: IP address
bb....bb: Port number
cc....cc: Host name
dd....dd: Client address
ee....ee: Client host name
- Description
-
The reverse proxy failed to receive the request body from the client.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01096
processing prefetched request body failed to aa....aa:bb....bb (cc....cc) from dd....dd (ee....ee)
aa....aa: IP address
bb....bb: Port number
cc....cc: Host name
dd....dd: Client address
ee....ee: Client host name
- Description
-
The reverse proxy failed to receive the request body from the client.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01097
pass request body failed to aa....aa:bb....bb (cc....cc) from dd....dd (ee....ee)
aa....aa: IP address
bb....bb: Port number
cc....cc: Host name
dd....dd: Client address
ee....ee: Client host name
- Description
-
The reverse proxy failed to send the request body.
-
AH01102
error reading status line from remote server aa....aa:bb....bb
aa....aa: IP address
bb....bb: Port number
- Description
-
The reverse proxy failed to read the status line from the remote Web server.
The status code 502 Proxy Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01106
bad HTTP/aa....aa.bb....bb header returned by cc....cc (dd....dd)
aa....aa: Major version
bb....bb: Minor version
cc....cc: URI
dd....dd: Method
- Description
-
The remote Web server has sent an invalid HTTP header.
The status code 502 Bad Gateway will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the settings of the remote Web server.
-
AH01110
error reading response
- Description
-
The reverse proxy failed to read the response body from the remote Web server.
The status code 502 Bad Gateway will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01114
HTTP: failed to make connection to backend: aa....aa
aa....aa: Host name
- Description
-
The reverse proxy failed to establish a connection with the remote Web server.
-
AH01139
TRACE forbidden by server configuration
- Description
-
The request issued by the TRACE method is denied because of the settings of the TraceEnable directive.
The status code 405 Method Not Allowed will be returned to the client, and the request processing will be interrupted.
- Action
-
To allow access, revise the settings of the TraceEnable directive.
-
AH01140
TRACE with request body is not allowed
- Description
-
The request issued by the TRACE method having a request body is denied because of the settings of the TraceEnable directive.
The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.
- Action
-
To allow access, revise the settings of the TraceEnable directive.
-
AH01144
No protocol handler was valid for the URL aa....aa. If you are using a DSO version of mod_proxy, make sure the proxy submodules are included in the configuration using LoadModule.
aa....aa: URL
- Description
-
The schema specified in the ProxyPass directive is invalid.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the transfer-destination schema of the ProxyPass directive.
-
AH01145
Sharing worker 'aa....aa' instead of creating new worker 'bb....bb'
aa....aa: URL1
bb....bb: URL2
- Description
-
The ProxyPass directive corresponding to URL2 shares the connection and settings with the ProxyPass directive corresponding to URL1.
-
AH01146
Ignoring parameter 'aa....aa' for worker 'bb....bb' because of worker sharing
aa....aa: Key specification in the ProxyPass directive
bb....bb: URL
- Description
-
The key specification in the ProxyPass directive corresponding to the URL is ignored, and the value of another ProxyPass directive that shares the settings will be used.
- Action
-
Revise the key specification in the ProxyPass directive.
-
AH01222
don't know how to spawn child process: aa....aa
aa....aa: File name
- Description
-
The process cannot be generated.
The status code 500 Internal Server Error will be returned, and the request processing will terminate.
- Action
-
Check the system status according to the detailed information shown in this message.
-
AH01223
couldn't spawn child process: aa....aa
aa....aa: File name
- Description
-
The process for the CGI program could not be generated.
The status code 500 Internal Server Error will be returned, and the request processing will terminate.
- Action
-
Check the system status according to the detailed information shown in this message.
-
AH01224
Timeout during reading request entity data
- Description
-
A timeout occurred when the request body was received from the client.
The status code 408 Request Time-out will be returned to the client, and the request processing will be interrupted.
- Action
-
Check the cause of the timeout.
-
AH01225
Error reading request entity data
- Description
-
An attempt to receive the request body from the client failed.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01275
Can't open directory for index: aa....aa
aa....aa: Directory name
- Description
-
The directory for directory indexing cannot be opened.
The status code 403 Forbidden will be returned to the client, and the request processing will be interrupted.
- Action
-
Check the system status according to the detailed information shown in this message.
-
AH01276
Cannot serve directory aa....aa: No matching DirectoryIndex (bb....bb) found, and server-generated directory index forbidden by Options directive
aa....aa: Directory name
bb....bb: Value specified in the DirectoryIndex directive
- Description
-
The directory index cannot be displayed due to the setting in the Options directive.
The status code 403 Forbidden will be returned, and the request processing will terminate.
- Action
-
To enable the directory index, change the setting in the Options directive.
-
AH01382
Request aa....aa read timeout
aa....aa: header or body
- Description
-
A timeout occurred during reception processing of the request header (including the request line) from the client or during reception processing of the request body.
- Action
-
This message was output because the time specified in the RequestReadTimeout directive elapsed. Revise the value specified in the RequestReadTimeout directive.
-
AH01506
PassEnv variable aa....aa was undefined
aa....aa: Environment variable
- Description
-
The aa....aa specified in the PassEnv directive is not defined as an environment variable.
- Action
-
Set up the environment variable.
-
AH01574
module aa....aa is already loaded, skipping
aa....aa: Module name
- Description
-
The processing will not be executed because the Web server is already incorporated into the module.
- Action
-
Revise the description of the LoadModule directive.
-
AH01580
Invalid error redirection directive: aa....aa
aa....aa: Redirect destination
- Description
-
A grammatical error exists in the customization method specified in the ErrorDocument directive. The error status number will not be customized.
- Action
-
To customize the error messages with the ErrorDocument directive, specify the text, local URL, or full URL. For details, see the explanation about the ErrorDocument directive.
-
AH01585
Unknown Transfer-Encoding: aa....aa
aa....aa: Transfer-Encoding header value
- Description
-
The value specified in the Transfer-Encoding header is invalid.
The status code 501 Method Not Implemented will be returned to the client, and the request processing will be interrupted.
- Action
-
Other than chunked is specified in the Transfer-Encoding header. Revise the Transfer-Encoding header.
-
AH01586
Unknown Transfer-Encoding: aa....aa; using Content-Length
aa....aa: Transfer-Encoding header value
- Description
-
The value specified in the Transfer-Encoding header is invalid.
The processing continues using the Content-Length header value.
- Action
-
Other than chunked is specified in the Transfer-Encoding header. Revise the Transfer-Encoding header.
-
AH01587
Invalid Content-Length
- Description
-
The length specified in the Content-Length header is invalid.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
You can only specify a numeric value (decimal number) in the Content-Length header. Revise the specified value.
-
AH01588
Requested content-length of aa....aa is larger than the configured limit of bb....bb
aa....aa: Specified length (bytes)
bb....bb: LimitRequestBody directive value (bytes)
- Description
-
A value greater than the LimitRequestBody directive value is specified as the length in the Content-Length header.
The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specified value of the LimitRequestBody directive. Specify 0 if no upper-limit value is set up for the request body size.
-
AH01589
Error reading first chunk aa....aa
aa....aa: (overflow) or null
- Description
-
The correct chunk size could not be acquired.
The status code 400 Bad Request or 408 Request Time-out will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01590
Error reading chunk aa....aa
aa....aa: (overflow) or null
- Description
-
The correct chunk size could not be acquired.
The status code 400 Bad Request or 408 Request Time-out will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH01591
Read content length of aa....aa is larger than the configured limit of bb....bb
aa....aa: Request body size that was read (bytes)
bb....bb: LimitRequestBody directive value (bytes)
- Description
-
A body of a size larger than the bb....bb was read.
The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the specified value of the LimitRequestBody directive. Specify 0 if no upper-limit value is set up for the request body size.
-
AH01596
Invalid mime types config path aa....aa
aa....aa: File name
- Description
-
The path of the file specified with the TypesConfig directive is invalid. The startup processing of the Web server will terminate.
- Action
-
Revise the settings of TypesConfig directive.
-
AH01597
could not open mime types config file aa....aa.
aa....aa: File name
- Description
-
The file specified with the TypesConfig directive cannot be opened. The startup processing of the Web server will terminate.
- Action
-
Revise the settings of TypesConfig directive.
-
AH01598
mod_mime: analyze_ct: cannot get media type from 'aa....aa'
aa....aa: Media type
- Description
-
The media type of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01599
Cannot get media type from 'aa....aa'
aa....aa: Media type
- Description
-
The media subtype of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01600
mod_mime: analyze_ct: cannot get media type from 'aa....aa'
aa....aa: Media type
- Description
-
The media type of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01601
Cannot get media subtype.
- Description
-
The media subtype of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01602
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01603
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01604
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01605
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01606
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01607
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01608
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01609
Cannot get media parameter.
- Description
-
The media parameters of MIME cannot be acquired properly. The request process continues.
- Action
-
Revise the MIME settings.
-
AH01614
client used wrong authentication scheme: aa....aa
aa....aa: Requested URI value
- Description
-
The type of authentication control of the Authorization header during user authentication is invalid.
The status code 401 Authorization Required will be returned, and the request processing will terminate.
- Action
-
Only Basic can be specified in the Authorization header. Revise the specified value of the Authorization header.
-
AH01615
need AuthName: aa....aa
aa....aa: Requested URI value
- Description
-
The realm name to be specified in the AuthName directive during user authentication is not specified.
The status code 500 Internal Server Error will be returned to the client, and the request processing will be interrupted.
- Action
-
Specify the AuthName directive when performing user authentication.
-
AH01617
user aa....aa: authentication failure for "bb....bb": Password Mismatch
aa....aa: User name
bb....bb: Requested URI value
- Description
-
An authentication error occurred in the client from which the requested URI was attempted to be accessed.
The status code 401 Authorization Required will be returned, and the request processing will terminate.
- Action
-
Revise the password.
-
AH01618
user aa....aa not found: bb....bb
aa....aa: User name
bb....bb: Requested URI value
- Description
-
The user name sent from the client from which the requested URI was attempted to be accessed could not be found in the list of user names that can access the URI.
The status code 401 Authorization Required will be returned, and the request processing will terminate.
- Action
-
To allow access permission to the user, add the user name to the settings.
-
AH01627
AuthType configured with no corresponding authorization directives
- Description
-
A directive that must be specified together with the AuthType directive is not specified.
The status code 500 Internal Server Error will be returned, and the request processing will terminate.
- Action
-
Revise the specified directives concerning user authentication.
-
AH01630
client denied by server configuration: aa....aa
aa....aa: File name or requested URI value
- Description
-
Access was denied due to the server settings.
- Action
-
To allow access, change the settings.
-
AH01631
user aa....aa: authorization failure for "bb....bb":
aa....aa: User name
bb....bb: Requested URI value
- Description
-
The user who attempted to access the requested URI was denied.
The status code 401 Authorization Required or 403 Forbidden will be returned, and the request processing will terminate.
- Action
-
To allow access, change the settings.
-
AH01637
Authorization of user aa....aa to access bb....bb failed, reason: file owner cc....cc does not match.
aa....aa: User name
bb....bb: Requested URI value
cc....cc: Owner name
- Description
-
Access was not allowed because the user was not the file owner.
-
AH01663
access to aa....aa failed, reason: user 'bb....bb' does not meet 'require'ments for user to be allowed access
aa....aa: Requested URI value
bb....bb: User name
- Description
-
Access was not allowed because the user did not match the user specified in Require.
- Action
-
To allow access, change the settings.
-
AH01664
No group file was specified in the configuration
- Description
-
The AuthGroupFile directive is not specified.
- Action
-
To restrict access by group, specify the AuthGroupFile directive.
-
AH01665
Could not open group file: aa....aa
aa....aa: File name
- Description
-
The file specified with the AuthGroupFile directive cannot be opened.
- Action
-
Revise the settings of AuthGroupFile directive.
-
AH01666
Authorization of user aa....aa to access bb....bb failed, reason: user doesn't appear in group file (cc....cc).
aa....aa: User name
bb....bb: Requested URI value
cc....cc: Group file
- Description
-
Access was not allowed because the group of the user who attempted to access the requested URI was not in the group file.
- Action
-
To allow access, revise the file specified with the AuthGroupFile directive.
-
AH01667
Authorization of user aa....aa to access bb....bb failed, reason: user is not part of the 'require'ed group(s).
aa....aa: User name
bb....bb: Requested URI value
- Description
-
Access was not allowed because the user did not match the group specified in Require.
- Action
-
To allow access, change the settings.
-
AH01668
No group file was specified in the configuration
- Description
-
The AuthGroupFile directive is not specified.
- Action
-
To restrict access by group, specify the AuthGroupFile directive.
-
AH01669
Could not open group file: aa....aa
aa....aa: File name
- Description
-
The file specified with the AuthGroupFile directive cannot be opened.
- Action
-
Revise the settings of AuthGroupFile directive.
-
AH01670
Authorization of user aa....aa to access bb....bb failed, reason: user doesn't appear in group file (cc....cc).
aa....aa: User name
bb....bb: Requested URI value
cc....cc: Group file
- Description
-
Access was not allowed because the group of the user who attempted to access the requested URI was not in the group file.
- Action
-
To allow access, revise the file specified with the AuthGroupFile directive.
-
AH01671
Authorization of user aa....aa to access bb....bb failed, reason: user is not part of the 'require'ed file group.
aa....aa: User name
bb....bb: Requested URI value
- Description
-
Access was not allowed because the user did not match the file group specified in Require.
- Action
-
To allow access, change the settings.
-
AH01796
AuthType aa....aa configured without corresponding module
aa....aa: AuthType directive value
- Description
-
The module corresponding to the specified AuthType directive has not been loaded.
The status code 500 Internal Server Error will be returned, and the request processing will terminate.
- Action
-
Revise the AuthType directive value.
-
AH01797
client denied by server configuration: aa....aa
aa....aa: File name or requested URI value
- Description
-
Access was denied due to the server settings.
- Action
-
To allow access, change the settings.
-
AH02100
Failed to open cgi file aa....aa for testing
aa....aa: File name
- Description
-
An attempt to open the file failed. The process of executing the script will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH02101
Failed to read cgi file aa....aa for testing
aa....aa: File name
- Description
-
Failed to read the file. The process of executing the script will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH02102
aa....aa is not executable; ensure interpreted scripts have "#!" or "'!" first line
aa....aa: File name
- Description
-
The specified file cannot be executed. The startup of the CGI program stops.
- Action
-
Make sure that "#!" or "!" is specified in the first line.
-
AH02155
getpwuid: couldn't determine user name from uid aa....aa, you probably need to modify the User directive
aa....aa: User ID
- Description
-
An error occurred when searching for aa....aa in the password database. The Web server stops the start processing.
- Action
-
Revise the specification according to the value specified in the User directive and the detailed information returned by the getpwuid() function shown in this message.
-
AH02156
setgid: unable to set group id to Group aa....aa
aa....aa: Group ID
- Description
-
An attempt to specify the group ID has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information returned by the setgid() function shown in this message.
-
AH02157
initgroups: unable to set groups for User aa....aa and Group bb....bb
aa....aa: User name
bb....bb: Group ID
- Description
-
An attempt to initialize the group access list of the user has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information returned by the initgroups() function shown in this message.
-
AH02162
setuid: unable to change to uid: aa....aa
aa....aa: User ID
- Description
-
An attempt to specify the user ID has failed. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information returned by the setuid() function shown in this message.
-
AH02163
set dumpable failed - this child will not coredump after software errors
- Description
-
An attempt to set up the core dump has failed. The core will not be output even if an error occurs for the normal core dump of the server process.
- Action
-
Revise the specification according to the detailed information returned by the prctl() function shown in this message.
-
AH02177
apr_socket_accept: giving up.
- Description
-
An (ENETDOWN) error has occurred in the accept() function. The server process that received the request will exit.
- Action
-
Revise the specification according to the detailed information returned by the accept() function shown in this message.
-
AH02179
apr_socket_accept: (client socket)
- Description
-
An error occurred in the accept() function. The server process that received the request will exit.
- Action
-
Revise the specification according to the detailed information returned by the accept() function shown in this message.
-
AH02325
A resource shortage or other unrecoverable failure was encountered before any child process initialized successfully... httpsd is exiting!
- Description
-
A resource shortage or another unrecoverable failure occurred before the server process was initialized normally. The Web server will now end.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
AH02439
error parsing URL aa....aa: bb....bb
aa....aa: URL
bb....bb: Detailed information
- Description
-
An error occurred during analysis of the transfer destination URL.
The status code 400 Bad Request will be returned to the client, and the request processing will be interrupted.
- Action
-
Revise the URL specified in the ProxyPass directive according to the cause specified in bb....bb.
-
AH02441
error on aa....aa - ap_pass_brigade
aa....aa: client or backend
- Description
-
An error occurred during data send processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH02442
error on aa....aa - ap_get_brigade
aa....aa: client or backend
- Description
-
An error occurred during data reception processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH02443
error apr_pollset_create()
- Description
-
An error occurred in apr_pollset_create().
The status code 500 Internal Server Error will be returned, and the request processing will terminate.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH02444
error apr_poll()
- Description
-
An error occurred in apr_poll().
The status code 500 Internal Server Error will be returned, and the request processing will terminate.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH02447
error on backconn
- Description
-
An error occurred during connection with the back-end server. The WebSocket communication will now end.
-
AH02452
failed to make connection to backend: aa....aa
aa....aa: Host name
- Description
-
An attempt to establish a connection with the back-end server failed.
The status code 503 Service Unavailable will be returned, and the request processing will terminate.
- Action
-
Check the status of the transfer destination server.
-
AH02477
mod_proxy must be loaded for mod_proxy_http
- Description
-
To use the mod_proxy_http module, the mod_proxy module is required. The Web server stops the start processing.
- Action
-
Make sure that the mod_proxy module has been incorporated by using the LoadModule directive.
-
AH02605
unknown event on backconn aa....aa
aa....aa: Value indicating the event that occurred
- Description
-
An unexpected event concerning the connection with the back-end server occurred.
-
AH02606
unknown event on client conn aa....aa
aa....aa: Value indicating the event that occurred
- Description
-
An unexpected event concerning the connection with the client occurred.
-
AH02607
error on client conn
- Description
-
An error occurred during connection with the client. The WebSocket communication will now end.
-
AH02656
Error while reading HTTP trailer: aa....aabb....bb
aa....aa: Status code
bb....bb: Error information
- Description
-
An error occurred while chunk data was being read.
-
AH00002
Fatal error: unable to create global pool for use by the scoreboard
- Description
-
The area to be used with the scoreboard could not be secured. The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
AH03142
apr_thread_create: unable to create worker thread
- Description
-
An attempt to generate a server thread failed. The server process terminates.
- Action
-
Revise the specification according to the detailed information shown in this message.