[BUG] Postgres communication error

[agauttam]

Describe the bug

2024-05-16 10:59:25.963 WARN 1 --- [pool-3-thread-2] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnection@3a993d1e (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024-05-16 10:59:25.965 WARN 1 --- [pool-3-thread-2] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnection@32a388dc (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024-05-16 10:59:25.967 WARN 1 --- [pool-3-thread-2] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnection@6af0582c (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024-05-16 10:59:25.969 WARN 1 --- [pool-3-thread-2] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnection@21424c5c (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024-05-16 10:59:25.971 WARN 1 --- [pool-3-thread-2] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnection@52c0e4a7 (This connection has been closed.). Possibly consider using a shorter maxLifetime value.
2024-05-16 10:59:25.972 WARN 1 --- [pool-3-thread-2] com.zaxxer.hikari.pool.PoolBase : Hikari - Failed to validate connection org.postgresql.jdbc.PgConnection@7c0b634b (This connection has been closed.). Possibly consider using a shorter maxLifetime value.

Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
Checking elasticsearch connection:
> Success
2024-05-16 11:06:10.461 ERROR 1 --- [ XNIO-1 task-1] c.p.u.w.r.e.ElasticsearchResource : ElasticsearchResource.getFieldValuesWithCount: ElasticsearchService.getFieldValuesWithCount: OpenSearch.getFieldValues: Connection reset by peer
2024-05-16 11:06:10.462 ERROR 1 --- [ XNIO-1 task-1] c.p.utmstack.web.rest.util.HeaderUtil : Entity processing failed, ElasticsearchResource.getFieldValuesWithCount: ElasticsearchService.getFieldValuesWithCount: OpenSearch.getFieldValues: Connection reset by peer
2024-05-16 11:06:10.462 ERROR 1 --- [tack-Executor-2] c.p.u.s.a.ApplicationEventService : ApplicationEventService.createEvent: OpenSearch.index: Connection reset by peer
2024-05-16 11:06:10.466 ERROR 1 --- [ XNIO-1 task-5] c.p.u.w.r.e.ElasticsearchResource : ElasticsearchResource.getFieldValuesWithCount: ElasticsearchService.getFieldValuesWithCount: OpenSearch.getFieldValues: Connection reset by peer
2024-05-16 11:06:10.466 ERROR 1 --- [ XNIO-1 task-5] c.p.utmstack.web.rest.util.HeaderUtil : Entity processing failed, ElasticsearchResource.getFieldValuesWithCount: ElasticsearchService.getFieldValuesWithCount: OpenSearch.getFieldValues: Connection reset by peer
2024-05-16 11:06:10.471 ERROR 1 --- [ XNIO-1 task-5] c.p.u.w.r.e.ElasticsearchResource : ElasticsearchResource.getFieldValuesWithCount: ElasticsearchService.getFieldValuesWithCount: OpenSearch.getFieldValues: Connection reset by peer
2024-05-16 11:06:10.471 ERROR 1 --- [ XNIO-1 task-5] c.p.utmstack.web.rest.util.HeaderUtil : Entity processing failed, ElasticsearchResource.getFieldValuesWithCount: ElasticsearchService.getFieldValuesWithCount: OpenSearch.getFieldValues: Connection reset by peer
Checking elasticsearch connection:

To Reproduce
Its comming from the day 1 when we installed the UTMStack

Environment

• OS: Ubuntu 22.04

[c3s4rfred]

Hi @agauttam those are common errors while the system is starting because docker swarm knows if the container is up, but internal services may be down during the startup. Also can be a network issue, consider to reboot the machine. After a while, the system must work, let us know if it doesn't.
Best regards

[agauttam]

My UTMStack system is freezing for a minute, whenever I am getting these errors.