F    Installation Log Files

Installation log files capture the screen output and processing of Full, Update, and Cloned installations and may provide valuable information for troubleshooting problems. This appendix contains the following information:

F.1    The Message of the Day File

A list of the installation log files created during the installation is displayed on the screen each time you log in. Example F-1 shows a sample /etc/motd file. The /etc/motd file contains the message of the day that is displayed each time a user logs in. The installation log files are located in the /var/adm/smlogs directory.

Example F-1:  Sample /etc/motd File Showing Location of Log Files

Tru64 UNIX V5.1A  (Rev. nnn); Fri Aug 24 11:44:35 EST 2001
****************************************************************************
The following files contain a record of the Update Installation session.
 
        /var/adm/smlogs/it.log             - log for it(8) utility
        /var/adm/smlogs/update.log         - update installation log file
        /var/adm/smlogs/upd_custom_files   - log of unprotected customized
                                             system files found during the
                                             update installation.
        /var/adm/smlogs/upd_obsolete_files - log of obsolete system files
                                             found during the update
                                             installation.
****************************************************************************
The installation software has successfully installed your system.
There are logfiles that contain a record of your installation.
These are:
        /var/adm/smlogs/install.cdf     - configuration description file
        /var/adm/smlogs/install.log     - general log file
        /var/adm/smlogs/install.FS.log  - file system creation logs
        /var/adm/smlogs/setld.log       - log for the setld(8) utility
        /var/adm/smlogs/fverify.log     - verification log file
 
 

F.2    Reviewing Installation Log Files

The installation log files contain useful information about problems that may have occurred during the installation process, and they should be examined for errors after the installation completes. All log files are located in the /var/adm/smlogs directory.

F.3    Full Installation Files

This section describes the following Full Installation log files:

F.3.1    The install.FS.log File

The install.FS.log file contains a log of the file system creation performed during a Full Installation. Any errors that occurred between the time you confirmed the start of the Full Installation and the completion of file system creation can be found here. This file is used only by a Full Installation.

F.3.2    The install.log File

The install.log file contains a log of all the output that was displayed to the screen from the time the file systems were created during the Full Installation until the system rebooted for the first time. This file contains information about file system creation, the operating system subsets that were loaded, and the configuration of any files that are needed to reboot the system for the first time. If the Full Installation was performed using Remote Installation Services (RIS), this file also contains a log of the load and configuration of the Worldwide Language Support subsets, if applicable. This file is used only by the Full Installation.

F.3.3    The it.log File

The it.log file contains a log of all the output that was displayed to the screen from the time the system was rebooted with the generic kernel until the time the system was rebooted for the final time with the newly built tailored kernel. Some of the information contained in this file is the configuration of the operating system software and the build of the tailored kernel. If the installation was performed using CD-ROM, this file also contains the load and configuration of the Worldwide Language Support subsets, if applicable. This file is used by the Full Installation and Update Installation processes.

F.3.4    The setld.log File

The setld.log file contains a record of all of the software subset management actions. If there was a problem loading or removing a software subset, a log of the errors will be found here. This file is maintained by the setld command and information is appended to the file whenever the setld command is used, with the exception of the setld -i operation.

F.3.5    The fverify.log File

The fverify.log file is maintained by the /usr/lbin/fverify utility, and it is modified whenever a software subset is loaded. Every time a subset is loaded, the setld command executes the fverify utility to verify that all of the files in the subset were correctly loaded. If any files were not correctly installed, a record of the files can be found here along with the reason the files failed to pass verification.

F.3.6    The install.cdf File

The install.cdf file contains a record of the information supplied during the Full Installation from the time the installation starts until you confirm the start of the installation. The install.cdf file is used to perform an Installation Cloning, which is documented in the Installation Guide -- Advanced Topics. This file is used only by the Full Installation.

F.4    Update Installation Log Files

This section describes the following Update Installation log files:

F.4.1    The update.log File

The update.log file contains a log of all the output that was displayed to the screen from the time the installupdate command was invoked until the system is rebooted under the new operating system for the first time. This log file is used only by the Update Installation process and should be examined to determine if there were any errors during the Update Installation.

F.4.2    The upd_custom_files File

The upd_custom_files file contains a list of all of the files that were saved to a .PreUPD extension as part of the Update Installation. Files saved to a .PreUPD extension are files that contained user customizations that could not be merged automatically with the version of the file shipped with the new operating system. The .PreUPD files can be used as references when manually merging customizations into the new files. The upd_custom_files file is created by the Update Installation and is used by the Update Installation Cleanup (/usr/sbin/updadmin) utility. Never modify this file.

F.4.3    The upd_PreMRG_files File

The upd_PreMRG_files file contains a list of all of the files that were saved to a .PreMRG extension as part of the Update Installation. Files saved to a .PreMRG extension are files that contained user customizations that the update tried to automatically merge with the version of the file shipped with the new operating system, but could not. The .PreMRG files can be used as a reference when manually merging customizations into the new files. This file is created by the Update Installation and is used by the Update Installation Cleanup (/usr/sbin/updadmin) utility. Never modify this file.

F.4.4    The upd_mergefail_files File

The upd_mergefail_files file contains a list of all of the protected system files that failed to automatically merge during the Update Installation. Because the merge failed, the Update Installation saved your customized file to a .PreMRG extension and then replaced the customized file with the version shipped in the new operating system. For every file in the upd_mergefail_files file, manually merge the customizations from the .PreMRG file into the new file. Failure to do the merge of customizations results in the loss of important customizations that may impact system performance. This file is created by the Update Installation process.

F.4.5    The upd_obsolete_files File

The upd_obsolete_files file should be empty because obsolete files and directories automatically are removed from the system by the Update Installation. However, this file will contain a list of obsolete directories if there are files present that were created by users or layered products. The Update Installation does not remove a directory that contains files that are not obsolete.