UIM automated_deployment_engine is either not starting or restarting
Article ID: 190146
Updated On:
Products
DX Unified Infrastructure Management (Nimsoft / UIM)
Issue/Introduction
The automated_deployment_engine keeps restarting, crashes with a red status icon, or fails to fully activate obtaining a PID but not a port.
Environment
Release : 8.x, 9.x, 20.x
Component : UIM - ADE
Cause
automated_deployment_engine is unable to connect to its local database.
Resolution
Scenario 1
1 deactivate automated_deployment_engine
2 rename $\Nimsoft\probes\service\automated_deployment_engine\automated_deployment_engine.h2.db
3 if present delete automated_deployment_engine.lock.db
the .lock.db is only supposed to exist when the probe is activated
4 activate automated_deployment_engine and it will automatically create a new h2.db.
Scenario 2
It is necessary to discover what is blocking access to the port.
As a test deactivate ppm and automated_deployment_engine
activate automated_deployment_engine
after it has a port and pid activate ppm to see if it can get a port
Scenario 3
1 deactivate automated_deployment_engine
2 rename the probe folder $\Nimsoft\probes\service\automated_deployment_engine
3 deploy automated_deployment_engine via Admin Console
1 deactivate automated_deployment_engine
2 rename $\Nimsoft\probes\service\automated_deployment_engine\automated_deployment_engine.h2.db
3 if present delete automated_deployment_engine.lock.db
the .lock.db is only supposed to exist when the probe is activated
4 activate automated_deployment_engine and it will automatically create a new h2.db.
Scenario 2
It is necessary to discover what is blocking access to the port.
As a test deactivate ppm and automated_deployment_engine
activate automated_deployment_engine
after it has a port and pid activate ppm to see if it can get a port
Scenario 3
1 deactivate automated_deployment_engine
2 rename the probe folder $\Nimsoft\probes\service\automated_deployment_engine
3 deploy automated_deployment_engine via Admin Console
Additional Information
Scenario 1 log sample:
05052020 12:34:42,619 [main] FATAL AutomatedDeploymentEngineProbe - Fatal Error during initialization:
com.nimsoft.nimdbprovider.base.exception.NimDBProviderBaseException: Encryption error in file "C:/Program Files (x86)/Nimsoft/probes/service/automated_deployment_engine/automated_deployment_engine.h2.db" [90049-171]
Scenario 2 log sample:
05052020 20:07:14,715 [main] ERROR NimDBProviderBase - Exception occurs in createConnection: Exception opening port "H2 TCP Server (tcp://<secondary hub IP>:55310)" (port may be in use), cause: "timeout; please check your network configuration, specially the file /etc/hosts" [90061-171]
org.h2.jdbc.JdbcSQLException: Exception opening port "H2 TCP Server (tcp://<secondary hub IP>:55310)" (port may be in use), cause: "timeout; please check your network configuration, specially the file /etc/hosts" [90061-171]
Scenario 3 log sample:
05082020 10:36:35,321 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to INFO. NimLogLevel=3
05082020 10:37:08,193 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to INFO. NimLogLevel=3
05082020 10:38:02,902 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to TRACE. NimLogLevel=5
05082020 10:38:31,674 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to TRACE. NimLogLevel=5
05082020 10:39:00,749 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to TRACE. NimLogLevel=5
Note that in this case even when activating the log fails to show the startup sequence.
automated_deployment_engine.h2.db contains the deployment history of robots deployed via USM and probes via Admin Console.
For windows netstat or the Micorsoft tool
05052020 12:34:42,619 [main] FATAL AutomatedDeploymentEngineProbe - Fatal Error during initialization:
com.nimsoft.nimdbprovider.base.exception.NimDBProviderBaseException: Encryption error in file "C:/Program Files (x86)/Nimsoft/probes/service/automated_deployment_engine/automated_deployment_engine.h2.db" [90049-171]
Scenario 2 log sample:
05052020 20:07:14,715 [main] ERROR NimDBProviderBase - Exception occurs in createConnection: Exception opening port "H2 TCP Server (tcp://<secondary hub IP>:55310)" (port may be in use), cause: "timeout; please check your network configuration, specially the file /etc/hosts" [90061-171]
org.h2.jdbc.JdbcSQLException: Exception opening port "H2 TCP Server (tcp://<secondary hub IP>:55310)" (port may be in use), cause: "timeout; please check your network configuration, specially the file /etc/hosts" [90061-171]
Scenario 3 log sample:
05082020 10:36:35,321 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to INFO. NimLogLevel=3
05082020 10:37:08,193 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to INFO. NimLogLevel=3
05082020 10:38:02,902 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to TRACE. NimLogLevel=5
05082020 10:38:31,674 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to TRACE. NimLogLevel=5
05082020 10:39:00,749 [main] INFO AutomatedDeploymentEngineProbe - log4j: log level set to TRACE. NimLogLevel=5
Note that in this case even when activating the log fails to show the startup sequence.
automated_deployment_engine.h2.db contains the deployment history of robots deployed via USM and probes via Admin Console.
For windows netstat or the Micorsoft tool
Feedback
Yes
No
Powered by
