Chapter 131 WEBSERV Messages

Cause  The configuration file contains more than one Browser directive that specifies the same agent string.

Effect  The iTP Secure WebServer environment does not start.

Recovery  In the configuration file (httpd.config), verify that there is not more than one Browser directive for the same agent string. Restart the iTP Secure WebServer.

For information about the Browser directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The configuration file contains more than one Message directive that specifies the same message ID.

Effect  The iTP Secure WebServer environment does not start.

Recovery  In the configuration file (httpd.config), verify that there is not more than one Message directive for the same msg-id. Restart the iTP Secure WebServer.

For information about the Message directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The error text specified with the Message directive is more than 4096 characters long.

Effect  The iTP Secure WebServer environment does not start.

Recovery  In the configuration file (httpd.config), verify that none of the Message directives have error texts that are more than 4096 characters long. Restart the iTP Secure WebServer.

For information about the Message directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The configuration file contains more than one Filemap directive with the same prefix.

Effect  The iTP Secure WebServer environment does not start.

Recovery  In the configuration file (httpd.config), verify that there is not more than one Filemap directive for the same prefix. Restart the iTP Secure WebServer.

For information about the Filemap directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The configuration file contains more than one EncodingType directive with the same encoding-type.

Effect  The iTP Secure WebServer environment does not start.

Recovery  In the configuration file (httpd.config), verify that there is not more than one EncodingType directive for the same encoding-type. Restart the iTP Secure WebServer.

For information about the EncodingType directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The server address could not be resolved to a valid IP address.

Effect  The iTP Secure WebServer environment does not start.

Recovery  For the Accept and AcceptSecureTransport directive, ensure that the -address switch in the configuration file has a valid host name/address.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The server hostname could not be resolved to a valid IP address.

Effect  The iTP Secure WebServer environment does not start.

Recovery  For the Accept and AcceptSecureTransport directive, ensure that the -address/-name switch in the configuration file has a valid host name/address.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The configuration file (httpd.config) contains one or more of the following obsolete directives:

Effect  The iTP Secure WebServer environment does not start.

Recovery  Check the configuration file (httpd.config) for any of these directives. If Port, ServerAddress, and ServerName are used, use the Accept directive instead. If SSLPort, ServerAddress, and SSLName are used, use the AcceptSecureTransport instead. Correct the configuration file (httpd.config) and try restarting the iTP Secure WebServer.

For information about the Accept and AcceptSecureTransport directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The priority value specified in a Region directive is not in the range 0-20.

Effect  Requests to the concerned Region directive fail.

Recovery  Check the configuration file (httpd.config). Verify that all priority values inside a Region directive are in the range 0-20. Restart the iTP Secure WebServer.

For information about the Region directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The host address specified in the Region directive could not be resolved to a valid IP address.

Effect  Requests directed to the concerned region are not served.

Recovery  In the configuration file (httpd.config), verify if a valid host address has been provided with the -host option of the Region command.

For information about the Region directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The host address specified in the Region directive could be resolved to more than one IP address.

Effect  Requests directed to the concerned Region are not served.

Recovery  Change the DNS configuration or HOSTS file (whichever is applicable) to make sure that each host address used with Region directive maps to a single IP address.

For information about the Region directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The directory/file mapped to a web address does not exist.

Effect  Requests for the mapped resource fails.

Recovery  In the configuration file (httpd.config), verify that all the absolute addresses specified with the Configuration directive exists. Restart the iTP Secure WebServer.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The port number specified is not within the allowed limit.

Effect  The iTP Secure WebServer environment does not start.

Recovery  In the configuration file (httpd.config), verify that all port numbers are within the range (1 through 65535). Restart the iTP Secure WebServer.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The CGI script sends an incomplete or malformed header or a Pathmon error can occur while using a pathway CGI applicationt.

Effect  The request is not served.

Recovery  Check if the Pathmon error is reported in the error log file. Change the configuration and resend the request.

Cause  The image map file could not be read.

Effect  Request is not served.

Recovery  Make sure the image map file is present, and has proper access permissions.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  Request to the image map contains no or one coordinate values.

Effect  Request is not served.

Recovery  Make sure the client request to the image map contains both the coordinates of the desired point on the image.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The image map file does not contain a DEFAULT directive.

Effect  Request is not served.

Recovery  Make sure the image map contains the DEFAULT directive at the end of the map file.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The relative URL in the image map file is not correct.

Effect  Request is not served.

Recovery  Verify the URL in the relative format in the image map file.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The image map file could not be open.

Effect  Request is not served.

Recovery  Make sure the image map file is present, and is correctly invoked by the html script.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The coordinate is not present in the correct format.

Effect  Request is not served.

Recovery  Make sure the image map coordinate is specified in the correct format.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The URL specified in the image map file is not is the correct format.

Effect  Request is not served.

Recovery  Make sure a correct string is specified in the URL.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The image map file does not contain the radius value in the CIRCLE directive.

Effect  Request is not served.

Recovery  Make sure the CIRCLE directive includes the radius value in the image map file.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The image map file does not contain a valid image map directive.

Effect  Request is not served.

Recovery  Make sure the correct image map directives are used in the image map file.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The image map file could not be parsed correctly.

Effect  Request is not served.

Recovery  Make sure the image map file contains no errors.

For information about using the image map, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer does not receive the request from the Web client within the time specified by the InputTimeout directive.

Effect  The iTP Secure WebServer closes the connection.

Recovery  Check the value assigned to the InputTimeout directive in the configuration file. If no value is assigned, the default value is 120 seconds. Change the value if it is not sufficient.

Cause  The Web client does not receive the response from the iTP WebServer within the time specified by the OuputTimeout directive.

Effect  The iTP Secure WebServer closes the connection.

Recovery  Check the value assigned to the OutputTimeout directive in the configuration file. If no value is assigned, the default value is 1200 seconds. Change the value if it is not sufficient.

Cause  An error occurred when the httpd process tried to obtain a host name.

Effect  The iTP Secure WebServer environment does not start.

Recovery  One possibility is that the host name or IP address is misspelled in the configuration file (httpd.config). If this is the cause, correct the misspelling and restart the iTP Secure WebServer.

If the host name and IP address are spelled correctly, ensure that the host name and IP address are registered in the DNS database file. If the host name is not registered, change the configuration file (httpd.config) to reflect the server IP address. Make sure both hostname and hostid are initialized in the TCP/IP process, which is the default setup for the DEFINE =TCPIP^PROCESS^NAME parameter. Delete the DEFINE=TCPIP^HOST^FILE parameter when DNS is used to resolve IP addresses. After correcting the problems, restart the iTP Secure WebServer.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The host name resolved to more than one IP address.

Effect  The iTP Secure WebServer environment does not start.

Recovery  This situation is very unlikely to occur. If it occurs, check DNS to ensure that the host name in question corresponds to the correct address.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The httpd process attempted to bind to a port but could not because the specified port was already in use.

Effect  The iTP Secure WebServer environment does not start.

Recovery  You can use SCF to query TCP/IP about the port numbers in use. If the port number is still in use, you will need to change the port number specified in the Accept or AcceptSecureTransport directive in the configuration file (httpd.config) so that it specifies a port number not in use. For information about the Accept and AcceptSecureTransport directives, see the iTP Secure WebServer System Administrator’s Guide.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  An error occurred when the httpd process attempted to obtain a socket. See the socket error reported in the message for more details about the cause.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Consult the TCP/IP and IPX/SPX Programming Manual for socket error information and take the recovery action recommended for the error.

Cause  The iTP Secure WebServer could not bind to the specified server port. See the error reported in the message for more details about the cause.

Effect  The specified server port is not active.

Recovery  Check the directive in the configuration file (httpd.config). Verify that the server name and port are spelled correctly, and that the specified port is not already active. Restart the iTP Secure WebServer.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer environment stopped because the WebServer cannot recognize a user name specified in the User directive section of the configuration file (httpd.config).

Effect  The iTP Secure WebServer environment stops.

Recovery  Check the User directive section of the configuration file (httpd.config) to verify that the user name is spelled correctly. Verify that the user name exists by using the SAFECOM INFO GROUP * command. Restart the iTP Secure WebServer.

For information about the User directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer environment stopped because the user name specified in the User directive section of the configuration file (httpd.config) is not a member of a root or super group.

Effect  The iTP Secure WebServer environment stops.

Recovery  Verify that the user name specified in the User directive section of the configuration file (httpd.config) is a member of the super or root group by using the SAFECOM INFO GROUP * command. Restart the iTP Secure WebServer.

For information about the User directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  When processing the configuration file (httpd.config), the iTP Secure WebServer encountered a user name that it does not recognize.

Effect  The iTP Secure WebServer environment stops.

Recovery  Check the User directive section of the configuration file (httpd.config) to verify that the user name is spelled correctly. Verify that the user name exists by using the SAFECOM INFO USER * command. Restart the iTP Secure WebServer.

For information about the User directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer environment stopped because the iTP Secure WebServer was not started by the root or super group.

Effect  The iTP Secure WebServer environment stops.

Recovery  Make sure the iTP Secure WebServer is started by the root or super group.

For information about the User directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The specified directory cannot be written to by the server process. See the error message reported for more details about the cause.

Effect  Warning message only.

Recovery  Check the spelling of the directory name in the configuration file (httpd.config), the existence of the directory, and the access rights of the directory. The server must have write access to the directory.

For information about the ServerRoot directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The specified directory cannot be accessed by the server process. See the error message reported for more details about the cause.

Effect  The iTP Secure WebServer environment stops.

Recovery  Check the directory spelling in the configuration file (httpd.config), the existence of the directory, and the access rights of the directory. The server must have write access to the directory. Restart the iTP Secure WebServer.

For information about the Chroot directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer ran out of memory while setting up directory entries.

Effect  The httpd process that encountered the memory shortage exits.

Recovery  Ensure that the CPU has plenty of memory. PATHMON will restart the httpd process if necessary.

Cause  The iTP Secure WebServer ran out of memory while executing the malloc function.

Effect  The httpd process that encountered the memory shortage exits.

Recovery  Ensure that the CPU has plenty of memory. PATHMON will restart the httpd process if necessary.

Cause  The iTP Secure WebServer ran out of memory while executing the realloc function.

Effect  The httpd process that encountered the memory shortage exits.

Recovery  Ensure that the CPU has plenty of memory. PATHMON will restart the httpd process if necessary.

Cause  The iTP Secure WebServer encountered an internal error.

Effect  The httpd process that encountered the error exits.

Recovery  The recovery action depends on the type of assertion failure. If this error occurs repeatedly, contact your service provider and provide the following information:

Cause  The specified PID file cannot be opened by the server process.

Effect  The iTP Secure WebServer environment doesn’t start.

Recovery  Recovery varies slightly based on whether the error occurred while executing the PidFile directive or the -pidfile option:

Restart the iTP Secure WebServer.

For information about the PidFile directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer could not change to the specified root directory. See the error message reported for more details about the cause.

Effect  The iTP Secure WebServer environment doesn’t start.

Recovery  Verify that the specified directory exists and the server has access rights to it. Consult the OSS System Calls Reference Manual for chdir error information.

Restart the iTP Secure WebServer.

Cause  The iTP Secure WebServer encountered a problem and cannot accept new connections. See the error message reported for more details about the cause.

Effect  The connection attempt fails.

Recovery  Based on the text of the error message, take the recommended measures to recover.

Cause  The allocated file descriptor is already in use or exceeds the maximum limit of 256.

Effect  The iTP Secure WebServer closes the open file descriptors and the current request.

Recovery  Free any outstanding I/O operations and try again.

Cause  An empty cipher list is provided as a parameter to the ciphers option of the AcceptSecureTransport directive.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify valid cipher names in the ciphers list supplied with the ciphers option.

For more information about the cipher list, see the iTP Secure WebServer System Administrator’s Guide.

Cause  An error occurred during secure connection.

Effect  Connection between the server and the client is aborted.

Recovery  This message is always followed by another error message. Correct the error and try again.

Cause  Either the certificate key database is not specified with the KeyDatabase directive or password is not specified with the ServerPassword directive in the configuration file (httpd.stl.config).

Effect  The iTP Secure WebServer environment does not start.

Recovery  Ensure that the key database and password is specified with the KeyDatabase and the ServerPassword directives respectively in the configuration file (httpd.stl.config).

iTP Secure WebServer must be configured with a key database and a password to decrypt the private key of the server certificate.

Cause  The DN specified in AcceptSecureTransport directive is not found in the key database.

Effect  The iTP WebServer does not start.

Recovery  Make sure the DN specified by the AcceptSecureTransport command matches the DN of the certificate. If you specified some non-English characters in the DN attribute values while generating a certificate request, make sure that you use the same editor to specify the DN attribute values with the AcceptSecureTransport command. Also, make sure that the correct key database is in use. Lastly, make sure that the certificate was properly added to the key database.

Cause  There is no private key associated to the certificate name specified in the AcceptSecureTransport command.

Effect  The iTP WebServer does not start.

Recovery  Do keyadmin -list and verify that the certificate has an associated private key entry. If not make sure that the certificate was indeed added to the keydatabase used for certificate request and key generation.

Cause  There was either no ServerPassword specified or the ServerPassword specified was invalid.

Effect  The iTP WebServer does not start.

Recovery  Specify the correct ServerPassword in the config file.

Cause  The certificate installed in the key database is either not valid or expired or the signature is invalid.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Make sure that the certificate is valid in all respects.

For information on installing certificates, see the iTP Secure WebServer System Administrator’s Guide.

Cause  Configuration errors related to secure transport occurred. Either the DN, the private key or the certificate was not present in the certificate/key database file or the certificate was invalid or there were errors in decrypting the private key.

Effect  The iTP Secure WebServer does not start.

Recovery  Run keyadmin -list and check for the following:

Cause  No key database was specified in the iTP Secure WebServer configuration.

Effect  The iTP Secure WebServer environment does not start if an AcceptSecureTransport directive has been configured.

Recovery  Specify a key database using the KeyDatabase configuration directive. Key database can be created using the keyadmin utility.

For more information on creating key databases and the KeyDatabase configuration directive, refer to the chapter that describes configuring for secure transport in the iTP Secure WebServer System Administrator's Guide.

Cause  No server password (password for the key database to be used by the server) set in the iTP Secure WebServer configuration.

Effect  The iTP Secure WebServer environment does not start if an AcceptSecureTransport directive has been configured.

Recovery  Specify the server password using the ServerPassword configuration directive.

For more information on ServerPassword configuration directive, refer to the chapter ‘Configuring for secure transport’ from the iTP Secure WebServer System Administrator’s Guide.

Cause  This is an informational message logged in case one of the events 463 or 464 occurs.

Effect  The iTP Secure WebServer environment does not start if an AcceptSecureTransport directive has been configured.

Recovery  Refer to events 463 and 464.

Cause  This error can be caused due to one of the following:

Effect  The iTP Secure WebServer environment does not start if an AcceptSecureTransport directive has been configured.

Recovery  The exact cause for the failure can be found using the err-msg text. Take the necessary corrective action to correct the problem.

Cause  The iTP Secure WebServer encountered an internal error.

Effect  The httpd process that encountered the error exits.

Recovery  The recovery action depends on the type of failure. If one of these errors occurs repeatedly, contact your service provider and provide the following information:

Cause  The iTP Secure WebServer encountered an internal error while generating export grade RSA key pair used for secure transport.

Effect  The httpd process that encountered the error exits.

Recovery  The recovery action depends on the type of failure. If one of these errors occurs repeatedly, contact your service provider and provide the following information:

Cause  The iTP Secure WebServer encountered an internal error.

Effect  The httpd process that encountered the error exits.

Recovery  The recovery action depends on the type of failure. If one of these errors occurs repeatedly, contact your service provider and provide the following information:

Cause  The iTP Secure WebServer encountered an internal error.

Effect  The httpd process that encountered the error exits.

Recovery  The recovery action depends on the type of failure. If one of these errors occurs repeatedly, contact your service provider and provide the following information:

Cause  The iTP Secure WebServer encountered an internal error.

Effect  The httpd process that encountered the error exits.

Recovery  The recovery action depends on the type of failure. If one of these errors occurs repeatedly, contact your service provider and provide the following information:

Cause  Wrong departmentID has been used inside region with directive SI_RequireSI.

Effect  Webserver will not provide access to the region configured to use anonymous ticketing.

Recovery  Use correct departmentID inside region with SI_RequireSI or specify the departmentID used with SI_RequireSI , with SI_Department directive.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  Value specified with departmentID contain a 'space'

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify departmentID without space.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  Attempt to alter attributes of the departmentID , specified with DepartmentID directive has been made after SI_RequireSI region command.

Effect  Webserver will not provide access to the region configured to use anonymous ticketing.

Recovery  Once declared a departmentID with specified attributes cannot be altered in after SI_RequireSI region command.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  DepartmentID not specified with SI_Department directive , has been used.

Effect  Webserver will not provide access to the region configured to use anonymous ticketing.

Recovery  Specify DepartmentID with the directive SI_Department.

Cause  The group value specified with the EnableAnonymousTicketing parameter is not within the valid range.

Effect  Requests for the region where the EnableAnonymousTicketing parameter is specified are not served.

Recovery  Specify a valid number with the EnableAnonymousTicketing parameter. The valid range is 0 to 255.

Cause  GroupID has been specified more than 255 inside region.

Effect  Webserver will not provide access to the region configured to use anonymous ticketing.

Recovery  Specify groupID less than 255.

Cause  Anonymous ticketing has not been enabled for the groupID specified with departmentID in SI_RequireSI directive hence secret could not be made for the corresponding departmentID.

Effect  Webserver will not provide access to the region configured to use anonymous ticketing.

Recovery  Enable anonymous ticketing for the groupID specified with departmentID in SI_RequireSI directive.

Cause  The SignatureLength parameter of the SI_Department directive has an invalid value.

Effect  If the SI_Department directive is specified in the Region directive, iTP Secure WebServer environment may start but the requests relating to that region will not be served as expected.

If the SI_Department is specified as an independent directive, iTP Secure WebServer environment does not start.

Recovery  Ensure that the value for the SignatureLength parameter of the SI_Department directive is valid. The valid values are 32, 64, or 128.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The value of attribute AnonymousTicketExpiration has been given less than 0.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify value greater than or equal to 0 for attribute AnonymousTicketExpiration.

Cause  The value of attribute PostExpirationExtension has been given less than 0.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify value greater than or equal to 0 for attribute PostExpirationExtension.

Cause  A fatal error occurred when the httpd process tried to request the current working directory.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Ensure that your current working directory exists. If the directory does exist, contact your service provider and provide the following information:

Cause  While attempting to restart the httpd process, a SERVERCLASS_SEND error to the Distributor process occurred. Therefore, the httpd process could not confirm the specified port number to use for its connection. This message appears in addition to message 556.

Effect  The httpd process cannot communicate with the Distributor process using this port, but continues to run.

Recovery  The most likely cause is that the port number is already in use. Use SCF to query TCP/IP about the port numbers in use. If the port number is already in use, you will need to change the configuration file (httpd.config) so that it specifies a unique port number.

Cause  The reply buffer from the Distributor process has a content value that does not match any expected value. This message usually signifies a port error in the Distributor process.

Effect  The httpd process cannot verify the port number used by the Distributor process.

Recovery  Informational message only; no corrective action is needed.

Cause  The iTP Secure WebServer encountered a logic error. The most likely cause is that an invalid startup argument was specified in the httpd command.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Contact your service provider and provide the following information:

Cause  A required httpd startup argument is missing.

Effect  The iTP Secure WebServer environment cannot start, stop, or restart.

Recovery  Run the iTP Secure WebServer with the appropriate startup argument.

Cause  The new PATHMON process could not be created. See the errors reported in the message for more details about the cause.

Effect  The PATHMON environment, and therefore the iTP Secure WebServer environment, cannot start.

Recovery  The recovery action depends on the error that occurred. For example, a PATHMON process with the same name might already exist, or the iTP Secure WebServer configuration file (httpd.config) might prescribe invalid settings for the PATHMON configuration parameters. Consult the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to recover. Correct the error and try again.

Cause  You attempted to use the restarth script to restart the iTP Secure WebServer environment, but the PATHMON environment wasn’t running.

Effect  The httpd process exits.

Recovery  Use the start script, rather than the restarth script, to start a new iTP Secure WebServer environment.

Cause  During the httpd restart phase, the httpd process attempted to start the specified PATHMON process, but the PATHMON process was already running.

Effect  The httpd process exits.

Recovery  Check to see if another process is running with the same PATHMON name. Ensure that the PATHMON name is unique in the configuration file (httpd.config). You might have used the start script instead of the restart script.

Cause  An error occurred during shutdown of the PATHMON process. See the errors reported in the message for more details about the cause.

Effect  The httpd process exits. The PATHMON environment is in an indeterminate state; it might or might not still be running.

Recovery  If PATHMON is still running, use PATHCOM to shut down the PATHMON environment manually. Consult the NonStop TS/MP and Pathway Management Programming Messages Manual and the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to recover.

Cause  The PATHMON process coldstart failed. See the errors reported in the message for more details about the cause.

Effect  The iTP Secure WebServer environment does not start.

Recovery  The recovery action depends on the error that occurred. For example, the iTP WebServer configuration file (httpd.config) might see a nonexistent Guardian subvolume. Consult the NonStop TS/MP and Pathway Management Programming Messages Manual and the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to recover. Correct the error and try again.

Cause  The specified server class could not be added to the iTP Secure WebServer environment. See the errors reported in the message for more details about the cause.

Effect  The server class is not present in the iTP Secure WebServer environment. Whether the rest of the iTP Secure WebServer environment can function normally depends on which server class is affected.

Recovery  Consult the NonStop TS/MP and Pathway Management Programming Messages Manual and the Guardian Procedure Errors and Messages Manual for error information. In most cases, the problem is with the values set for the Pathmon directive’s MaxServerClasses and MaxServerProcesses attributes in the iTP Secure WebServer configuration file (httpd.config). For example, the creation of the server class would exceed the limit set by either the MaxServerClasses or MaxServerProcesses attribute. Increase the value of the attribute whose limit has been reached and try again.

Cause  The httpd process was unable to delete a server class successfully. See the errors reported in the message for more details about the cause. (One possibility is that the process was in debug mode.)

Effect  All of the processes in the httpd server class stop.

Recovery  Stop the iTP Secure WebServer environment and restart the iTP Secure WebServer.

Cause  The SERVERCLASS_SEND_ procedure did not complete during start or restart because of an error that occurred when the Distributor process attempted to bind to a socket. See the error reported in the message for more details about the cause.

Effect  The httpd process cannot communicate with the Distributor process. The httpd process might exit.

Recovery  Consult the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to correct the error. Restart the iTP Secure WebServer.

Cause  The server class startup encountered an error. See the errors reported in the message for more details about the cause.

Effect  The iTP Secure WebServer environment stops.

Recovery  Consult the NonStop TS/MP and Pathway Management Programming Messages Manual and the Guardian Procedure Errors and Messages Manual for error information. In most cases, the problem is with the values set for the Pathmon directive’s MaxServerClasses and MaxServerProcesses attributes in the iTP Secure WebServer configuration file (httpd.config). For example, the creation of the server class would exceed the limit set by either the MaxServerClasses or MaxServerProcesses attribute. Increase the value of the attribute whose limit has been reached and restart the iTP Secure WebServer.

Cause  During a restart, the specified server class could not be stopped because of the error reported in the message. See the errors reported in the message for more details about the cause.

Effect  The iTP Secure WebServer environment stops.

Recovery  Consult the NonStop TS/MP and Pathway Management Programming Messages Manual and the Guardian Procedure Errors and Messages Manual for error information. Take any necessary measures to correct the errors and restart the iTP Secure WebServer.

Cause  An error occurred during an attempt to restart the iTP Secure WebServer with the restarth script option.

Effect  The intended configuration changes have not taken effect.

Recovery  Stop the current iTP Secure WebServer environment and restart the iTP Secure WebServer using the new configuration file (httpd.config).

Cause  The restarth command has been issued successfully.

Effect  The iTP Secure WebServer environment is running with the new configuration.

Recovery  Informational message only; no corrective action is needed.

Cause  An error caused the iTP Secure WebServer environment to shut down. Another error message always precedes this message; to determine which error occurred, see the first error message. The error requires attention from an operator.

Effect  The iTP Secure WebServer environment exits.

Recovery  See the previous error message for a description of the error and take the appropriate recovery measures.

Cause  The httpd process could not freeze the httpd server classes during restarth.

Effect  The httpd process is busy with request processing; the httpd server classes will freeze eventually.

Recovery  Informational message only; no corrective action is needed.

Cause  AWAITIOX of accept_nw2 function call failed with an error.

Effect  The socket with the error is closed. See the error message reported for more details about the cause.

Recovery  Contact your service provider and provide the following information:

Cause  The accept_nw2 function call failed with an error.

Effect  The socket with the error is closed. See the error message reported for more details about the cause.

Recovery  Contact your service provider and provide the following information:

Cause  An error occurred when the iTP Secure WebServer was communicating with a Pathway server. See the error reported in the message for more details about the cause.

Effect  The data structure related to the Pathway server is freed.

Recovery  Contact your service provider and provide the following information:

Cause  The SERVERCLASS_DIALOG_BEGIN_ call encountered an error.

Effect  The iTP Secure WebServer cannot process the request, and a server error is reported to the client.

Recovery  Ensure that the server class named in this message is configured and running. See the Guardian Procedure Errors and Messages Manual for descriptions of the file-system errors. Take any recommended actions to correct the file-system error.

Cause  The FILE_GETRECEIVEINFO function call failed with an error. See the error reported in the message for more details about the cause.

Effect  The httpd process exits.

Recovery  Consult the Guardian Procedure Errors and Messages Manual for error information. Take any recommended measures to correct the file-system error. If required, shut down the iTP Secure WebServer environment and restart the iTP Secure WebServer.

Cause  The httpd process cannot set a timer because the httpd process cannot get a value from the JULIANTIMESTAMP function.

Effect  The httpd process exits.

Recovery  Informational message only; no corrective action is needed.

Cause  The iTP Secure WebServer was unable to obtain the TANDEM_PATHMON_NAME environmental variable.

Effect  The httpd process exits.

Recovery  Stop the current iTP Secure WebServer environment and restart the iTP Secure WebServer.

Cause  The iTP Secure WebServer encountered an error while executing the READUPDATEX function on a file. See the error reported in the message for more details about the cause.

Effect  The httpd process exits.

Recovery  Consult the Guardian Procedure Errors and Messages Manual for error information. Take any recommended measures to correct the file-system error. If required, stop the iTP Secure WebServer environment and restart the iTP Secure WebServer.

Cause  The iTP Secure WebServer could not open $RECEIVE because of an error. See the error reported in the message for more details about the cause.

Effect  The httpd process exits.

Recovery  Consult the Guardian Procedure Errors and Messages Manual for error information. Take any recommended measures to correct the file-system error. If required, stop the iTP Secure WebServer environment and restart the iTP Secure WebServer.

Cause  The system administrator did not configure the TANDEM_RECEIVE_DEPTH environment variable.

Effect  The iTP Secure WebServer defaults to a receive depth of 1.

Recovery  If the iTP Secure WebServer requires a larger receive depth value, the system administrator must stop the iTP Secure WebServer, modify the configuration file (httpd.config) to include the TANDEM_RECEIVE_DEPTH environment variable with the new receive depth value, and restart the iTP Secure WebServer. See the iTP Secure WebServer System Administrator’s Guide for information about configuring the TANDEM_RECEIVE_DEPTH environment variable.

Cause  The system administrator configured the iTP Secure WebServer TANDEM_RECEIVE_DEPTH environment variable with a value that is less than 1.

Effect  The iTP Secure WebServer defaults to a receive depth of 1.

Recovery  If the iTP Secure WebServer requires a larger receive depth value, the system administrator must stop the iTP Secure WebServer, modify the configuration file (httpd.config) to include the TANDEM_RECEIVE_DEPTH environment variable with the new receive depth value, and restart the iTP Secure WebServer. See the iTP Secure WebServer System Administrator’s Guide for information about configuring the TANDEM_RECEIVE_DEPTH environment variable.

Cause  The system administrator configured the iTP Secure WebServer TANDEM_RECEIVE_DEPTH environment variable with a value that is greater than 255.

Effect  The iTP Secure WebServer defaults to a receive depth of 255.

Recovery  If the iTP Secure WebServer requires a different receive depth value, the system administrator must stop the iTP Secure WebServer, modify the configuration file (httpd.config) to include the TANDEM_RECEIVE_DEPTH environment variable with the new receive depth value, and restart the iTP Secure WebServer. See the iTP Secure WebServer System Administrator’s Guide for information about configuring the TANDEM_RECEIVE_DEPTH environment variable.

Cause  The iTP Secure WebServer encountered an error executing REPLYX for a PATHMON reply. See the error reported in the message for more details about the cause.

Effect  The httpd process exits.

Recovery  Stop the current iTP Secure WebServer environment and restart the iTP Secure WebServer.

Cause  The socket_nw function call failed with an error. See the error message reported for more details about the cause.

Effect  The request fails because of the socket call failure; the iTP Secure WebServer environment continues to function.

Recovery  Contact your service provider and provide the following information:

Cause  AWAITIOX received a system message other than OPEN or CLOSE.

Effect  Informational message only; the iTP Secure WebServer environment continues to function.

Recovery  Informational message only; no corrective action is needed.

Cause  While the httpd process was waiting for a reply from the Servlet Server Class (SSC), an error occurred in the SSC. See the error reported in the message for more details about the cause.

Effect  The httpd process handling the request stops.

Recovery  Consult the Guardian Procedure Errors and Message Manual for file-system error information. Make the appropriate correction in the SSC for the file-system error that occurred. If only one httpd process was running, restart the iTP Secure WebServer environment.

Cause  An error occurred during a reply to the Servlet Server Class (SSC). See the error reported in the message for more details about the cause.

Effect  The reply is not sent, and the SSC process might stop.

Recovery  If this error disrupts the operation of the SSC, consult the Guardian Procedure Errors and Messages Manual for error information and take the recovery action recommended for the error.

Cause  The application server class has abended. One possible reason for a server class to abend is if an application error occurs when accessing memory.

Effect  Access to any related URLs is denied.

Recovery  Check the application for defects, such as illegal memory references, that might cause it to abend.

Cause  The application server class is busy. The httpd processes outnumber application processes, and there is no idle application process to which the httpd process can link.

Effect  Access to any related URLs is denied.

Recovery  Increase the Maxservers parameter for the server class to a number greater than or equal to the value of the Maxservers parameter of the httpd server class.

Cause  The application server class is frozen.

Effect  Access to any related URLs is denied.

Recovery  Restart the server class using PATHCOM.

Cause  An invalid or nonexistent Guardian subvolume name has been specified for the Gsubvol attribute of the Pathmon directive in the configuration file (httpd.config). See the error reported in the message for more details about the cause.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify a valid Guardian subvolume name in the Gsubvol attribute of the Pathmon directive. Retry the start or restart operation.

For information about the Pathmon directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer was not able to allocate memory for the chunk request.

Effect  The request is rejected, and the current connection closes.

Recovery  The iTP Secure WebServer starts another connection. To avoid this error, reduce the value specified by the MaxRequestBody directive in the configuration file (httpd.config).

For information about the MaxRequestBody directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer has determined that the chunked request is invalid.

Effect  The request is rejected, and the connection is closed.

Recovery  The iTP Secure WebServer starts another connection.

Cause  The client sent a request that has chunk data greater than the size allowed, or the combined chunks exceed the size allowed.

Effect  The request is rejected, and the current connection closes.

Recovery  The iTP Secure WebServer starts another connection. To avoid this error, increase the value specified by the MaxRequestBody directive in the configuration file (httpd.config).

For information about the MaxRequestBody directive, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer has determined that the request has reached the KeepAliveMaxRequest count.

Effect  The request completes, and the current connection closes.

Recovery  The iTP Secure WebServer starts another connection.

Cause  Either a timeout occurred while iTP WebServer waited for the next request, or an unrecoverable error was detected during request processing.

Effect  The connection is closed, and the request completes with an error.

Recovery  The iTP Secure WebServer starts another connection.

Cause  The value contained in the Expect header of an HTTP request is other than 100-continue.

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. To avoid this error, populate the Expect header in an HTTP request only with a value of "100-continue".

Cause  The HTTP request contains an Expect and Transfer-encoding headers. The Transfer-encoding header contains a value other than "chunked".

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. To avoid this error, when the HTTP request also contains an Expect header, populate the Transfer-encoding header in an HTTP request with a value of "chunked."

Cause  The HTTP request contains an Expect and Content-Length headers. The Content-Length header value is invalid.

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. To avoid this error, populate the Content-Length header with valid values.

Cause  The HTTP protocol is not mentioned in the HTTP request header or the URL specified in the HTTP request contains spaces.

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. To avoid the error, do not have any spaces in the HTTP request URL and mention the HTTP protocol version in the HTTP request.

Cause  Content negotiation was invalid or the HTTP request Trailer header contains invalid values.

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. To avoid the error, format a proper HTTP request.

Cause  The requested file extension is not configured or there is no file extension specified in the RequiredFileExtension option of the Region directive.

Effect  The request is rejected and iTP Secure WebServer returns an internal server error.

Recovery  Make sure that the requested file extension is specified in the RequiredFileExtension option of the Region directive.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The PUT HTTP request contains the Content-Range header.

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. To avoid this error, do not add the Content-Range header with a PUT HTTP request.

Cause  An error was detected while the HTTPD server process was setting buffer pools for file caching. <s1> indicates where the error was detected (actually the failed Guardian procedure call). <s2> indicates the purpose of the pool. <n1> indicates the error returned by the operating system.

Effect  The file caching feature is disabled; however, the HTTPD server process continues to run. If the problem is corrected, file caching automatically restarts.

Recovery  Consult the Guardian Procedure Calls Reference Manual with regards to <s1> and <n1> to correct the error. If the problem persists, contact your service provider.

Cause  The file caching buffer pool is corrupted. <s1> indicates where the error was detected (actually the failed Guardian procedure call). <n1> indicates the error reported by the operating system. <n2> provides additional information about <n1>, if available.

Effect  The specific HTTPD server process stops. Depending on your configuration, the iTP Secure Webserver is likely to continue running. A new HTTPD server process may automatically start as determined by PATHMON.

Recovery  Collect the saveabend (ZZSAnnnn) file created when the HTTPD server process was terminated, and provide it to your service provider.

Cause  An error was detected when the HTTPD server process attempted to increase the size of its file cache extended segment. <n1> indicates the error returned by the operating system. Probable causes are disk space shortage or insufficient Kernel Mode Swap Facility (KMSF) resources.

Effect  No new file content is cached until the problem is corrected or more buffer space is freed. The HTTPD server process continues to run.

Recovery  Consult the Guardian Procedure Calls Reference Manual regarding the RESIZESEGMENT procedure call and <n1> to correct the error, or consult the KMSF Manual to increase swap files.

Cause  An internal error has been detected. <s1> indicates where the error was detected.

Effect  The specific HTTPD server process stops. Depending on your configuration, the iTP Secure Webserver is likely to continue running. A new HTTPD server process may automatically start as determined by PATHMON.

Recovery  Collect the saveabend (ZZSAnnnn) file created when the HTTPD server process terminates, and provide it to your service provider.

Cause  Invalid HTTP request line or HTTP request line too long.

Effect  The request is rejected and the current connection is closed.

Recovery  The iTP Secure WebServer starts another connection. Resend the request with the cause corrected.

Cause  A socket operation failed.

Effect  The socket with the error is closed. See the error message reported for more details about the cause.

Recovery  Consult the TCP/IP and IPX/SPX Programming Manual for socket error information and take the recovery action recommended for the error.

Cause  The initialization of AutoAccept failed.

Effect  iTP Secure WebServer will try to rollback to use of conventional TCP/IP.

Recovery  Consult the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to recover.

Cause  The operation attempted is not supported with AutoAccept feature enabled.

Effect  The operation fails.

Recovery  This is an informational message only; no corrective action is needed.

Cause  The AutoAccept feature is enabled and an accepted connection is passed on for load balancing.

Effect  The accepted connection is handled by another httpd process.

Recovery  This is an informational message only; no corrective action is needed..

	NOTE: EMS event 617 is common in a production environment that overloads the ems.logs. iTP WebServer is modified to reduce the occurrence of this message, from every 20th occurrence to every 2000th occurrence.

Cause  An error occurred while trying to obtain the status of httpd serverclass.

Effect  iTP Secure WebServer retries twice to get the status and on the httpd process exits.

Recovery  If PATHMON is still running, use PATHCOM to shut down the PATHMON environment manually. Consult the NonStop TS/MP and Pathway Management Programming Messages Manual for error information and take the recommended measures to recover.

Cause  The TCPMON/TCP6MON with which iTP Secure WebServer tried to communicate did not respond.

Effect  The httpd process exits.

Recovery  Start the TCPMON/TCP6MON process on the CPU specified.

Cause  The httpd process has reached its maximum capacity to handle connections with the AutoAccept feature.

Effect  The connection is passed on to another process or connection is closed.

Recovery  This is an informational message only; no corrective action is needed.

	NOTE: EMS event 620 is common in a production environment that overloads the ems.logs. iTP WebServer is modified to reduce the occurrence of this message, from every 20th occurrence to every 2000th occurrence.

Cause  Authentication accompanying the HTTP request failed.

Effect  The request is rejected and the current connection is closed.

Recovery  This is an informational message only. To avoid this error, resend the HTTP request with valid basic-authentication required by the httpd process for the requested resource.

Cause  The byte range in a multipart HTTP request exceeds the size of the file referenced in the URL.

Effect  The request is rejected and the current connection is closed.

Recovery  This is an informational message only. To avoid this error, specify correct byte ranges in the multipart HTTP request.

Cause  A Pathsend operation issued by httpd process fails with error 201.

Effect  The request is rejected and the current connection is closed.

Recovery  Consult the NonStop TS/MP and Pathway Management Programming Messages Manual for error information and take the recommended measures to recover. Correct the error and try again.

Cause  A Pathsend operation issued by httpd process fails with error 211, indicating a processor failure.

Effect  The request is rejected and the current connection is closed.

Recovery  Consult the NonStop TS/MP and Pathway Management Programming Messages Manual for error information and take the recommended measures to recover. Correct the error and try again.

Cause  A Pathsend operation issued by httpd process fails with error.

Effect  The request is rejected and the current connection is closed.

Recovery  Consult the NonStop TS/MP and Pathway Management Programming Messages Manual and the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to recover. Correct the error and try again.

Cause  The values of Numstatic and Maxserver do not match in the httpd server configuration.

Effect  The iTP Secure WebServer does not start.

Recovery  Make sure the values of Numstatic and Maxserver match in the httpd server configuration.

Cause  The -count argument of the MaxConnections configuration directive contains an out-of-range value.

Effect  The iTP Secure WebServer does not start.

Recovery  Specify the value given in the valid range with the -count argument.

	NOTE: The valid range is from 1 to 255 x Numstatic value of the httpd server class. The valid range shown in the error message is 1:510 as the Numstatic value in this case is 2 (255 x 2 = 510).

Cause  Only one processor is specified in the CPUS directive for httpd serverclass with the online-upgrade feature.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify at least two processors for the CPUS directive of httpd serverclass.

For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The iTP Secure WebServer configuration file (httpd.config) has more than two PATHMONs.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Specify only two PATHMONs in the iTP Secure WebServer configuration file (httpd.config) to use the online-upgrade feature.

Cause  iTP Secure WebServer is configured to support the online-upgrade feature and the system is configured to use a single processor.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Configure the system to use more than one processor to use the online-upgrade feature.

Cause  The PATHMON names in the configuration file (httpd.config) are identical.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Ensure that the PATHMON names are different when you are using the online-upgrade feature.

Cause  The online-upgrade feature is used and Numstatic for httpd serverclass is set to 1.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Set Numstatic for httpd serverclass to 2 or more.

Cause  iTP Secure WebServer is configured using the conventional TCP/IP transport process.

Effect  The iTP Secure WebServer environment does not start.

Recovery  Use the parallel library TCP/IP transport process instead of the conventional TCP/IP transport process to use the online-upgrade feature.

Cause  The -count argument of the MaxConnections configuration directive contains an out-of-range value.

Effect  The iTP Secure WebServer does not start.

Recovery  Specify the value given in the valid range with the -count argument.

	NOTE: The valid range is from 1 to 255 x Numstatic value of the httpd server class. The valid range shown in the error message is 1:510 as the Numstatic value in this case is 2 (255 x 2 = 510).

Cause  iTP Secure WebServer environment failed to create a new log file during a log file rollover operation.

Effect  The httpd process would fail to complete the rollover. Another httpd would try and complete it when it tries to log an event.

Recovery  If this error persists, check if the access restrictions to the log directory have changed and if the concerned disk is active.

Cause  The allocated file descriptor exceeds the maximum limit of 256.

Effect  The iTP Secure WebServer closes the open file descriptors and the current request.

Recovery  Free any outstanding I/O operations and try again.

Cause  The allocated file descriptor is already in use or invalid.

Effect  The iTP Secure WebServer closes the open file descriptors and the current request.

Recovery  Free any outstanding I/O operations and try again.

Cause  The Linkmon process on the CPU on which httpd is working has stopped.

Effect  The httpd process exits.

Recovery  If the Linkmon process auto-restarts, newly started httpd would start working with the new Linkmon. However, if this error persists, explicitly restart the Linkmon.

Cause  The GnuTLS library cannot process the received data packet. GnuTLS error number provides the reason for the failure. For more information on the error, see http://gnutls.org/manual/gnutls.html.

Effect  The iTP WebServer cannot read the data from the received data packet. This message follows another error message. For details of the root cause, refer the first error message.

Recovery  The client must re-send the request that complies with the conditions decided during the handshake. Many of these errors are transient and are resolved on re-sending the request. Contact your service provider if the problem persists.

Cause  You specified an invalid hashing algorithm with -hashAlgorithm option.

Effect  The iTP WebServer fails to start.

Recovery  Specify a supported hashing algorithm with -hashAlgorithm option.

Cause  You did not specify a hashing algorithm with -hashAlgorithm option.

Effect  The iTP WebServer fails to start.

Recovery  Specify a supported hashing algorithm with -hashAlgorithm option.

Cause  Content length of the POST request is greater than the value specified in the MaxPostRequestSize directive.

Effect  The iTP WebServer does not serve the request.

Recovery  Configure the MaxPostRequestSize directive with a value that is greater than or equal to the expected content-length of POST requests.

Cause  The ClientCADatabase directive is not configured

Effect  If not configured, the iTP WebServer continues to use the KeyDatabase file for client authentication.

Recovery  Configure the ClientCADatabase directive in httpd.stl.config file and restart the iTP WebServer.

Cause  One of the following returns this error:

Effect  The iTP Secure WebServer environment fails to start if AcceptSecureTransport directive is configured.

Recovery  Use the error-msg text to find the root cause and correct the problem.

Cause  An attempt is made to update the httpd serverclass when distributor serverclass is configured.

Effect  The httpd serverclass is not updated.

Recovery  Use restarth script to perform the update for httpd serverclass.

Cause  A serverclass name of invalid length is specified with ServerClassName directive.

Effect  The iTP WebServer environment fails to start.

Recovery  Specify a serverclass name of valid length.

Cause  The server definition that must be updated is not found in the configuration file for the specified serverclass name.

Effect  The server definition is not updated.

Recovery  Specify the correct serverclass name and retry the operation.

Cause  An attempt is made to delete the serverclass from the running pathmon and the serverclass is not found in the specified pathmon.

Effect  The serverclass is not deleted.

Recovery  None

Cause  An error occurred when the Distributor process attempted to bind an address to a socket. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The Distributor process cannot allocate enough memory for the new thread. See the error reported in the message for more details about the cause.

Effect  The Distributor process aborts.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process attempted to create a socket. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process attempted to bind an address to a socket. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process tried to accept a connection on a port. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process tried to accept a connection on a port. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process attempted a send operation.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

For Pathsend error information, see the NonStop TS/MP Pathsend and Server Programming Manual.

Cause  An error occurred when the Distributor process attempted a send operation. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The Distributor process was attempting to execute a serverclass_send operation and a retryable operation error occurred. See the errors reported in the message for more details about the cause.

Effect  The request fails.

Recovery  The operation will be reattempted after a predetermined timeout.

Cause  The Distributor process was attempting to execute a serverclass_send operation and a nonretryable operation error occurred. See the errors reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process tried to accept a connection on a port. See the error reported in the message for more details about the cause.

Effect  The request fails.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  This is the Distributor process startup message.

Effect  Informational message only.

Recovery  Informational message only; no corrective action is needed.

Cause  The Distributor process attempted to obtain a new control socket and failed. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An error occurred when the Distributor process attempted to open $RECEIVE. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The READUPDATEX procedure returned an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The timeout routine returned an error.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The setsockopt operation did not complete successfully. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The setsockopt_nw operation returned an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process continues to run.

Recovery  Informational only message: no corrective action is needed.

Cause  The buffer contained unexpected data.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The Distributor process was unable to allocate sufficient memory space. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The FILE_GETRECEIVEINFO procedure failed with an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The REPLYX procedure failed with an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The Distributor process encountered an error while writing to $RECEIVE.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  An unidentified message was received on $RECEIVE. The error might be caused by an incompatibility error between the Distributor process and the process with which it was communicating.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  No more openers are allowed at $RECEIVE. This can be caused by either of the following reasons:

Effect  The Distributor process exits.

Recovery  The recovery action depends on the cause of this message:

Cause  A system message was received.

Effect  Informational message only; the Distributor process continues to run.

Recovery  Informational message only; no corrective action is needed.

Cause  The Distributor process was attempting to process a serverclass_send operation when it encountered an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  A timeout occurred. See the error reported in the message for more details about the cause.

Effect  Informational message only; the Distributor process continues to run.

Recovery  Informational message only; no corrective action is needed.

Cause  A system error occurred. See the error text for more information.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The file descriptor of the thread did not match the file descriptor of the operation that just completed.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The accept_nw2 operation failed with an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The sock_close_reuse_nw operation failed with an error. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  The sock_close_reuse_nw operation failed to complete correctly. See the error reported in the message for more details about the cause.

Effect  The Distributor process exits.

Recovery  Contact your service provider, and provide all relevant information as described in the beginning of “Events 2000 Through 2999: Distributor Process Messages (Identifier: dist)”.

Cause  This message indicates a Distributor process configuration error.

Effect  The Distributor process exits.

Recovery  Change the number of ports specified in the Accept or AcceptSecureTransport directive so that they specify a value less than 200.

For information about the Accept and AcceptSecureTransport directives, see the iTP Secure WebServer System Administrator’s Guide.

Cause  During its startup, the Distributor process detected that the httpd LINKDEPTH configuration parameter is not set to one.

Effect  The Distributor process will not start.

Recovery  Edit the configuration file (httpd.config) and change the httpd server's LINKDEPTH parameter to 1. Start the iTP Secure WebServer. For specific information about the LINKDEPTH parameter, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The Distributor process cannot establish a context-sensitive dialog with an httpd process.

Effect  Any existing context-sensitive dialogs continue to be used. The Distributor process attempts to reestablish the dialog five times. Scaling up the environment is limited as long as this error condition exists.

Recovery  Investigate the NonStop TS/MP error condition to determine why the context-sensitive dialog cannot be established. Take corrective actions as necessary.

Cause  The Distributor process has detected that the statically configured httpd processes (those indicated by the NUMSTATIC parameter) have reached 80% of their total capacity.

Effect  None. This is a warning message indicating that you may need to configure additional capacity.

Recovery  This event does not require any explicit recovery actions; however, if you want to configure more capacity, you can increase the httpd server configuration parameters TANDEM_RECEIVE_DEPTH or NUMSTATIC until this event is not generated under normal server usage. Changing these parameters requires that you restart the iTP Secure WebServer. For specific information about the httpd server configuration TANDEM_RECEIVE_DEPTH and NUMSTATIC parameters, see the iTP Secure WebServer System Administrator’s Guide.

Cause  The Distributor process has detected that the statically configured httpd processes (those indicated by the NUMSTATIC parameter) have reached 90% of their total capacity.

Effect  None. This is a warning message indicating that you may need to configure additional capacity.

Recovery  This event does not require any explicit recovery actions; however, if you want to configure more capacity, you can increase the httpd server configuration parameters TANDEM_RECEIVE_DEPTH or NUMSTATIC until this event is not generated under normal server usage. Changing these parameters requires that you restart the iTP Secure WebServer. For specific information about the httpd server configuration TANDEM_RECEIVE_DEPTH and NUMSTATIC parameters, see the iTP Secure WebServer System Administrator’s Guide.