Owners Manual

Troubleshooting Your Application | Troubleshooting
OMNM 6.5.2 User Guide 693
Application Server Does Not Start
To find application server issues, search the server log ( \oware\jboss-
x.x\server\oware\log\server.log
) file for the word error . Review the log for the first
error or exception. This is typically the item that needs to be resolved and the most relevant for
troubleshooting information.
• Installation checks to confirm your hardware is adequate, but if you are installing to a VM,
you can reduce hardware allocations after that installation. If you do that, your application
server may not start and will provide no logs. This indicates you may have inadequate
hardware or an inadequate portion of your hardware assigned to the VM running
OpenManage Network Manager. If this occurs, check the hardware requirements, and
reconfigure your VM, or install on a different machine.
- Check the total system RAM
- Check the appserver heap setting in
/owareapps/installprops/lib/
installed.properties
. If it exceeds the total system RAM either you must allocate
more RAM or reduce the appserver setting
Application server should never be allocated less than 3G ram, and Web server should never
be allocated less than1G RAM.
• The following socket errors (or similar) are reported when starting the application.
(Feb 14, 2014 4:57:50 PM) [OWProcessMonitor] ERROR! command socket
failure: Address already in use: Cannot bind
(Feb 14, 2014 4:57:50 PM) [OWProcessMonitor] re-initializing command
socket: attempt 1 of 10
This indicates a port conflict is likely preventing your system from functioning properly. This
typically occurs when network management or other applications reside on the same server.
Determine the source of the port conflict and remove the application. Best practice is to
install on a dedicated server platform.
• Port Conflicts, as described in the previous paragraph, can arise after installation. For example
if you install other software that uses the SNMP ports (161 and 162), after you have installed
OpenManage Network Manager, the installation cannot catch such a conflict. When you try
to start it, application server will report it cannot bind to that port, and fail. See
Ports Used on
page 1021 for a list of potential conflicts. The
server.log file lists to such errors when they
occur.
• Confirm your license is current and installed. Search the
\oware\jboss-
5.1\server\oware\log\server.log
file for error , and the license expired error
appears.
To install a license file without a running application server, run the
licenseimporter
script:
licenseimporter license.xml
Your license may have a different name, but the script syntax is the same.
Permission issues caused by license
You receive the "You do not have a permission to view this application" message, it most likely
means that you have an expired feature license.
Solution:
For Virtual Appliance: