Knowledge Doc: pod arcsight-installer-XXXX fusion-arcsight-configuration-service-XXXXXXXXXX-XXXXX 1/2 only one of two pods running

0 Likes

Summary
Only one of the two pods for the fusion-arcsight-configuration-service are running.

Products
ArcSight Transformation Hub

Environment
ArcSight Platform On Premise 22.1 Version

Situation
The output of kubectl get pods -A -owide command shows one of two pods running as below:

arcsight-installer-XXXX fusion-arcsight-configuration-service-XXXXXXXXXX-XXXXX 1/2

After checking the pods logs the below is seen.

2022-06-28 14:30:06.781 INFO 134 --- [ main] liquibase.lockservice : Waiting for changelog lock....
2022-06-28 14:30:16.787 WARN 134 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'liquibase' defined in class path resource [com/mf/arcsight/configuration/config/LiquibaseConfig.class]: Invocation of init method failed; nested exception is liquibase.exception.LockException: Could not acquire change log lock. Currently locked by fusion-arcsight-configuration-service-64f689f87d-bj5bb (172.16.27.129) since 6/16/22 7:22 AM
2022-06-28 14:30:16.787 INFO 134 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown initiated...
2022-06-28 14:30:16.801 INFO 134 --- [ main] com.zaxxer.hikari.HikariDataSource : HikariPool-1 - Shutdown completed.
2022-06-28 14:30:16.804 INFO 134 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2022-06-28 14:30:16.815 INFO 134 --- [ main] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2022-06-28 14:30:16.992 ERROR 134 --- [ main] o.s.boot.SpringApplication : Application run failed

Read Full Knowledge Base Article for Resolution. 



URL Name
KM000011410

Labels:

Support Tips/Knowledge Docs
  • I have similar problem

    Pod intelligence-tenant-control-xxxxxxxxxx-xxxxx is not working
    Error Message :

    migrate-db liquibase.exception.LockException: Could not acquire change log lock.  Currently locked by interset-api (10.12.3.14) since 8/7/23 1:05

    .
    .
    .

    migrate-db INFO  [2023-08-09 07:11:50,944] liquibase.lockservice.StandardLockService: Waiting for changelog lock....
    migrate-db INFO  [2023-08-09 07:11:50,944] liquibase.lockservice.StandardLockService: Waiting for changelog lock....
    migrate-db INFO  [2023-08-09 07:11:50,944] liquibase.lockservice.StandardLockService: Waiting for changelog lock....
    migrate-db INFO  [2023-08-09 07:11:50,944] liquibase.lockservice.StandardLockService: Waiting for changelog lock....



Related
Recommended