23.5 Messages beginning with KH
This section describes the messages beginning with KH.
-
KH00001
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.
-
KH00002
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.
-
KH00004
Child: Graceful exit event signaled. Child process is ending.
- Description
-
The planned termination event was reported to the server process.
The planned termination processing of the server process will start.
-
KH00005
Child: Unable to retrieve the graceful exit event from the parent
- Description
-
The planned termination event handle of the server process could not be acquired.
The server process terminates.
- Action
-
Revise the specification according to the detailed information returned by the ReadFile() function shown in this message.
-
KH00006
Parent: Unable to duplicate the graceful exit event handle for the child
- Description
-
The planned termination 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 returned by the DuplicateHandle() function shown in this message.
-
KH00007
Parent: Unable to send the graceful exit event handle to the child
- Description
-
The planned termination 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.
-
KH00008
Parent: Could not create graceful exit event for child process
- Description
-
An attempt to generate a planned termination for the server process has failed.
The generation of the server process will now stop.
- Action
-
Revise the specification according to the detailed information returned by the CreateEvent() function shown in this message.
-
KH00009
Parent: Received graceful stop signal -- Shutting down the server gracefully.
- Description
-
The planned termination event was reported to the control process.
The Web server starts the planned termination processing.
-
KH00010
ResetEvent(graceful_stop_event)
- Description
-
The control process failed to release the planned termination event.
The planned termination processing of the Web server will continue.
- Action
-
Revise the specification according to the detailed information returned by the ResetEvent() function shown in this message.
-
KH00011
Parent: SetEvent for child process aa....aa failed
aa....aa: Handle value
- Description
-
The control process has failed to set up a planned termination event for the server process.
The planned termination processing of the Web server will continue.
- Action
-
Revise the specification according to the detailed information returned by the SetEvent() function shown in this message.
-
KH00012
Parent: Child process exited successfully.
- Description
-
The server process ended successfully.
The Web server continues the planned termination processing.
-
KH00013
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.
-
KH00014
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 returned by the ResetEvent() function shown in this message.
-
KH00015
Parent: Forcing termination of child process aa....aa
aa....aa: Handle number
- Description
-
The control process will forcibly terminate the server process that does not terminate with the specified planned termination event.
The Web server continues the planned termination processing.
- Action
-
Revise the cause due to which the server process does not terminate.
-
KH00016
Parent: Cannot create graceful stop event aa....aa
aa....aa: Event object name
- Description
-
The control process has failed to generate an event for planned termination.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information returned by the CreateEvent() function shown in this message.
-
KH00018
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.
-
KH00019
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.
-
KH00020
Unknown Transfer-Encoding aa....aa
aa....aa: 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.
-
KH00021
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.
-
KH00022
aa....aa with body is not allowed for bb....bb
aa....aa: Method
bb....bb: Requested URI value
- Description
-
Body is specified for a method for which the body is not allowed.
The status code 413 Request Entity Too Large will be returned to the client, and the request processing will be interrupted.
- Action
-
To allow a TRACE method to which the request body is added, specify extended in the TraceEnable directive. However, a request cannot be received if the request body size exceeds 64 KB.
-
KH00025
Child: Unable to retrieve the parent process handle from the parent
- Description
-
The process handle of the control process could not be acquired from the control process.
The server process terminates.
- Action
-
Revise the specification according to the detailed information returned by the ReadFile() function shown in this message.
-
KH00026
Parent: Unable to duplicate the parent process handle for the child
- Description
-
The process handle of the control process could not be duplicated.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information returned by the DuplicateHandle() function shown in this message.
-
KH00027
Parent: Unable to send the parent process handle to the child
- Description
-
The process handle of the control process 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.
-
KH00028
Child: Parent process exited. Child process is ending.
- Description
-
The termination of the control process was detected.
The termination processing of the server process will start.
-
KH00029
Parent: the child process exited before starting initialization.
- Description
-
The server process terminated before the initialization processing was started.
The Web server stops the start processing.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
KH00030
Parent: WaitForMultipleObjects failed.
- Description
-
The control process failed to await the initialization processing start event of the server process.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information returned by the WaitForSingleObject() function shown in this message.
-
KH00031
the service control dispatcher terminated before completing initialization of the service.
- Description
-
The service control dispatcher thread terminated before the service initialization processing was complete.
The startup processing of the service stops.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
KH00032
service initialization wait timed out.
- Description
-
A timeout occurred when the service startup process was awaiting the service initialization processing completion event.
The startup processing of the service stops.
- Action
-
Revise according to the cause of error described in messages output other than this message.
-
KH00033
WaitForMultipleObjects failed.
- Description
-
The service startup process failed to await the service initialization processing completion event.
The startup processing of the service stops.
- Action
-
Revise the specification according to the detailed information returned by the WaitForSingleObject() function shown in this message.
-
KH00034
Parent aa....aa: Using config file "bb....bb"
aa....aa: Control process ID
bb....bb: Config file name
- Description
-
The process ID of the control process, and the configuration file name used in the startup processing is displayed.
The Web server continues the startup processing.
-
KH00035
Parent aa....aa: Using config file "bb....bb"
aa....aa: Control process ID
bb....bb: Config file name
- Description
-
The process ID of the control process, and the configuration file name used in the startup processing is displayed.
The Web server continues the startup processing.
-
KH00037
The HWS trace could not open the log file aa....aa specified in the HWSTraceLogFile.
aa....aa: File name
- Description
-
The file described in the aa....aa specified in the HWSTraceLogFile directive cannot be opened.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00038
The HWS trace output the log of the process (pid=aa....aa) into the file bb....bb specified in the HWSTraceLogFile.
aa....aa: Process ID
bb....bb: File name
- Description
-
The contents of the shared memory of the process described in the aa....aa were output in the file described in bb....bb specified in the HWSTraceLogFile directive.
The output in the file is terminated successfully, and the processing is continued.
-
KH00039
The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.
aa....aa: File name
- Description
-
An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.
The output process will now stop.
-
KH00040
The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.
aa....aa: File name
- Description
-
An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.
The output process will now stop.
-
KH00043
Couldn't start RequestLog process 'aa....aa'.
aa....aa: Value specified in the HWSRequestLog directive
- Description
-
An attempt to generate a process for the output of the request log has failed.
The Web server stops the start processing.
- Action
-
Revise the HWSRequestLog directive according to the detailed information shown in this message.
-
KH00044
httpsd: Invalid request log path aa....aa.
aa....aa: File name
- Description
-
The file path specified in the HWSRequestLog directive is invalid.
The Web server stops the start processing.
- Action
-
Revise the HWSRequestLog directive according to the detailed information shown in this message.
-
KH00045
httpsd: could not open request log file aa....aa.
aa....aa: File name
- Description
-
The request log file could not be opened.
The Web server stops the start processing.
- Action
-
Revise the HWSRequestLog directive according to the detailed information shown in this message.
-
KH00046
Graceful stop requested, doing graceful stop
- Description
-
The planned termination of the Web server was requested. The planned termination processing will start.
-
KH00047
caught SIGUSR2, shutting down
- Description
-
The Web server stopped due to reception of the SIGUSR2 signal.
-
KH00048
caught SIGXCPU, shutting down
- Description
-
The Web server stopped due to reception of the SIGXCPU signal.
-
KH00049
caught SIGXFSZ, shutting down
- Description
-
The Web server stopped due to reception of the SIGXFSZ signal.
-
KH00052
Server ran out of threads to serve requests. Consider raising the ThreadsPerChild setting
- Description
-
The server threads for processing requests are insufficient.
The request process continues.
- Action
-
Consider increasing the value of the ThreadsPerChild directive.
-
KH00053
request queue reached HWSMaxQueueSize setting, consider raising the HWSMaxQueueSize setting
- Description
-
The number of requests maintained in the request queue has reached the specified value of the HWSMaxQueueSize directive.
The processing continues. The connection of the requests from the client that are over and above the queue size will be disconnected at the Web server side.
- Action
-
Consider increasing the value of the HWSMaxQueueSize directive.
-
KH00054
Parent: aa....aa
aa....aa: Error
- Description
-
An error occurred during server process generation.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00055
The HWS trace could not open the log file aa....aa specified in the HWSTraceLogFile.
aa....aa: File name
- Description
-
The file described in the aa....aa specified in the HWSTraceLogFile directive cannot be opened.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00056
The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.
aa....aa: File name
- Description
-
An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.
The output process will now stop.
-
KH00057
The HWS trace could not write the log file aa....aa specified in the HWSTraceLogFile.
aa....aa: File name
- Description
-
An attempt to output the contents of the shared memory to the file specified in the HWSTraceLogFile directive failed.
The output process will now stop.
-
KH00058
The HWS trace output the log of the process (pid=aa....aa) into the file bb....bb specified in the HWSTraceLogFile.
aa....aa: Process ID
bb....bb: File name
- Description
-
The contents of the shared memory of the process described in the aa....aa were output in the file described in bb....bb specified in the HWSTraceLogFile directive.
The output in the file is terminated successfully, and the processing is continued.
-
KH00061
QOSCookieServers is out of range
- Description
-
The specified range of the QOSCookieServers directive is invalid.
The Web server stops the start processing.
- Action
-
Revise the QOSCookieServers directive value.
-
KH00062
QOSRejectionServers is out of range
- Description
-
The specified range of the QOSRejectionServers directive is invalid.
The Web server stops the start processing.
- Action
-
Revise the QOSRejectionServers directive value.
-
KH00063
Could not open file: aa....aa
aa....aa: File name
- Description
-
The file specified in the QOSResponse directive cannot be opened.
The Web server stops the start processing.
- Action
-
Revise the QOSResponse directive value according to the detailed information shown in this message.
-
KH00064
Could not open file: aa....aa
aa....aa: File name
- Description
-
The file specified in the QOSResponse directive cannot be opened.
The Web server stops the start processing.
- Action
-
Revise the QOSResponse directive value according to the detailed information shown in this message.
-
KH00065
Could not open file: aa....aa
aa....aa: File name
- Description
-
The file specified in the QOSResponse directive cannot be opened.
The Web server stops the start processing.
- Action
-
Revise the QOSResponse directive value according to the detailed information shown in this message.
-
KH00066
This file is too large: aa....aa
aa....aa: File name
- Description
-
The file specified in the QOSResponse directive cannot be read because it is too big.
The Web server stops the start processing.
- Action
-
Specify a file smaller than 4,294,967,295 bytes.
-
KH00067
Could not read file: aa....aa
aa....aa: File name
- Description
-
The file specified in the QOSResponse directive cannot be read.
The Web server stops the start processing.
- Action
-
Revise the QOSResponse directive value according to the detailed information shown in this message.
-
KH00069
Request rejected (service temporarily unavailable)
- Description
-
The request processing was denied.
The request process will now stop.
-
KH00324
The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.
aa....aa: File name
- Description
-
The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00325
The HWS trace could not obtain the shared memory identifier from the file aa....aa specified in the HWSTraceIdFile.
aa....aa: File name
- Description
-
The shared memory identifier cannot be obtained from the file described in the aa....aa specified in the HWSTraceIdFile directive.
The process continues.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00326
The format of the shared memory identifier specified in the HWSTraceIdFile is invalid.
- Description
-
The format of the shared memory identifier of the file specified in the HWSTraceIdFile directive is invalid.
The process continues.
- Action
-
Revise the shared memory identifier.
-
KH00328
HWS trace shmctl() IPC_RMID could not remove the shared memory segment(id=aa....aa).
aa....aa: Shared memory identifier
- Description
-
The shared memory cannot be deleted.
The process continues.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00329
The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.
aa....aa: File name
- Description
-
The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00330
The HWS trace could not create the segment(size=aa....aa).
aa....aa: Size
- Description
-
Shared memory cannot be secured.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00331
The HWS trace could not assign the segment(id=aa....aa).
aa....aa: Shared memory identifier
- Description
-
The shared memory cannot be assigned.
he process will now stop.
- Action
-
Revise the specification according to the detailed information about shmat() shown in this message.
-
KH00332
HWS trace shmctl() IPC_STAT could not educe the current value(id=aa....aa).
aa....aa: Shared memory identifier
- Description
-
The shared memory status for the aa....aa cannot be extracted.
The process will now stop.
- Action
-
Revise the specification according to the detailed information about shmctl() shown in this message.
-
KH00333
HWS trace shmctl() IPC_SET could not set the value(id=aa....aa), you probably need to modify User or Group directives.
aa....aa: Shared memory identifier
- Description
-
The shared memory status for aa....aa cannot be set up.
The process will now stop.
- Action
-
This error occurs when the user specified in the User directive or Group directive is not registered in the system. Revise the specified value of the User directive or Group directive.
-
KH00334
The HWS trace could not create the segment(size=aa....aa).
aa....aa: Size (bytes)
- Description
-
Shared memory cannot be secured.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00335
The HWS trace could not map the segment(id=aa....aa) for the parent.
aa....aa: Shared memory identifier
- Description
-
The shared memory cannot be assigned to a blank.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00337
The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.
aa....aa: File name
- Description
-
The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00338
The HWS trace created shared memory segment #aa....aa.
aa....aa: Shared memory identifier
- Description
-
Shared memory for the internal trace was secured.
The process continues.
-
KH00340
The HWS trace could not open the ID file aa....aa specified in the HWSTraceIdFile.
aa....aa: File name
- Description
-
The file specified in the aa....aa described in the HWSTraceIdFile directive cannot be opened.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00341
The HWS trace could not open the segment(id=aa....aa).
aa....aa: Shared memory identifier
- Description
-
An attempt to open the shared memory has failed.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00342
The HWS trace could not map the segment(id=aa....aa) for the child.
aa....aa: Shared memory identifier
- Description
-
The shared memory cannot be assigned to a blank.
The process will now stop.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00349
[client aa....aa] bb....bb:forcing termination of request "cc....cc"
aa....aa: Client address
bb....bb: child process process-ID, server thread thread-ID, or child process process-ID: server thread thread-ID
cc....cc: Request line
- Description
-
The request processing described in cc....cc was interrupted because the time from the receipt of the planned termination request until the forced termination has elapsed.
The Web server interrupt the request processing and continues the termination processing.
-
KH00350
error reading response header from remote server aa....aa
aa....aa: Host name
- Description
-
An attempt to read the response header from the remote Web server failed.
The status code 502 Bad Gateway will be returned to the client, and the request processing will be interrupted.
- Action
-
Check for a message indicating that an attempt to read data from the remote Web server failed.
-
KH00351
apr_socket_opt_set(FIONBIO): Failed to set
- Description
-
An error occurred when the FIONBIO option was set.
The Web server continues the processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00352
apr_socket_opt_set(FIONBIO): Failed to set
- Description
-
An error occurred when the FIONBIO option was set.
The Web server continues the processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00353
Failed to set the PRFSPOOL environment variable
- Description
-
An attempt to set up the PRFSPOOL environment variable failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00354
Cannot load PRF library into server: aa....aa
aa....aa: Detailed information
- Description
-
An attempt to load the PRF library failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00355
Cannot load PRF library into server: aa....aa
aa....aa: Detailed information
- Description
-
An attempt to load the PRF library failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00356
Cannot load PRF library into server: aa....aa
aa....aa: Detailed information
- Description
-
An attempt to load the PRF library failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00357
Cannot load PRF library into server: aa....aa
aa....aa: Detailed information
- Description
-
An attempt to load the PRF library failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00358
Cannot load PRF library into server: aa....aa
aa....aa: Detailed information
- Description
-
An attempt to load the PRF library failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00359
Cannot load PRF library into server: aa....aa
aa....aa: Detailed information
- Description
-
An attempt to load the PRF library failed.
The Web server continues the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00360
PRF: open_service failed(aa....aa)
aa....aa: Return code
- Description
-
The PRF daemon cannot be used.
The Web server continues the start processing.
- Action
-
Make sure that the PRF daemon is running.
-
KH00361
The server did not send a status-code aa....aa response because the server already sent an error response to the client.
aa....aa: Status code
- Description
-
A status code response is not sent because an error response is already sent to the client.
-
KH00362
The server started by non-root user. User and Group directives is not used.
- Description
-
The User directive and Group directive are not used because the server is started by a general user.
-
KH00363
Socket Input: timed out (aa....aa:bb....bb --> cc....cc:dd....dd)
aa....aa: Connection destination IP address
bb....bb: Connection destination port number
cc....cc: IP address of the Web server
dd....dd: Port number of the Web server
- Description
-
A timeout occurred in the receipt processing executed with the client or back-end server. Any one of the following standby time periods has been exceeded:
-
Standby time when data is no longer received during the receipt of a request (receipt of HTTP protocol after establishing a connection) from the client
-
Standby time from sending a request to the back-end server until the receipt of a response, when you are using reverse proxy
-
Standby time when data is no longer received during the receipt of a response from the back-end server, when you are using reverse proxy
-
- Action
-
This message was output because the time specified in the Timeout directive was exceeded. Revise the value specified in the directive.
-
KH00364
Socket Output: timed out (aa....aa:bb....bb <-- cc....cc:dd....dd)
aa....aa: Connection destination IP address
bb....bb: Connection destination port number
cc....cc: IP address of the Web server
dd....dd: Port number of the Web server
- Description
-
A timeout occurred in the send processing executed with the client or back-end server. Any one of the following standby time periods has been exceeded:
-
Standby time when data can no longer be sent while a response is being sent to the client
-
Standby time when data can no longer be sent while a request is being sent to the back-end server, when you are using a reverse proxy
-
- Action
-
This message was output because the time specified in the Timeout directive was exceeded. Revise the value specified in the directive.
-
KH00375
Parent aa....aa: Using config file "bb....bb"
aa....aa: Control process ID
bb....bb: Config file name
- Description
-
The process ID of the control process, and the configuration file name used in the startup processing is displayed.
The Web server continues the startup processing.
-
KH00376
Graceful stop requested, doing graceful stop
- Description
-
The planned termination of the Web server was requested. The planned termination processing will start.
-
KH00377
caught SIGUSR2, shutting down
- Description
-
The Web server stopped due to reception of the SIGUSR2 signal.
-
KH00378
caught SIGXCPU, shutting down
- Description
-
The Web server stopped due to reception of the SIGXCPU signal.
-
KH00379
caught SIGXFSZ, shutting down
- Description
-
The Web server stopped due to reception of the SIGXFSZ signal.
-
KH00380
The server started by non-root user. User and Group directives is not used.
- Description
-
The User directive and Group directive are not used because the server is started by a general user.
-
KH00382
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 specified in the aa....aa has not terminated. The Web server continues the termination or restart processing.
-
KH00383
Couldn't start websocket log process 'aa....aa'.
aa....aa: Value specified in the HWSWebSocketLog directive
- Description
-
An attempt to generate a process used to output WebSocket log data failed.
The Web server stops the start processing.
- Action
-
Revise the HWSWebSocketLog directive according to the detailed information shown in this message.
-
KH00384
httpsd: Invalid websocket log path aa....aa.
aa....aa: File name
- Description
-
The file path specified in the HWSWebSocketLog directive is invalid.
The Web server stops the start processing.
- Action
-
Revise the HWSWebSocketLog directive according to the detailed information shown in this message.
-
KH00385
httpsd: could not open websocket log file aa....aa.
aa....aa: File name
- Description
-
The WebSocket log file could not be opened.
The Web server stops the start processing.
- Action
-
Revise the HWSWebSocketLog directive according to the detailed information shown in this message.
-
KH00415
An attempt to acquire the path of the audit log library has failed.
- Description
-
An attempt to acquire the path of the library for the audit log output has failed.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00416
An attempt to load the audit log library has failed.
- Description
-
An attempt to load the library for the audit log output has failed.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00417
An attempt to acquire the address of the audit log function has failed.
- Description
-
An attempt to acquire the address of the function of library for the audit log output has failed.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00418
An attempt to acquire the path of the audit log library has failed.
- Description
-
An attempt to acquire the path of the library for the audit log output has failed.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00419
An attempt to acquire the address of the audit log function has failed.
- Description
-
An attempt to acquire the address of the function of library for the audit log output has failed.
The Web server stops the start processing.
- Action
-
Revise the specification according to the detailed information shown in this message.
-
KH00420
server reached MaxClients setting, consider raising the MaxClients setting
- Description
-
The number of server processes has reached the value set up in the MaxClients directive. Consider increasing the value specified in the MaxClients directive. If the value specified in the MaxClients directive is exceeded, the server process will not be generated.
- Action
-
Revise the value specified in the MaxClients directive. To generate as many idle server processes as specified in the MinSpareServers directive, the value specified in the MaxClients directive must be increased.
-
KH00421
MaxClients can't be changed by restart. Original was used
- Description
-
The MaxClients directive cannot be changed during restart with graceful or restart.
The MaxClients directive value at the time of startup of the Web server will be set up, and the restart processing will continue.
- Action
-
Do not change the MaxClients directive value during restart.
-
KH00422
WARNING: MaxClients of aa....aa exceeds compile time limit of
bb....bb servers, decreasing MaxClients to bb....bb.
aa....aa: MaxClients directive value
bb....bb: Maximum limit
- Description
-
The MaxClients directive value exceeds the maximum limit. The Web server sets the maximum limit value for the MaxClients directive, and then continues the startup processing.
- Action
-
Revise the MaxClients directive value.
-
KH00423
MaxClients of aa....aa exceeds compile time limit of 2048, decreasing to match
aa....aa: MaxClients directive value
- Description
-
The MaxClients directive value exceeds the maximum limit. The Web server sets the maximum limit value for the MaxClients directive, and then continues processing.
- Action
-
Revise the MaxClients directive value.
-
KH00424
WARNING: MaxClients of aa....aa not allowed, increasing to 1.
aa....aa: MaxClients directive value
- Description
-
An invalid value is specified in MaxClients directive.
1 will be set up for the MaxClients directive value of the Web server, and the startup processing will continue.
- Action
-
Revise the MaxClients directive value.
-
KH00425
MaxClients of aa....aa not allowed, increasing to 1
aa....aa: MaxClients directive value
- Description
-
An invalid value is specified in MaxClients directive.
1 will be set up for the MaxClients directive value of the Web server, and the startup processing will continue.
- Action
-
Revise the MaxClients directive value.
-
KH00426
server reached MaxClients setting, consider raising the MaxClients setting
- Description
-
The number of server threads that are processing requests reaches the MaxClients directive value. Consider increasing the MaxClients directive value. No more server processes are generated if the number of server threads exceeds the value specified in the MaxClients directive.
- Action
-
Revise the value specified in the MaxClients directive.
-
KH00427
server is within MinSpareThreads of MaxClients, consider raising the MaxClients setting
- Description
-
The number of idle server threads is now less than the MinSpareThreads directive value.
- Action
-
Revise the value specified in the MaxClients or MinSpareThreads directive.
-
KH00429
WARNING: MaxClients of aa....aa is less than ThreadsPerChild of
bb....bb, increasing to bb....bb. MaxClients must be at least as large
as the number of threads in a single server.
aa....aa: Value specified in the MaxClients directive
bb....bb: Value specified in the ThreadsPerChild directive
- Description
-
The MaxClients directive value is smaller than the ThreadsPerChild directive value. The Web server sets the ThreadsPerChild directive value for the MaxClients directive value, and then continues the startup processing. The MaxClients directive value must be at least equal to the number of server threads belonging to one server process.
- Action
-
Revise the MaxClients directive value.
-
KH00430
MaxClients of aa....aa is less than ThreadsPerChild of bb....bb, increasing to match
aa....aa: Value specified in the MaxClients directive
bb....bb: Value specified in the ThreadsPerChild directive
- Description
-
The MaxClients directive value is smaller than the ThreadsPerChild directive value. The Web server sets the ThreadsPerChild directive value for the MaxClients directive value, and then continues processing.
- Action
-
Revise the MaxClients directive value.
-
KH00431
WARNING: MaxClients of aa....aa is not an integer multiple of
ThreadsPerChild of bb....bb, decreasing to nearest multiple cc....cc,
for a maximum of dd....dd servers.
aa....aa: Value specified in the MaxClients directive
bb....bb: Value specified in the ThreadsPerChild directive
cc....cc: Maximum number of concurrent connections
dd....dd: Maximum number of server processes
- Description
-
The MaxClients directive value is not an integer multiple of the ThreadsPerChild directive value. The Web server sets the MaxClients directive value that is reduced to an integer multiple of the ThreadsPerChild directive value, and then continues the startup processing.
- Action
-
Revise the MaxClients directive value.
-
KH00432
MaxClients of aa....aa is not an integer multiple of ThreadsPerChild of bb....bb, decreasing to nearest multiple cc....cc
aa....aa: Value specified in the MaxClients directive
bb....bb: Value specified in the ThreadsPerChild directive
cc....cc: Maximum number of concurrent connections
- Description
-
The MaxClients directive value is not an integer multiple of the ThreadsPerChild directive value. The Web server sets the MaxClients directive value that is reduced to an integer multiple of the ThreadsPerChild directive value, and then continues processing.
- Action
-
Revise the MaxClients directive value.
-
KH00433
WARNING: MaxClients of aa....aa would require bb....bb servers and
would exceed ServerLimit of cc....cc, decreasing to dd....dd.
To increase, please see the ServerLimit directive.
aa....aa: Value specified in the MaxClients directive
bb....bb: Maximum number of server processes
cc....cc: ServerLimit directive value
dd....dd: Maximum number of concurrent connections
- Description
-
The maximum number of server processes calculated from the MaxClients and ThreadsPerChild directives exceeds the ServerLimit directive value. The Web server sets the ServerLimit directive value multiplied by the ThreadsPerChild directive value for the maximum number of concurrent connections, and then continues the startup processing.
- Action
-
Revise the ServerLimit directive value.
-
KH00434
MaxClients of aa....aa would require bb....bb servers and exceed ServerLimit of cc....cc, decreasing to dd....dd
aa....aa: Value specified in the MaxClients directive
bb....bb: Maximum number of server processes
cc....cc: ServerLimit directive value
dd....dd: Maximum number of concurrent connections
- Description
-
The maximum number of server processes calculated from the MaxClients and ThreadsPerChild directives exceeds the ServerLimit directive value. The Web server sets the ServerLimit directive value multiplied by the ThreadsPerChild directive value for the maximum number of concurrent connections, and then continues processing.
- Action
-
Revise the ServerLimit directive value.