If your Access Gateway Service fails to install, use one of the following procedures to discover the cause:
The following instructions explain how to run the installation program in debug mode and how to clean up after such an installation:
Use the following command to start the installation program:
LAX_DEBUG=true ./<filename>.bin -DAM_INSTALL_DEBUG=true -DAM_INSTALL_DEBUG_JAVA=true
Replace <filename> with the name of the executable.
The output is displayed as the execution occurs.
Additional information is logged to the /tmp/novell_access_manager/ags_installxxxxx.log file.
Use the output and the log file to discover the cause of the problem.
After you run the installation in debug mode, you must clean up the results
Change to the /tmp/novell_access_manager/directory.
Delete the following files:
ags_installxxxxx.log
AccessGateway_InstallerLog-<timestamp>.log
IMPORTANT:You need to delete the log files because they contain sensitive information in clear text.
The following instructions explain how to run the installation program in debug mode and how to clean up after such an installation.
Use the following command to start the installation program:
<filename>.exe -DAM_INSTALL_DEBUG=true -DAM_INSTALL_DEBUG_JAVA=true
Replace <filename> with the name of the executable.
Press the Ctrl key until the progress bar reaches 100% and goes away.
A terminal window opens to display standard output.
Additional verbose information is sent to the \agsinstall_debug.txt file.
Use the output and the log file to discover the cause of the problem.
After you run the installation in debug mode, you must clean up the results:
Delete the \agsinstall_debug.txt file.
Delete the installation log files in the following directories:
Windows 2003 Server and Windows 2008 Server: \agsinstall.log
Windows 2003 Server: \Program Files\Novell\log
Windows 2008 Server: \Program Files (x86)\Novell\log
IMPORTANT:You need to delete the log files because they contain sensitive information in clear text.