If a problem occurs during installation or uninstallation, check the appropriate log file in the logs directory:
Solaris OS: /var/sadm/install/logsLinux: /var/opt/sun/install/logs
Examining the uninstall and installer log files (along with the Java ES configuration log and component logs) can help locate the source of problems. For example, you can compare the packages listed in the installation log to the packages listed in the uninstallation log.
Most logs have two versions:
An A version of the log file records completion.
A B version of the log file contains more detailed log messages.
The following table lists the formats of the log files.
Table 9–1 Java ES Log File Name Formats
Logged Entity |
Log File Name Format |
---|---|
Installer: components |
Java_Enterprise_System_install.Atimestamp Java_Enterprise_System_install.Btimestamp Java_Enterprise_System_Config_Log.id |
uninstaller |
Java_Enterprise_System_uninstall.Atimestamp Java_Enterprise_System_uninstall.Btimestamp Java_Enterprise_System_Config_Log.id |
Installation summary |
Java_Enterprise_System_Summary_Report_install. timestamp JavaES_Config_log.timestamp JavaES_PanelFlow_log.timestamp JavaES_MasterLog_log.timestamp Java_Enterprise_System_Summary_Report_ uninstall. timestamp |
To use the log files for troubleshooting, attempt to isolate the first problem that occurred. Often, the first problem leads to successive problems.
The log files can give you clues that determine your next steps, such as these:
If there was a configuration problem, look at the configuration summary to examine the settings you used.
If there was a directory conflict, check that you did not specify a directory that is reserved by a component.