discovery_server not starting

Article Id: 193704
Status: Published
Updated On: 23-06-2020 17:45
Products:
CA Unified Infrastructure Management On-Premise (Nimsoft / UIM) , NIMSOFT PROBES , DX Infrastructure Management
Issue/Introduction:

Recently we had a situation where we were locked out from our DB server and data_engine was not able to connect to the DB. With the help of our DBA we were able to identify that discovery_server was sending the wrong connection string and due to the number of failed attempts we were locked out. Now the password was reset and the data_engine is again able to connect to the DB but discovery_server still fails.

Environment:

Release : 9.2.0

Component : UIM - DISCOVERY_SERVER

Resolution:

Increase the java min/max memory settings:

to these values:

<startup>
   <opt>
      java_opts = -server -XX:ErrorFile=./hs_err_pid.log
      java_mem_max = -Xmx4096m
      java_mem_init = -Xms2048m
   </opt>
</startup>

Also please make sure that the discovery_server.cfg contains the correct NimBUS addresses for the udm_manager and the data_engine, (which should be up and running as well), for example:

<setup>
  ...
   data_engine = /lvxxxxxxxxxx3_domain/lvxxxxxxxxxx3_hub/lvxxxxxxxxxx3/data_engine
  ...
   <udm>
     ...
      udm_manager = /lvxxxxxxxxxx3_domain/lvxxxxxxxxxx3_hub/lvxxxxxxxxxx3/udm_manager
      ...
   </udm>

<setup>

Then do a cold start of the discovery_server (Deactivate-Activate).

Additional Information:

Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: SHUTDOWN is in progress. ClientConnectionId:f5fc4533-0585-424c-8f51-981c42f0ae96
 at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:258)
 at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:256)
 at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:108)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.sendLogon(SQLServerConnection.java:4290)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.logon(SQLServerConnection.java:3157)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.access$100(SQLServerConnection.java:82)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection$LogonCommand.doExecute(SQLServerConnection.java:3121)
 at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:7151)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:2478)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:2026)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:1687)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectInternal(SQLServerConnection.java:1528)
 at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:866)
 at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:569)
 at java.sql.DriverManager.getConnection(DriverManager.java:664)
 at java.sql.DriverManager.getConnection(DriverManager.java:208)
 at org.apache.commons.dbcp2.DriverManagerConnectionFactory.createConnection(DriverManagerConnectionFactory.java:79)
 at org.apache.commons.dbcp2.PoolableConnectionFactory.makeObject(PoolableConnectionFactory.java:256)
 at org.apache.commons.pool2.impl.GenericObjectPool.create(GenericObjectPool.java:868)
 at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:435)
 at org.apache.commons.pool2.impl.GenericObjectPool.borrowObject(GenericObjectPool.java:363)
 at org.apache.commons.dbcp2.PoolingDataSource.getConnection(PoolingDataSource.java:134)
 at org.springframework.jdbc.datasource.DataSourceUtils.doGetConnection(DataSourceUtils.java:111)
 at org.springframework.jdbc.datasource.DataSourceUtils.getConnection(DataSourceUtils.java:77)