Troubleshooting

Reality records error details in various error logs depending on what class of error has occurred. Below is a list of useful log files for diagnosing problems when starting and running Reality on UNIX:

$REALROOT/files/daemon.log

Records major events and errors with Reality daemons and Reality processes.

/var/adm/RCS/RCS_SESS_LOG (or /usr/adm/RCS/RCS_SESS_LOG on Linux)

Records incoming and outgoing connections both successful and failed.

/var/adm/RCS/RCS_EVENT_LOG (or /usr/adm/RCS/RCS_EVENT_LOG on Linux)

Records other SMANAGER (Reality session manager) activity.

Error numbers

Reality error numbers can be converted into human readable messages by using the perror command from the UNIX shell; for example:

$ perror 2004
Error  2004: RFE_NOITEM    Item does not exist

From Reality TCL you can use:

: sys perror 2004

Example messages

Below is an example of a message logged in the daemon log.

Oct 30 07:55:20 #2240  tlrestore WARNING: Image 000000E4 Result (2027) File section already exists

This message indicates that an attempt was made by the 'tlrestore' process (part of Reality resilience) to create a file, which already exists on the database. Running perror 2027 would report:

Error  2027: RFE_SECTEXISTS          File section already exists.

Note

More verbose error logging can be activated by running killreal -l 6 from the UNIX shell prompt.

Below is an example of information logged in the session log:

Session :11  Thu, 21 Nov 2002  15:14:29  IC
    System :demodb, User Id :SYSMAN, Account :SYSMAN, Server :SQLSRVR
    Client Id :, PLID :INET-207.238.117.133-9
    Class :Process, Flags :0, Timeout 1
Session :11  Thu, 21 Nov 2002  15:14:29  Session Terminated by Server Rejection
    Database Initialisation Failed 2008

Running perror 2008 would report:

Error  2008: RFE_INVACCPASS          Invalid logon attempt