Problem with FortiClient HA with Postgres Bitna mi Docker

[RahimovaN]

Hello, I wanted to install FortiClient EMS HA with Bitna mi Docker architecture with FortiClient EMS 7.4.4 image. For this, I used the official Postgres and FortiClient latest version packages. However, despite several attempts, EMS does not start with HA. I used the official documentation during the installation. Thanks in advance for your support.

he gets nodes
EMS Node(s):
Name | Role | Status | Last Seen
--------------------------------------------------+---------+---------+----------------------------
ems-1 (*) | primary | online | 2025-10-18 18:14:07.562784

DB Node(s):
Host | Port | Role | Status | Latency (MS)

.. .. .. .. | | standby | offline | 40
.. .. .. .. | 5432 | standby | offline | 41

 

[Anthony_E]

Hello,

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible.

Thanks,

[RahimovaN]

Hello,

Are there any changes in process?

[AEK]

Hi Rahim

You are probably hitting one of the below known issues.

1205131	PostgreSQL database failover causes EMS server failover.
1208343	In a setup of EMS HA with Postgres HA, the secondary EMS node appears offline after a failover process of Postgres DB.

Ref: https://docs.fortinet.com/document/forticlient/7.4.4/ems-release-notes/34950/new-known-issues

[RahimovaN]

Yes, it looks like my problem. Is there any solution for this problem?

[AEK]

I don't see a workaround in the release notes. You probably need to open a ticket.

Meanwhile if the issue doesn't impact your production then you can leave it as is until TAC fixes the issue or a new fix is released.

Otherwise if it it actually has a bad impact on your production then I'd eliminate the HA for now until TAC fixes the issue or a new fix is released.