HP 3000 Manuals HP 3000 Manuals
The Event Log The Event Log is a collection of text files containing messages of interest from the components of X.400 (MTA, RTS, encoder, decoder, x4xfer, and x4mailer). The subject of these messages are routine events which are a normal part of message processing. This logging facility is optional and should not be confused with the error logging facility, which records errors regardless of whether the Event Log facility is enabled or not. You can enable or disable event logging using the x4eventlog command. Run x4stat to determine which event logs are enabled. HP X.400 maintains at least one event log in the /usr/spool/x400/log directory for each component. Do not remove event log files when X.400 is running. If more disk space is needed, use x4agelog to age the event log files; and then remove the archived files. Without aging the event log files, the UNIX commands mv and rm do not free more disk space until X.400 is stopped. The MTA Event Log File The MTA maintains one log file that records all incoming and outgoing messages (mta.evnt), and how they are delivered, routed, or otherwise handled. For an adjacent MTA not configured in x4admin, incoming and outgoing transfer information is logged in default.evnt. The RTS Event Log Files The RTS maintains two types of log files. One type of log file is maintained for each configured adjacent (remote) MTA (r###.evnt where ### is the output queue number assigned to the adjacent MTA). These files record information about incoming and outgoing transfers. The other log file contains information about the process ID of the RTS, when the RTS is brought up and down, and when and which RTS configuration files are modified while RTS is running (rts.evnt). RTS Message Transfer Problem
NOTE When troubleshooting X.400 problems, OTS (nettl) header and PDU tracing for Session should be on.
To troubleshoot an RTS message transfer problem with respect to the OTS, you should do the following: 1. Determine the RTS event log file (in the /usr/spool/x400/log directory) that corresponds to the adjacent X.400 node with which you are having the problem (for example, r001.evnt, r002.evnt, etc.). 2. View the file and look for the message that describes what happened (for example, a connection failure or a user abort). The following is an example of an event log for a connection refusal: 11/04-16:10:56 Received S-CONNECT.Confirm (Refuse) (X4EVENT 3575) REASON = Validation failure Path ID: 1 3. Since OTS no longer logs the Path ID and Process ID for session and transport events, use the time stamp and type of event to associate RTS and OTS messages. using the example above, you would search for an OTS message logged at "16:10:56" which was an S-CONNECT.Confirm. Note that the names used for the different session PDUs by X.400 and OTS are not always spelled exactly the same. The following is an example of the OTS log message corresponding to the RTS log message in step 2: ^^^^^^^^^^^^^^^^^^^^^^^^^^^HP OSI MGMT^^^^^^^^^^^^^^^^^^^^^^^^^^^ Timestamp : Mon Nov 04 1991 16:10:55.667546 Process ID : ICS: Subsystem : SESSION User ID ( UID ) : -1 Trace Kind : HDR IN TRACE Device ID : -1 Path ID : -1 Connection ID : -1 [99730 S-CONNECT-Cnf(Neg) Buffer1 is Session Id Buffer2 is Udta Srv=00[....] Reason=02 Capa=0100 4. In the case of provider aborts, a reason code in hexadecimal is logged in r###.evnt. Refer to chapter 7 in the OSI Planning and Troubleshooting Guide for a description of the reason code. The Encoder, Decoder, and x4xfer Event Log Files The encoder, decoder, and x4xfer each maintain their own log file (encoder.evnt, decoder.evnt, and x4xfer.evnt) which records incoming and outgoing messages on the HP X.400/HP Desk side of X.400. The x4mailer Event Log Files The x4mailer maintains two log files. One records events and errors associated with incoming messages (x4min.evnt); and the other records events and errors associated with outgoing messages ( x4m.evnt). Both the error log and event log messages are logged into the x4mailer log files.