This section describes the information provided about error conditions detected by this component.
PSSP security components maintain several log files. One is used to record the administrative tasks that are performed when configuring the security services on the system. It contains text messages indicating both normal progress and error conditions encountered in performing those tasks. The other files are kept by the Kerberos V4 daemons. The content is also message text.
The kerberos and kadmind daemons record only their initial startup and any errors encountered. The kpropd daemon records the normal progress of Kerberos V4 database propagation as well as errors encountered.
SP security configuration scripts that are used to set up the security services during installation, migration, and partitioning record their progress and completion status in the following file: /var/adm/SPlogs/auth_install/log. The configuration log file is trimmed automatically at midnight to its last 500 lines.
This is an example of the configuration log:
************************************************ * Beginning of logging for -- spsetauth * Fri Dec 3 14:39:33 1999 ************************************************ ************************************************ * Beginning of logging for -- updauthfiles * Fri Dec 3 14:39:35 1999 ************************************************ updauthfiles: This command invoked as: updauthfiles updauthfiles: About to update local file: /.rhosts updauthfiles: Updated local file: /.rhosts updauthfiles: About to update local file: /.k5login ************************************************ *** End of logging for -- updauthfiles *** Fri Dec 3 14:39:57 1999
Each Kerberos V4 daemon has a log file in which errors are recorded. The Kerberos V4 log files are not automatically trimmed.
For a full list of DCE daemon logs, refer to IBM DCE for AIX, Version 3.1: Administration Guide - Core Components. This is an example of the log file:
9:19:57: ------------------------------------------------------------
show.cfg is starting at 1999-11-09-09:19:57.078-05:00I---.
09:19:57: The DCE configuration log file was successfully backed up to
/opt/dcelocal/etc/cfgdce.bck.
09:19:57: Parsing command line data.
09:19:57: show.cfg
09:19:57: Querying the supported protocols.
09:19:57: Using protseqs.rpc.
09:19:57: Querying IP information.
09:19:57: Querying currently configured components.
09:19:57: Reading the file, /opt/dcelocal/etc/cfgdce.dat...
09:19:57: Finished reading the file, /opt/dcelocal/etc/cfgdce.dat.
09:19:57: Determining the security server type.
09:19:57: Determining the Directory server type.
09:19:57: Waiting up to 30 seconds for "mget_dir_reptype_worker"
to complete.
09:20:02: Authenticating as hosts/c166cw.ppd.pok.ibm.com/self.
09:20:03: Gathering component state information...
09:20:03: Querying the supported protocols.
09:20:03: Using protseqs.rpc.
09:20:03: Querying IP information.
09:20:03: Reading the file, /opt/dcelocal/etc/cfgdce.dat...
09:20:03: Finished reading the file, /opt/dcelocal/etc/cfgdce.dat.
09:20:03: Querying currently configured components.
09:20:03: Reading the file, /opt/dcelocal/etc/cfgdce.dat...
09:20:03: Finished reading the file, /opt/dcelocal/etc/cfgdce.dat.
09:20:03: Determining the security server type.
09:20:03: Determining the Directory server type.
09:20:03: Waiting up to 30 seconds for "mget_dir_reptype_worker"
to complete.
09:20:03: Reading the file, /opt/dcelocal/etc/cfgdce.dat...
09:20:03: Finished reading the file, /opt/dcelocal/etc/cfgdce.dat.
09:20:03: Writing the file, /opt/dcelocal/etc/cfgdce.dat...
09:20:03: Finished writing the file, /opt/dcelocal/etc/cfgdce.dat.
09:20:04: Waiting up to 60 seconds for "check_secval_status_worker"
to complete.
09:20:04: Querying the supported protocols.
09:20:04: Using protseqs.rpc.
09:20:04: Waiting up to 20 seconds for "isListeningWorker dced"
to complete.
09:20:04: Querying the currently configured cell name.
09:20:04: Querying the supported protocols.
09:20:04: Using protseqs.rpc.
09:20:05: Waiting up to 20 seconds for "isListeningWorker rpc"
to complete.
09:20:05: Querying the currently configured cell name.
09:20:05: Querying the supported protocols.
09:20:05: Using protseqs.rpc.
09:20:06: Waiting up to 20 seconds for "isListeningWorker sec_svr"
to complete.
09:20:06: Querying the currently configured cell name.
09:20:08: Waiting up to 20 seconds for "isListeningWorker cds_svr"
to complete.
09:20:08: Querying the currently configured cell name.
09:20:10: Waiting up to 20 seconds for "isListeningWorker cds_cl"
to complete.
09:20:10: Querying the currently configured cell name.
09:20:10: 09:20:10: Component Summary for Host: c166cw.ppd.pok.ibm.com 09:20:10: Component Configuration State Running State 09:20:10: Security Master server Configured Running 09:20:10: Security client Configured Running 09:20:10: RPC Configured Running 09:20:10: Initial Directory server Configured Running 09:20:10: Directory client Configured Running 09:20:10: 09:20:10: The component summary is complete. 09:20:11: logout hosts/c166cw.ppd.pok.ibm.com/self