Qlik Community

Security & Governance

Discussion board where members can learn more about Qlik Sense deployments which are governed and self-service.

Announcements
QLIKWORLD LIVE! MAY 16 - 19TH, EARLY BIRD DISCOUNTS! REGISTER TODAY
cancel
Showing results for 
Search instead for 
Did you mean: 
arethaking
Creator II
Creator II

Load balancing is not working on multi node

Hi All,
Before posting, I have searched in google and community.
We are facing a regularly reload issue. We have two nodes. Seems load balancing is not working properly.

Scheduler multi-node is showing status like stop master, stop slave, Not available.

Logs are showing at Message field as below:

A connection attempt failed because the connected party did not properly respond after a period of time,
or established connection failed because connected host has failed to respond 11.22.33.44:4432

An existing connection was forcibly closed by the remote host↵↓Unable to write data to the transport connection:
An existing connection was forcibly closed by the remote host.
↵↓Unable to write data to the transport connection: An existing connection was forcibly closed by the remote host.
↵↓An error occurred while executing the command definition.
See the inner exception for details.↵↓Exception of type 'Repository.Core.Exceptions.TransactionException' was thrown.

An established connection was aborted by the software in your host machine↵
↓Unable to write data to the transport connection: An established connection was aborted by the software in your host machine.

Please advise.

Thanks in advance.

 

 

 

Repository_Log.PNG

Load Balancer Log.PNG

Labels (1)
  • SaaS

1 Reply
Bastien_Laugiero

Hello,

These error messages indicated connectivity issues between the Qlik Sense Scheduler service and the Postgres database. 

You may monitor the stability of the network between the two machines and also look at the Windows Event logs on the Postgres server to see if any Error / Warning are popping up.

Hope this helps!

Bastien Laugiero
If a post helps to resolve your issue, please mark the appropriate replies as CORRECT.