iTP Secure WebServer Operator Messages Manual

WEBSERV Messages
iTP Secure WebServer Operator Messages Manual—429507-002
1-59
Events 3000 through 3999: Common Gateway
Interface (CGI Server Processes and CGI Library)
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. Stop the gcache server and restart.
5002
trace-file-name
is the name of the file specified in the “Env TRACEFILE=” command.
Cause. The iTP Global Cache server could not open the trace log file.
Effect. No trace records will be logged. Normal gcache server processing will not be
interrupted.
Recovery. Confirm that the gcache server’s environment variable, TRACEFILE has a
valid path and filename. Correct if necessary. Stop the gcache server and restart.
5003
Cause. The iTP Global Cache server could not open $RECEIVE because of an error.
Effect. The gcache 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 gcache server and restart.
5004
Cause. Memory could not be allocated from the heap for the incoming session key
cache item.
Effect. The gcache process exits.
Check for the following possible causes:
•
Insufficient heap size
•
Memory leaks in user-written code
(#5002) GCACHE: can't open trace log file trace-file-name
(#5003) GCACHE: MAINLOOP: unable to open $RECEIVE
(#5004) GCACHE: MAINLOOP: DeMarshall memdup failed, SessionCacheItem is
null, WRITE_CACHE failed