DX Unified Infrastructure Management

 View Only
  • 1.  20.4 Upgrade failed - sla_engine does want to start

    Posted Jan 17, 2022 08:10 AM
    Went from 20.3 t0 20.4 today and now our sla_engine does not start. From the logs below looks like it wants a secure connection (I guess SSL) to SQL. Is there a way to fix this?

    ene 17 12:54:14:400 [main, sla_engine] Starting [SLA Engine] version [20.40 build number 44]
    ene 17 12:54:14:400 [main, sla_engine] Initilizing Probe sla_engine
    ene 17 12:54:14:403 [main, sla_engine] Doing Setting Operations for sla_engine
    ene 17 12:54:14:403 [main, sla_engine] Doing Setting operation on the probe
    ene 17 12:54:14:404 [main, sla_engine] Configuration file has been loaded:sla_engine.cfg
    ene 17 12:54:14:413 [main, sla_engine] DBInfoProvider getInstance
    ene 17 12:54:14:413 [main, sla_engine] new DBInfoProvider()
    ene 17 12:54:14:413 [main, sla_engine] DBInfoProvider setProviderName
    ene 17 12:54:14:414 [main, sla_engine] De Address /AIS_SPAIN_DOMAIN/AIS_SPAIN_HUB/cncsnimbushub/data_engine
    ene 17 12:54:14:419 [main, sla_engine] Request to probe "/AIS_SPAIN_DOMAIN/AIS_SPAIN_HUB/cncsnimbushub/data_engine" callback get_connection_string was successful.
    ene 17 12:54:14:755 [main, sla_engine] In FileUtils.getFileChecksum
    ene 17 12:54:14:755 [main, sla_engine] local certificate store FileChecksum - b77bead942f994421a1de5baccdffb0c
    ene 17 12:54:14:761 [main, sla_engine] Resulting parsed connection data is: DatabaseConnectionInfo [databaseName=CA_UIM, databaseServer=10.219.35.18, dbProvider=SQLOLEDB, nisJdbcUsername=ANSAdmin, nisJdbcPassword={not_shown_for_security_reasons}, nisJdbcUrl=jdbc:sqlserver://;serverName=10.219.35.18;databaseName=CA_UIM;applicationName=sla_engine;Network Library=dbmssocn;Language=us_english]
    ene 17 12:54:14:762 [main, sla_engine] ConnectionString from dataengine was successful
    ene 17 12:54:14:762 [main, sla_engine] Connection string retrieved successfully from data_engine
    ene 17 12:54:14:762 [main, sla_engine] Got Provider Name SQLOLEDB
    ene 17 12:54:14:762 [main, sla_engine] probe.checkDatabaseConnection
    ene 17 12:54:14:763 [main, sla_engine] new DataAccessLayerProvider()
    ene 17 12:54:14:763 [main, sla_engine] Class name selected as db provider is com.nimsoft.nimbus.probe.service.slaengine.dal.mssql.DataAccessLayer
    ene 17 12:54:14:765 [main, sla_engine] MSSQLDBProvider.getInstance()
    ene 17 12:54:14:765 [main, sla_engine] MSSQLDBProvider getInstance()
    ene 17 12:54:14:766 [main, sla_engine] String getConnString()
    ene 17 12:54:14:770 [main, sla_engine] Request to probe "/AIS_SPAIN_DOMAIN/AIS_SPAIN_HUB/cncsnimbushub/data_engine" callback get_connection_string was successful.
    ene 17 12:54:16:426 [main, sla_engine] In FileUtils.getFileChecksum
    ene 17 12:54:16:426 [main, sla_engine] local certificate store FileChecksum - b77bead942f994421a1de5baccdffb0c
    ene 17 12:54:16:427 [main, sla_engine] Resulting parsed connection data is: DatabaseConnectionInfo [databaseName=CA_UIM, databaseServer=10.219.35.18, dbProvider=SQLOLEDB, nisJdbcUsername=ANSAdmin, nisJdbcPassword={not_shown_for_security_reasons}, nisJdbcUrl=jdbc:sqlserver://;serverName=10.219.35.18;databaseName=CA_UIM;applicationName=sla_engine;Network Library=dbmssocn;Language=us_english]
    ene 17 12:54:16:427 [main, sla_engine] Connection string retrieved successfully from data_engine
    ene 17 12:54:16:732 [main, sla_engine] Exception occurs in createConnection com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "No appropriate protocol (protocol is disabled or cipher suites are inappropriate)". Trace: com.microsoft.sqlserver.jdbc.SQLServerException: The driver could not establish a secure connection to SQL Server by using Secure Sockets Layer (SSL) encryption. Error: "No appropriate protocol (protocol is disabled or cipher suites are inappropriate)".
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.terminate(SQLServerConnection.java:1368)
    at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1412)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connectHelper(SQLServerConnection.java:1058)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.login(SQLServerConnection.java:833)
    at com.microsoft.sqlserver.jdbc.SQLServerConnection.connect(SQLServerConnection.java:716)
    at com.microsoft.sqlserver.jdbc.SQLServerDriver.connect(SQLServerDriver.java:841)
    at java.sql.DriverManager.getConnection(DriverManager.java:664)
    at java.sql.DriverManager.getConnection(DriverManager.java:247)
    at com.nimsoft.nimbus.probe.service.slaengine.dal.mssql.MSSQLDBProvider.createConnection(MSSQLDBProvider.java:104)
    at com.nimsoft.nimbus.probe.service.slaengine.dal.mssql.MSSQLDBProvider.<init>(MSSQLDBProvider.java:83)
    at com.nimsoft.nimbus.probe.service.slaengine.dal.mssql.MSSQLDBProvider.getInstance(MSSQLDBProvider.java:64)
    at com.nimsoft.nimbus.probe.service.slaengine.dal.mssql.DataAccessLayer.<init>(DataAccessLayer.java:28)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
    at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
    at java.lang.Class.newInstance(Class.java:442)
    at com.nimsoft.nimbus.probe.service.slaengine.dal.DataAccessLayerProvider.<init>(DataAccessLayerProvider.java:65)
    at com.nimsoft.nimbus.probe.service.slaengine.dal.DataAccessLayerProvider.getInstance(DataAccessLayerProvider.java:40)
    at com.nimsoft.nimbus.probe.service.slaengine.Probe.checkDatabaseConnection(Probe.java:445)
    at com.nimsoft.nimbus.probe.service.slaengine.Probe.probeSettings(Probe.java:376)
    at com.nimsoft.nimbus.probe.service.slaengine.SLAEngine.main(SLAEngine.java:169)
    Caused by: javax.net.ssl.SSLHandshakeException: No appropriate protocol (protocol is disabled or cipher suites are inappropriate)
    at sun.security.ssl.HandshakeContext.<init>(HandshakeContext.java:171)
    at sun.security.ssl.ClientHandshakeContext.<init>(ClientHandshakeContext.java:103)
    at sun.security.ssl.TransportContext.kickstart(TransportContext.java:220)
    at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:428)
    at com.microsoft.sqlserver.jdbc.TDSChannel.enableSSL(IOBuffer.java:1379)


  • 2.  RE: 20.4 Upgrade failed - sla_engine does want to start

    Posted Jan 17, 2022 10:08 AM
    Going to upgrade SQL 2014 to SP3 as per https://knowledge.broadcom.com/external/article?articleId=231416


  • 3.  RE: 20.4 Upgrade failed - sla_engine does want to start

    Posted Jan 17, 2022 01:14 PM
    delete the sla_engine probe from IM. Then delete the sla_engine directory. Then redeploy the sla_engine package. Then it should start and run. There's apparently a file that exists that gets in the way of a correct install and needs to be manually addressed. There's a KB on it if you search.


  • 4.  RE: 20.4 Upgrade failed - sla_engine does want to start

    Posted Jan 17, 2022 01:19 PM
    Thanks Garin. Worked like a treat. BTW: SQL 2014 SP3 with CU4 made no difference


  • 5.  RE: 20.4 Upgrade failed - sla_engine does want to start

    Posted Jan 19, 2022 04:39 AM

    Found article for update from 8.x to 9.x which says the same:
    https://knowledge.broadcom.com/external/article/113003/sla_engine-probe-not-starting-after-the.html

    But yeah, it also worked out for our environment.