Novell eBook Reader - Manual (Page 47)

Troubleshooting Your Liberty IDP Installation and Configuration 43
Manual (99a) 3/17/03
103
Novell Confidential 07appc.fm last saved 4/14/03
C
Troubleshooting Your Liberty IDP Installation
and Configuration
This section provides information on the following topics:
Š Troubleshooting Installation Issues
Š Troubleshooting Post-Installation Issues
Š Basic Troubleshooting Tips
Troubleshooting Installation Issues
Most of the issues that occur during installation are likely to be logged in one of the log files
described in this section. You should review each log file to identify the source of the problem. The
Apache or Tomcat errors are open source projects, so the errors logged in these types of log files
should be documented. Use a Web search engine to search for the information specific to the error.
Reviewing Log Files Created During Installation
The following four log files are created during the Liberty IDP installation:
1. apache_install.log: This log file, located by default at C:\Program
Files\Novell\apache_install.log, documents the various steps of the Apache installation. The key
portion of this file is the "Installation operation completed successfully" message shown in the
example below. any error messages in this file should be noted. Since Apache is an open source
project, Web sites such as Google* are likely to reference many of the errors reported.
1: SelfStartService 2: 0
1: StartApacheMonitor 2: 0
Action ended 10:35:15: InstallFinalize. Return value 1.
Action start 10:35:15: RemoveExistingProducts.
Action ended 10:35:15: RemoveExistingProducts. Return value 1.
Action ended 10:35:15: INSTALL. Return value 1.
=== Logging stopped: 4/2/2003 10:35:15 ===
MSI (s) (14:3C): Product: Apache HTTP Server 2.0.44 -- Installation operation
completed successfully.
2. Apache_Tomcat_Installlog.txt:This log file, located by default at C:\Program
Files\Novell\Tomcat\Apache_Tomcat_Installlog.txt, documents every instruction performed by
the Tomcat installation, including the interface with Apache through mod_jk, the various Windows
registry changes, and the setting up of the Tomcat webapps environment. The start of the file
includes a counter of errors and warnings. Ideally, you should see all successes, as shown below.
If you see any errors, you should scan the file for the specific errors reported. As with Apache,
Tomcat is open source and many of the errors or warnings encountered are likely to be documented
and referenced through Internet search engines.