This section contains troubleshooting suggestions for issues relating to the ALM Octane installation.
You can also check the log here: C:\Program Files\octane\log
For an up-to-date list of installation troubleshooters, see Micro Focus Software Self-solve knowledge base article KM02703217.
When you reboot the machine, you need to manually restart the ALM Octane server:
service octane restart
The service runs in the background.
If you encounter problems opening ALM Octane in Internet Explorer, check that the domain is configured correctly:
Edit the octane.conf and provide the correct the domain.
Restart the ALM Octane server.
- Check which ports are open using, for example in Red Hat Enterprise Linux (RHEL) 6.5:
iptables -L -nv --line-number
- Open ports, for example:
iptables -I INPUT 8 -p tcp --dport 8080 -j ACCEPT
- Save changes:
service iptables save
Typically, a user is logged out of ALM Octane only after session timeout. If, however, you are unexpectedly logged out while actively working in ALM Octane, you may need to clear cookies before you can log in again.
To prevent an unexpected logout:
When working with a local DNS, make sure that you access ALM Octane only with a fully-qualified machine name, together with the machine's domain.
If JVM fails to load after the octane service is started, check that Java is properly installed and that
JAVA_HOME is configured correctly.
The C:\Program Files\octane\log\wrapper.log file shows the following error message:
ERROR | wrapper | JVM exited while loading the application. INFO | jvm 1 | Unrecognized VM option 'UseCompressedClassPointers' INFO | jvm 1 | Error: Could not create the Java Virtual Machine. INFO | jvm 1 | Error: A fatal exception has occurred. Program will exit.
To identify the important parameters of the system that may affect the installation, run the following commands:
|All installed Java applications||
|All installed Java versions||
|The JAVA_HOME property||
|The PATH property||
By default, the installation uses port 8080 for HTTP or port 8443 for HTTPS (SSL). If you change the port to a non-default value after the initial installation phase, the site Servers tab shows:
The original application server address still displays as port 8080.
The server state is inaccessible even though the server is accessible.
If errors occur during site schema creation, and the site.log file contains a message indicating that a certain tablespace or a temporary tablespace does not exist, check that the specified TableSpace or TempTableSpace is correct.
If you receive a site schema error, such as "Cannot upgrade SA. SA schema version must be lower than the current server version," do the following:
Open a backup copy of the site schema.
Fix the problem.
Reinitialize (meaning, run initserver.bat again).
Check if your DBA made manual additions to the database schema, such as adding tables, indexes, and so on. If the installation encounters objects that it does not expect in the database schema, the installation can fail.
To avoid this, create exception files. For details, see Using exception files for manual database changes.
If you still have problems:
Check that the parameters in the octane.conf file and the exception files have been entered correctly.
Check the C:\Program Files\octane\log\wrapper.log for errors.