When the onap system is restarted, if the SO-DB restart is triggered during the SO boot process. This will cause the MSOCockpit-1.2.0-SNAPSHOT.war war package in SO to fail to connect to the SO-DB during deployment. Although it seems that the SO state is normal, it is actually not working.

The system cannot be automatically restored. You need to manually restart the SO to recover.

 

The exception information is as follows:

oot@dev-so-669db6cfbc-rv547:/opt/jboss/standalone/deployments# cat MSOCockpit-1.2.0-SNAPSHOT.war.failed {    "WFLYCTL0080: Failed services" =>

{"jboss.undertow.deployment.default-server.default-host./camunda" => "org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./camunda: java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processEngine': FactoryBean threw exception on object creation; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ProcessEngine    Caused by: java.lang.RuntimeException: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processEngine': FactoryBean threw exception on object creation; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ProcessEngine    Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'processEngine': FactoryBean threw exception on object creation; nested exception is org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ProcessEngine    Caused by: org.springframework.transaction.CannotCreateTransactionException: Could not open JDBC Connection for transaction; nested exception is java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ProcessEngine    Caused by: java.sql.SQLException: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ProcessEngine    Caused by: javax.resource.ResourceException: IJ000453: Unable to get managed connection for java:jboss/datasources/ProcessEngine    Caused by: javax.resource.ResourceException: IJ031084: Unable to create connection    Caused by: java.sql.SQLNonTransientConnectionException: Could not connect to address=(host=so-db)(port=3306)(type=master) : connect timed out    Caused by: org.mariadb.jdbc.internal.util.dao.QueryException: Could not connect to address=(host=so-db)(port=3306)(type=master) : connect timed out    Caused by: java.net.SocketTimeoutException: connect timed out"}

,    "WFLYCTL0412: Required services that are not installed:" => ["jboss.undertow.deployment.default-server.default-host./camunda"],    "WFLYCTL0180: Services with missing/unavailable dependencies" => undefined