Below, you will find more details on checking for the above issues and troubleshooting them.

Resolution

Important: in order to allow root cause analysis of each OA Control Panel outage, collect debug detail to be passed to the Odin Technical Support team. Use the attached oa_dump.bash script, launch it on OA Management Node, when CP is inaccessible. The script will produce a .tar.bz2 archive. Note: the OA core server should have gdb package installed preliminarily.

Check the status of servers

Verify that all the servers listed below are up and running (the malfunctioning of any server below may affect the Control Panel). Start any servers that are down:

Analyze the part of the logs that are being appended to the log file when trying to log into the Control Panel. Use search in the Odin Knowledgebase for the error and warning messages you find in the logs.

Use the 'tail' utility to get the necessary part of the log. The 'tail' utility for Windows can be found in the Support Tools pack.

Check system resources

If OA servers are deployed as virtual environments, check that the proper amount of memory is allocated to the servers.

Refer to the hardware requirements in the corresponding installation guide. For example, see the Hardware Requirements for version 5.5.

If you are using Virtuozzo products, use the native PVC/PSBM/PCS tools to check and tune memory and other resource limits configured for virtual servers: vzlist, vzctl.

Check /proc/user_beancounters for failed counters for specific resources and increase them if necessary.

For example, in case vzctl enters into container with OSA core throws:

# vzctl enter 10
Unable to fork: Cannot allocate memory

It means kmemsize is hit, as also mentioned in /var/log/messages. To increase it:

# vzctl set 10 --save --kmemsize <softlimit>:<hardlimit>

Where the limits would be bigger than the current ones.

Check and tune (if necessary) the number of Linux threads on the OA UI server. Refer to Odin Knowledgebase article #118465 for more details.

Make sure there is enough free disk space on the OA Management Node, UI and Database servers.

In the case of a Linux-based installation, you also should check the number of disk inodes available on servers using the 'df -i' command.

On PVC, PSBM or PCS servers, the amount of disk inodes allocated for a container can be changed with the vzctl utility:

Check licenses

If your servers are deployed as virtual environments, make sure the virtualization product's license is active and allows the required number of virtual environments to be launched. For PVC, PSBM or PCS servers, use the following command:

# vzlicview

Pay attention to the following parameters of the license in the output of the command above - make sure the license is active and the number of allowed CPUs, containers and Virtual Machines has not been exceeded: