iTP Secure WebServer Operator Messages Manual Abstract This manual describes the operator messages reported by components of the iTP Secure WebServer and related products. The audience for this manual is system managers and operators who monitor and control the operations of an iTP Secure WebServer environment. Product Version iTP Secure WebServer (Release 7.0) Supported Release Version Updates (RVUs) This publication supports J06.03 and all subsequent J-series RVUs, H06.
Document History Part Number Product Version Published 422713-001 iTP Secure WebServer D42 (Release 4.0) July 1999 425145-001 iTP Secure WebServer D42 (Release 4.1) February 2000 427021-001 iTP Secure WebServer (Release 5.0) December 2000 429507-001 iTP Secure WebServer (Release 5.1) August 2001 429507-002 iTP Secure WebServer (Release 7.
Legal Notices Copyright 2008 Hewlett-Packard Development Company L.P. Confidential computer software. Valid license from HP required for possession, use or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. The information contained herein is subject to change without notice.
iTP Secure WebServer Operator Messages Manual Glossary Index Tables Legal Notices What’s New in This Manual iii Manual Information iii New and Changed Information iii Changes in the 429507.001 Manual About This Manual v Who Should Read This Manual Related Manuals v Notation Conventions v Abbreviations xi -iv v 1.
Contents iTP Secure WebServer Operator Messages Manual—429507-002 ii
What’s New in This Manual Manual Information iTP Secure WebServer Operator Messages Manual Abstract This manual describes the operator messages reported by components of the iTP Secure WebServer and related products. The audience for this manual is system managers and operators who monitor and control the operations of an iTP Secure WebServer environment. Product Version iTP Secure WebServer (Release 7.0) Supported Release Version Updates (RVUs) This publication supports J06.
What’s New in This Manual • • • • • New and Changed Information 442 Connection aborted. 626 MaxConnections directive: Numstatic of httpd server should be equal to Maxservers. 627 MaxConnections directive: Numeric value (0) out of range for -count argument. 628 Maximum connections reached: The server reached its maximum configured capacity. Supported release statements have been updated to include J-series RVUs. Changes in the 429507.
About This Manual This manual describes the operator messages reported by components of the iTP Secure WebServer and related products. This section includes the following information: • • • • Who Should Read This Manual Related Manuals Notation Conventions Abbreviations Who Should Read This Manual The iTP Secure WebServer Operator Messages Manual is intended for system managers and operators who will monitor and control the operations of an iTP Secure WebServer environment.
General Syntax Notation About This Manual This requirement is described under Backup DAM Volumes and Physical Disk Drives on page 3-2. General Syntax Notation The following list summarizes the notation conventions for syntax presentation in this manual. UPPERCASE LETTERS. Uppercase letters indicate keywords and reserved words; enter these items exactly as shown. Items not enclosed in brackets are required. For example: MAXATTACH lowercase italic letters.
General Syntax Notation About This Manual each side of the list, or horizontally, enclosed in a pair of brackets and separated by vertical lines. For example: FC [ num ] [ -num] [ text] K [ X | D ] address-1 { } Braces. A group of items enclosed in braces is a list from which you are required to choose one item. The items in the list may be arranged either vertically, with aligned braces on each side of the list, or horizontally, enclosed in a pair of braces and separated by vertical lines.
Notation for Messages About This Manual Line Spacing. If the syntax of a command is too long to fit on a single line, each continuation line is indented three spaces and is separated from the preceding line by a blank line. This spacing distinguishes items in a continuation line from items in a vertical list of selections. For example: ALTER [ / OUT file-spec / ] CONTROLLER [ , attribute-spec ]... !i and !o.
Notation for Messages About This Manual Nonitalic text. Nonitalic letters, numbers, and punctuation indicate text that is displayed or returned exactly as shown. For example: Backup Up. lowercase italic letters. Lowercase italic letters indicate variable items whose values are displayed or returned. For example: p-register process-name [ ] Brackets. Brackets enclose items that are sometimes, but not always, displayed.
Change Bar Notation About This Manual Change Bar Notation Change bars are used to indicate substantive differences between this edition of the manual and the preceding edition. Change bars are vertical rules placed in the right margin of changed portions of text, figures, tables, examples, and so on. Change bars highlight new or revised information. For example: The message types specified in the REPORT clause are different in the COBOL85 environment and the Common Run-Time Environment (CRE).
Abbreviations About This Manual Abbreviations The following list defines abbreviations and acronyms used in this guide. Both industrystandard terms and HP terminologies are included. cgi. Common Gateway Interface (CGI server processes and CGI library) dist. Distributor process gtacl. Runs a process in the Guardian environment from the OSS environment httpd. WebServer (httpd process) rls. Resource Locator Service (RLS) ssc. Servlet Server Class (SSC) stl. Security subsystem (SSL and PCT) wid.
Abbreviations About This Manual iTP Secure WebServer Operator Messages Manual—429507-002 xii
1 WEBSERV Messages This section describes the operator messages generated by the iTP Secure WebServer subsystem. The subsystem ID displayed by these messages includes WEBSERV as the subsystem name. Note. Negative-numbered messages are common to most subsystems. If you receive a negative-numbered message, refer to the Operator Messages Manual. Table 1-1 lists the iTP Secure WebServer Components that report operator messages: Table 1-1.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 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. 30 (#30) SSL MAC check failed Cause. An error occurrs when a record is received with an incorrect MAC.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 195 (#195) directive-name directive: invalid hostname or address (host-name) directive-name is the name of the configuration directive that caused the error. host-name is the invalid host name or address. Cause. An error occurred when the httpd process tried to obtain a host name. Effect. The iTP Secure WebServer environment does not start. Recovery.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages For information about configuration directives, see the iTP Secure WebServer System Administrator’s Guide. 197 (#197) directive-name directive: port port-num in use by another directive directive-name is the name of the configuration directive that caused the error. port-num is the port number already in use. Cause.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 201 (#201) directive-name directive: could not bind server to server-name port port-num (err-msg) directive-name is the configuration directive being executed. server-name is the name of the server. port-num is the port number. err-msg is the OSS-supplied error message text that further defines the cause of the error. Cause. The iTP Secure WebServer could not bind to the specified server port.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages For information about the User directive, see the iTP Secure WebServer System Administrator’s Guide. 205 (#205) Group directive: can’t change to group ‘group-name’ (server not started as root) group-name is the invalid user name. Cause. The iTP Secure WebServer environment stopped because the user name specified in the User directive section of the configuration file (httpd.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 207 (#207) User directive: can’t change to user ‘user-name’ (server not started as root) user-name is the user name. 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 209 (#209) Chroot directive: can’t access directory ‘dir-name’ (err-msg) dir-name is the directory name. err-msg is the OSS-supplied error message text that further defines the cause of the error. Cause. The specified directory cannot be accessed by the server process. Refer to the error message reported for more details about the cause. Effect. The iTP Secure WebServer environment stops. Recovery.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 220 (#220) process out of memory 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 223 (#223) pid-action: can’t open pid file ‘pid-filename’ for writing pid-action is the action where the PID file error occurred. The values are: PidFile directive A PID file error occurred when attempting to execute the PidFile directive. -pidfile option A PID file error occurred when attempting to execute the -pidfile option when the server was run.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages err-msg is an error message that describes the chdir error encountered. See the description of the chdir command in the OSS System Calls Reference Manual for an explanation of the chdir error messages. Cause. The iTP Secure WebServer could not change to the specified root directory. Refer to the error message reported for more details about the cause. Effect. The iTP Secure WebServer environment doesn’t start.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 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. Also, make sure that the correct key database is in use. Lastly, make sure that the certificate was properly added to the key database.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 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: • • • The message number The configuration file (httpd.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 547 (#547) Logic error in TandemInit. Contact your HP Analyst. 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: • • • • The message number The configuration file (httpd.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages Cause. The new PATHMON process could not be created. Refer to 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 552 (#552) ERROR: pathmon shutdown error perror-code; Info:ferror-code, Detail ferror-subcode perror-code is a code for the PATHMON error that occurred. See the NonStop TS/MP and Pathway Management Programming Messages Manual for explanations of the PATHMON error codes. ferror-code is a code for the file-system error that occurred.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. ferror-subcode is a subcode providing more detailed information about the file-system error. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system subcodes. Cause. The PATHMON process coldstart failed.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 556 (#556) SERVERCLASS_SEND_error: ferror-code ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 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).
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 559 (#559) iTP WebServer configuration not changed 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).
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 563 (#563) accept: AWAITIOX failed with error ‘err-msg’ err-msg is the OSS-supplied error message text that further defines the cause of the error. Cause. AWAITIOX of accept_nw2 function call failed with an error. Effect. The socket with the error is closed. Refer to the error message reported for more details about the cause. Recovery.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages Cause. An error occurred when the iTP Secure WebServer was communicating with a Pathway server. Refer to 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: • • • The error messages reported The log file The configuration file (httpd.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages Cause. The FILE_GETRECEIVEINFO function call failed with an error. Refer to 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages required, stop the iTP Secure WebServer environment and restart the iTP Secure WebServer. 571 (#571) can not open $RECEIVE ferror-code ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. Cause. The iTP Secure WebServer could not open $RECEIVE because of an error.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 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.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 577 (#577) accept:socket failed with error err-msg err-msg is the OSS-supplied error message text that further defines the cause of the error. Cause. The socket_nw function call failed with an error. Refer to the error message reported for more details about the cause. Effect. The request fails due to the socket call failure; the iTP Secure WebServer environment continues to function. Recovery.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages Recovery. Consult the Guardian Procedure Errors and Message Manual for filesystem error information. Make the appropriate correction in the SSC for the filesystem error that occurred. If only one httpd process was running, restart the iTP Secure WebServer environment. 583 (#583) REPLYX to SSC failed ferror-code ferror-code is a code for the file-system error that occurred.
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages 586 (#586) Pathsend failed with error 913 because serverclass frozen Cause. The application server class is frozen. Effect. Access to any related URLs is denied. Recovery. Restart the server class using PATHCOM. 591 (#591) Cannot use Gsubvol ’subvol’ specified in pathmon directive. Error ferror-code subvol is the name of the nonexistent Guardian subvolume.
WEBSERV Messages Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) For information about the MaxRequestBody directive, see the iTP Secure WebServer System Administrator’s Guide. 597 (#597) the chunk request is invalid, bad chunk size or content. 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.
WEBSERV Messages Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) Effect. The connection is closed, and the request completes with an error. Recovery. The iTP Secure WebServer starts another connection. 609 (#609) File cache initialization error () for (); error: Cause. An error was detected while the httpd server process was setting buffer pools for file caching. indicates where the error was detected (actually the failed Guardian procedure call).
Events 1 through 999: WebServer (httpd process) Messages (Identifier: httpd) WEBSERV Messages Recovery. Consult the Guardian Procedure Calls Reference Manual regarding the RESIZESEGMENT procedure call and to correct the error, or, consult the KMSF Manual to increase swap files. 612 (#612) httpd server internal error; detected by () Cause. An internal error has been detected. indicates where the error was detected. Effect. The specific httpd server process stops.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 628 Maximum connections reached: The server reached its maximum configured capacity. Type: Informational Cause. The iTP WebServer reached the maximum configured capacity specified in the -count argument of Maxconnections. Effect. The iTP WebServer does not serve any new incoming connection. Recovery. No recovery. It is an Informational message.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages Cause. An error occurred when the Distributor process attempted to bind an address to a socket. Refer to 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) above.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 2004 (#2004) bind_nw failed: cound not bind to port port-num in transport tcp-name errno socket-error port-num is the port number where the error occurred. tcp-name is the name of the TCP/IP process where the error occurred. socket-error is an error code returned by the TCP/IP socket function. See the TCP/IP and IPX/SPX Programming Manual for explanations of socket errors. Cause.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 2006 (#2006) accept_nw failed: could not accept to port port-num errno socket-error port-num is the port number where the error occurred. socket-error is an error code returned by the TCP/IP socket function. See the TCP/IP and IPX/SPX Programming Manual for explanations of socket errors. Cause. An error occurred when the Distributor process tried to accept a connection on a port.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages pathsend-error is a code for the Pathsend error that occurred. See the NonStop TS/MP Pathsend and Server Programming Manual for explanations of the Pathsend error codes. Cause. An error occurred when the Distributor process attempted a send operation. Refer to the error reported in the message for more details about the cause. Effect. The request fails. Recovery.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 2010 (#2010) serverclass_send fail server-class-name, Nonretryable Pathsend error pathsend-error, File system error filename ferror-code server-class-name is the name of the PATHWAY server class. pathsend-error is a code for the Pathsend error that occurred. See the NonStop TS/MP Pathsend and Server Programming Manual for explanations of the Pathsend error codes.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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) on page 1-33. 2012 (#2012) distributor started: built distributor-build-stamp distributor-build-stamp is the timestamp of when the Distributor process started. Cause. This is the Distributor process startup message. Effect.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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) on page 1-33. 2015 (#2015) READUPDATEX failed ferror-code ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. Cause.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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) on page 1-33. 2018 (#2018) setsockopt_nw SO_RCVBUF: failed with errno=socket-error socket-error is an error code returned by the TCP/IP socket function.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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) on page 1-33. 2021 (#2021) FILE_GETRECEIVEINFO failed ferror-code ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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) on page 1-33. 2024 (#2024) Unidentified message received on $RECEIVE Cause. An unidentified message was received on $RECEIVE.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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. 2027 (#2027) AWAITIOX: pmon error ferror-code ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. Cause.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 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) on page 1-33. 2030 (#2030) Thread fd=file-desc1, awaitiox fd= file-desc2, THESE SHOULD MATCH!!! file-desc1 is the file descriptor of the thread.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 2032 (#2032) sock_close_reuse_nw error:errno=socket-error socket-error is an error code returned by the TCP/IP socket function. See the TCP/IP and IPX/SPX Programming Manual for explanations of socket errors. Cause. The sock_close_reuse_nw operation failed with an error. Refer to the error reported in the message for more details about the cause. Effect. The Distributor process exits. Recovery.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages 2055 (#2055) httpd LINKDEPTH not equal 1 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.
WEBSERV Messages Events 2000 through 2999: Distributor Process Messages (Identifier: dist) 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.
Events 2000 through 2999: Distributor Process Messages (Identifier: dist) WEBSERV Messages HP recommends that you adjust httpd server configuration parameters TANDEM_RECEIVE_DEPTH and NUMSTATIC until this event is not generated under normal server usage. 2060 (#2060) Maximum configured httpd servers are now started Cause. The Distributor process detected that the number of httpd processes running has reached its maximum limit. Effect. None.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages Effect. The Distributor process stops. Recovery. Correct the error condition, and restart the iTP Secure WebServer. 2063 (#2063) Unable to get httpd serverclass status. Error error-condition error-condition reports the error condition. Cause. The Distributor process cannot obtain the current status of the httpd server class from PATHCOM. Effect. The Distributor process continues.
WEBSERV Messages Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) 3002 (#3002) cgilib: Can’t set an alarm signal, aborting! Cause. The CGI library could not set the CGI_flush timer. Effect. The operation is aborted, and the generic or Pathway CGI process where the error occurred exits. Recovery.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages See the descriptions of the CGI_fflush, CGI_set_fflush_timer, and the TANDEM_CGI_FFLUSH_TIMER in the iTP Secure WebServer System Administrator’s Guide for details. 3004 (#3004) cgilib: Internal logic error. aborting! Please contact HP. Cause. The CGI library attempted to change the CGI_fflush timer, but could not because the local_alarm internal routine was invoked with improper parameters. Effect.
WEBSERV Messages Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) Effect. The generic or Pathway CGI process where the error occurred exits. Recovery. Check for the following possible causes: • • The value specified in your user code for the CGI_set_fflush_timer procedure, or the value specified in the server configuration for the TANDEM_CGI_FFLUSH_TIMER Pathway environment variable, is out of the allowable range.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages 3007 (#3007) cgilib: Malloc failure! Cause. The CGI library called the malloc function, but was unable to obtain memory from the heap. Effect. The generic or Pathway CGI process where the error occurred exits. Recovery. Check for the following possible causes: • • Insufficient heap size Memory leaks in user-written code If any of these conditions exist, correct them.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages Recovery. Consult the Guardian Procedure Errors and Messages Manual for error information and take the recommended measures to correct the error. 3010 (#3010) cgilib: Error on Receive Read=ferror-code ferror-code is an error code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. Cause.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages • A saveabend file of the CGI process 3012 (#3012) cgilib: CGI_printf Buffer Overflow Cause. Insufficient buffer space was allocated to hold the CGI output data. Effect. The generic or Pathway CGI process where the error occurred exits. Recovery. Ensure that user-written code does not generate output greater than 32 kilobytes. 3014 (#3014) cgilib: Unable to Open $RECEIVE Cause.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages 3016 (#3016) cgilib: Improper Dialog Cause. The CGI library and the httpd server interact using Pathsend dialogs. The proper sequence for a dialog conversation on $RECEIVE is that the first message contains a DIALOG_BEGIN indication, and the following messages contain a DIALOG_CONTINUE indication.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages 3018 (#3018) cgilib: Unexpected Error reading $RECEIVE error=ferror-code ferror-code is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. Cause. The CGI library encountered an error while reading $RECEIVE. Refer to the error reported in the message for more details about the cause. Effect.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages Effect. Error logging will not occur to an exclusive file, however, fatal errors are still reported to EMS and all errors are also reported in the trace log file, if tracing is enabled. Normal gcache server processing will not be interrupted. Recovery. Confirm that the gcache server’s environment variable, ERRORFILE has a valid path and filename. Correct if necessary.
Events 3000 through 3999: Common Gateway Interface (CGI Server Processes and CGI Library) WEBSERV Messages Recovery. If any of these conditions exist, correct them. 5005 (#5005) GCACHE: MAINLOOP: $RECEIVE READ failed err: error-num error-num is a code for the file-system error that occurred. See the Guardian Procedure Errors and Messages Manual for explanations of the file-system error codes. Memory could not be allocated from the heap for the incoming session key cache item. Cause.
Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) WEBSERV Messages Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) If you encounter a WebSafe2 message and further assistance is required, contact your service provider and provide the following types of information: • • • Descriptions of the problem and accompanying symptoms Details from the message or messages generated Supporting documentation such as EMS logs, WID trace files (which log communications between the WebSafe2 unit
Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) WEBSERV Messages Recovery. Replace the cipher specification in the AcceptSecureTransport directive with a supported value as listed in the iTP Secure WebServer System Administrator’s Guide. For information about the AcceptSecureTransport directive, see the iTP Secure WebServer System Administrator’s Guide. 6003 (#6003) SERVERCLASS_SEND_ to WID failed. Pathmon error: perror-code, file sys error: ferror-code.
Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) WEBSERV Messages 6006 (#6006) Command DECRYPT_DATA failed. WID error: error-num error-text error-num is a code for the WID error returned. error-text is the text of the WID error returned. Cause. The WebSafe2 Interface Driver (WID) server returned a WID error when it received a request to decrypt a master key. Effect. The request aborts. Recovery.
Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) WEBSERV Messages 6008 (#6008) Command GET_CERTIFICATE failed. WID error: error-num error-text error-num is a code for the WID error returned. error-text is the text of the WID error returned. Cause. The WebSafe2 Interface Driver (WID) server returned a WID error when the GET_CERTIFICATE function was called. Effect. The request aborts. Recovery.
Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) WEBSERV Messages 6010 (#6010) Get certificate from WID server pathmon-name:server-class failed. pathmon-name is the name of the PATHMON process for the environment where the WID processes are running. server-class is the name of the WID server class. Cause. The iTP Secure WebServer cannot get the certificate from the WebSafe2 Interface Driver (WID) server. Effect. The request aborts. Recovery.
Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) WEBSERV Messages Recovery. Contact your service provider, and provide the information described in the beginning of Events 6000 through 6999: WebSafe2 Messages (Identifier: wsf) on page 1-61. 6016 (#6016) The DN to be used by WebSafe is not found. Make sure that AcceptSecureTransport -cert or SSLName directive specify the correct DN Cause. The certificate specified in the AcceptSecureTransport command was not found in the WID keyfile. Effect.
Events 7000 through 7999: Servlet Server Class (SSC) Messages (Identifier: ssc) WEBSERV Messages Effect. The Secure Sockets Layer (SSL) handshake fails. Recovery. Informational message only; no corrective action is required. 6021 (#6021) Cannot make SSLV3 connection with this cert. Only SSLV2 will be supported. SSLV2 cipher DES-CBC3-MD-5 will be disabled. Cause. The iTP Secure WebServer was configured with a WebSafe2 unit with a version prior to 2.6.11 that does not support SSLV3 and cipher DES-CBC3-MD5.
Events 7000 through 7999: Servlet Server Class (SSC) Messages (Identifier: ssc) WEBSERV Messages Recovery. None. 7002 (#7002) Servlet Server Class Start Failed. Servlet Server Class Object code vproc = T1222V10_xxxx_xx does not match Class file vproc of: T1222V10_xxxx_xx. Terminating Server. Cause. The vproc of the Servlet Server Class object code does not match the vproc of servlet Class file. Effect. The Servlet Server Class can not start. Recovery.
Events 7000 through 7999: Servlet Server Class (SSC) Messages (Identifier: ssc) WEBSERV Messages 7005 (#7005) Abort!!! Cause. An exception occurred in the Java Runtime environment which caused an abort. The exception that occurred is reported in the servlet error log. Effect. The Servlet Server Class (SSC) process where the error occurred aborts. Recovery. Check the servlet error log to determine the exception that occurred. Follow the recommended measures to recover.
Events 7000 through 7999: Servlet Server Class (SSC) Messages (Identifier: ssc) WEBSERV Messages Recovery. Check that the pathname being sent is a valid pathname. If the name is valid and the problem persists, contact your service provider and provide the following information: • • The number of this error message The configuration files (httpd.config) 7008 (#7008) httpd returned error for Mime type translation Cause.
WEBSERV Messages Events 7000 through 7999: Servlet Server Class (SSC) Messages (Identifier: ssc) Recovery. Mime types cannot exceed 500 bytes in length. Check the Java Servlet code to determine which mime type is being sent that exceeds the buffer. Retry the operation using a valid mime type. 7013 (#7013) Servlet Server Class Object code call to getProcName() failed Cause. The servlet server process was unable to obtain its own process name during process startup. Effect.
WEBSERV Messages Events 7000 through 7999: Servlet Server Class (SSC) Messages (Identifier: ssc) iTP Secure WebServer Operator Messages Manual—429507-002 1- 72
Glossary This glossary defines terms used both in this manual and in other manuals. Both industry-standard terms and HP-specific terms are included. browser. A graphical user interface (GUI) used to access sites on the World Wide Web. Netscape, Internet Explorer, Mosaic, and Lynx are commonly used browsers. CCITT (International Telegraph and Telephone Consultative Committee). A division of the United Nations International Telecommunications Union that coordinates standards-setting activities. CGI.
domain Glossary domain. In the Internet, a part of the naming hierarchy. Syntactically, a domain name consists of a sequence of names (labels) separated by periods (dots). Ethernet. A popular local area network (LAN) technology invented at the Xerox Corporation Palo Alto Research Center. An Ethernet itself is a passive coaxial cable; the interconnections all contain active components. Ethernet is a best-effort delivery system that uses CSMA/CD technology.
Internet Protocol (IP) Glossary Internet Protocol (IP). The Internet standard protocol that defines the Internet datagram as the unit of information passed across the Internet and that provides the basis for the Internet connectionless, best-effort packet delivery service. Internet. Physically, a collection of packet-switching networks interconnected by gateways, along with protocols that allow them to function logically as a single, large, virtual network.
packet Glossary packet. The unit of data sent across a packet-switching network. While some Internet literature uses it to refer specifically to data sent across a physical network, other literature views the Internet as a packet-switching network and describes IP datagrams as packets. PATHMON. The central controlling process for a NonStop TS/MP application. Pathway. The former name of NonStop TS/MP, a product providing transaction services for persistent, scalable, transaction-processing applications.
server programs Glossary server programs. In NonStop TS/MP, programs that handle the data manipulation and data output activities for online transaction processing applications. Server programs are designed to receive request messages from requester programs; perform the desired operations, such as database inquiries or updates, security verifications, numerical calculations, or data routing to other computer systems; and return reply messages to requester programs. Simple Mail Transfer Protocol (SMTP).
wait mode Glossary wait mode. In the NonStop Kernel operating system, the mode in which the called procedure waits for the completion of an input/output (I/O) operation before returning a condition code to the caller. Compare nowait mode. Web Container. A Java runtime environment that manages the lifecycle of servlets and JSP . Web clients. Programs that execute on IBM-compatible PC, Apple Macintosh, or Unix platforms, among others.
Index E error messages Distributor 1-1 iTP Secure WebServer Operator Messages Manual—429507-002 Index -1
iTP Secure WebServer Operator Messages Manual—429507-002 Index -2
Content Feedback First Name: __________________ Phone: _____________________ Company: ___________________ Last Name: _________________ e-mail address: ______________ (All contact information fields are required.) If you’re reporting an error or omission, is your issue: Minor: I can continue to work, but eventual resolution is requested. Major: I can continue to work, but prompt resolution is requested. Critical: I cannot continue to work without immediate response.
