The UMP Web-page/portal does not load

Document ID : KB000074913
Last Modified Date : 28/03/2018
Show Technical Document Details
Issue:
Let us discuss few common causes why the UMP Web-page/portal does not load
Cause:
There could be many causes for the issue to happen, we will be discussing few common causes in this document
Resolution:
  • First things first, check if the wasp (stands for Web Application Server Probe) on the UMP Box is running, if it is running, from the Admin Console, you should see the Green indicator with Port and PID Numbers associated with the wasp (to find out on how to login to Admin Console, please click here):
User-added image
  • If wasp is in error state as below:
User-added image
  • Or shows invalid security, login to Infrastructure Manager, select wasp on UMP robot, right-click the probe and select Security > Validate (to find out on how to login to Infrastructure Manager, please click here):
User-added image 
  • If wasp is in deactivate state as below, activate it (to find out how to activate the wasp probe, please click here):
User-added image
  • If you see the below error message in the web-browser when you try logging in to the UMP Console:
User-added image 
  • (or) you see “Failed to retrieve information about robot …” error message like below when you select the UMP robot from the Admin Console, most likely the cause is firewall blocking the communication on the UMP Box, you would need to work with your Systems Administrator to allow firewall access (to find out information on Firewall ports, please click here):
User-added image
  • If the wasp has Port and PID numbers associated with it as below, enable the wasp debugging (to find out on how to enable debugging and read the log files, please click here):
User-added image 
  • If the wasp debug log file reads the below message, there is port conflict, you would need to check this internally which application is running on the same wasp port.
In the below example wasp is configured to run on port 8080 also being used by another application simultaneously on the UMP Robot:
Caused by: java.net.BindException: Address already in use: JVM_Bind <null>:8080
               at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:413)
               at org.apache.tomcat.util.net.AbstractEndpoint.init(AbstractEndpoint.java:650)
               at org.apache.coyote.AbstractProtocol.init(AbstractProtocol.java:452)
               at org.apache.coyote.http11.AbstractHttp11JsseProtocol.init(AbstractHttp11JsseProtocol.java:119)
               at org.apache.catalina.connector.Connector.initInternal(Connector.java:978)
               ... 9 more
Caused by: java.net.BindException: Address already in use: JVM_Bind
               at java.net.DualStackPlainSocketImpl.bind0(Native Method)
               at java.net.DualStackPlainSocketImpl.socketBind(DualStackPlainSocketImpl.java:106)
               at java.net.AbstractPlainSocketImpl.bind(AbstractPlainSocketImpl.java:387)
               at java.net.PlainSocketImpl.bind(PlainSocketImpl.java:190)
               at java.net.ServerSocket.bind(ServerSocket.java:375)
               at java.net.ServerSocket.<init>(ServerSocket.java:237)
               at java.net.ServerSocket.<init>(ServerSocket.java:181)
               at org.apache.tomcat.util.net.DefaultServerSocketFactory.createSocket(DefaultServerSocketFactory.java:49)
               at org.apache.tomcat.util.net.JIoEndpoint.bind(JIoEndpoint.java:400)
               ... 13 more
  • If you observe error message(s) in the wasp debug log other than above, try searching with the error message(s) in CA UIM knowledge base available at CA Support by clicking here
  • If the wasp for some reason does not pick the port number as shown below and the wasp debugging does not return error, the issue could be due to some other reason:
User-added image 
  • One of the causes could be the data_engine probe has gone in the error state as below (or) is running into issues:User-added image
  • Try validating the probe as mentioned previously in the document
  • If the data_engine probe is in deactivated state, activate it as mentioned previously in the document
  • If the above does not resolve the issue with the data_engine probe and it continues to be in error state, enable the debugging similar to what is discussed here.
Note, after enabling the data_engine debugging, if you would like to view the log files, the file name would be data_engine.log and on the robot where data_engine probe is installed, assuming the underlying Operating System is Windows, the default path would be C:\Program Files (x86)\Nimsoft\probes\slm\data_engine.
  • If the data_engine debug log file reads the below self-explanatory message, you would need to work with your Database Administrator to increase the size of LOG_BACKUP:
"The transaction log for database 'CA_UIM' is full due to 'LOG_BACKUP'"
  • If you observe error message(s) in the data_engine debug log other than above, try searching the error message in CA UIM knowledge base available at CA Support by clicking here
Additional Information: