This subsection describes messages output by the basic functionality of Cosminexus HTTP Server with error level info.

---

[client client-address] detailed-information: core_output_filter: writing data to the network

An error occurred during the process of sending data to the client.

Error level: info

(S) The process of sending data from the Web server to the client will be interrupted.

(O) Revise according to detailed-information.

---

detailed-information: apr_socket_addr_get(APR_LOCAL)

The socket information of the Web server could not be acquired.

Error level: info

(S) The Web server stops the request processing.

(O) Revise according to detailed-information that the getsockname() function returns.

---

detailed-information: apr_socket_addr_get(APR_REMOTE)

The socket information of the client could not be acquired.

Error level: info

(S) The Web server stops the request processing.

(O) Revise according to detailed-information that the getpeername() function returns.

---

No ExecCGI or Open verb found for files of type 'extension-type'.

The registry keys ExecCGI and Open were searched, but no interpreter correlated to the script extension was found.

Error level: info

(S) The script execution processing will continue by using the interpreter specified in the #! line number.

(O) Revise the script extension and the correlated programs.

---

detailed-information: select failed

An error occurred in select() of the server process.

Error level: info

(S) The process of accepting the requests continues.

(O) Revise according to detailed-information that the select() function returns.

---

Parent: Duplicating socket fd-number and sending it to child process process-ID

The control process duplicates the socket, and sends to the server process.

Error level: info

(S) The Web server continues the startup processing.

---

Using ConfigArgs of the installed service "service-name".

The registry entry ConfigArgs of the service specified in the service-name is used in the startup option.

Error level: info

(S) The Web server continues the startup processing.

---

removed PID file file-name (pid=control-process-ID)

The file that stores the control process ID was deleted.

Error level: info

(S) The Web server continues the termination processing.

---

No ConfigArgs registered for service-name, perhaps this service is not installed?

The registry entry ConfigArgs of the service described in the service-name does not exist.

Error level: info

(S) The Web server continues the startup processing.

(O) Confirm that the service has been installed.

---

[client client-address] client sent an unrecognized expectation value of Expect: header-value

The request processing cannot be continued because the client sent the request by specifying a value that is not supported by the Expect header value.

Error level: info

(S) The status code 417 Expectation Failed will be returned to the client, and the request processing will be interrupted.

(O) Only 100-continue can be specified as the Expect header value. Revise the Expect header.

---

The HWS trace created shared memory segment #shared-memory-identifier.

Shared memory for the internal trace was secured.

Error level: info

(S) The process continues.

---

The HWS trace output the log of the process (pid = process-ID) into the file file-name specified in the HWSTraceLogFile.

The contents of the shared memory of the process described in the process-ID were output in the file described in file-name specified in the HWSTraceLogFile directive.

Error level: info

(S) The output in the file is terminated successfully, and the processing is continued.

---

Child process-ID: Accept thread exiting.

The request reception thread is terminated.

Error level: info

(S) The termination processing of the server process will continue.

---

server seems busy, (you may need to increase StartServers, or Min/MaxSpareServers), spawning number-of-server-processes-to-be-generated children, there are number-of-existing-idle-server-processes idle, and number-of-existing-server-processes total children

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. The number of server processes proposed to be generated is the number specified in the number-of-server-processes-to-be-generated. The number of server processes that are currently in the idle state is the number specified in the number-of-existing-idle-server-processes. The total number of existing server processes is the number specified in the number-of-existing-server-processes.

Error level: info

(S) The startup of the Web server will continue. Server processes will be generated in numbers of 1, 2, 4, 8, 16, and 32 until the number of idle servers specified in the MinSpareServers directive is reached. If the number of processes to be generated reaches 8 or more, this message will be output.

---

[client client-address] no AuthGroupFile, so 'file-group' requirement cannot succeed for file 'file-name'

The file-group request will not be successful because AuthGroupFile is not specified.

Error level: info

(S) The request process continues.

---

Details: Socket Input: timed out (Connection-source-IP-address: Port-number --> Connection-destination-IP-address: Port-number)(Server-process-ID or server-thread-ID)

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

Error level: info

(S) The processing continues.

(O) This message was output because the time period specified in the Timeout directive has expired. Revise the value specified in the Timeout directive.

---

Details: Socket Output: timed out (Connection-destination-IP-address: Port-number <-- Connection-source-IP-address: Port-number)(Server-process-ID or server-thread-ID)

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

Error level: info

(S) The processing continues.

(O) This message was output because the time period specified in the Timeout directive has expired. Revise the value specified in the Timeout directive.

---

[client client-address] The server did not send a status-code status-code response because the server already sent an error response to the client.

A status-code response is not sent because an error response is already sent to the client.

Error level: info

(S) The processing continues.