Nov 2019: Rim won't join Central Node (HTTP Error 503)

[JustinDallas]

Hello Folks,

I have a 2 node cluster, with 1 central and 1 rim node.   As of now, I see that no work is being distributed to the rim node at all, even though the rim node is visible in the QMC

When I look at the Sense\Log\Repository\System\QLIKSENSE_Service_Repository logs on the Central node, I see the following":

WARN Failed to retrieve service status from 'http://gre-v-qs-02:4444/status/'. Server host 'gre-v-qs-02'. Error message: 'Unable to connect to the remote server

I then tried to redistribute the cert to see if maybe that would kick start something.  In the logs I see the following.

....Cannot reach the following remote host when distributing certificates: http://gre-v-qs-02:4444/setup/certificateDistribution (HTTP code: 400)...

However, I know these errors are all vicious lies, because from the central node, I can access the urls that Qlik claims to be unable to reach.

I've attached my QlikSense Central Node repository log file to this post for completeness.

Any help on getting this rim node back up is greatly appreciated.

[Gencho]

Did you change the name of the server after you installed Qlik Sense? 

The error looks like it's something that it does not allow you to distribute the certificates, what I could try to do is:

• Disable the firewall and open the Qlik ports
• Check if you have any antivirus installed and disable it and redistribute the certificates
• Did you changed the  postgresql.conf file? when I create a cluster depending on the number of nodes in my environment I must change the max_connections = 100 by default is 100, if you have 6 nodes, you have to change for 600. I also change the  listen addresses and I set like this listen_addresses = '*'  and in the pg_hba.conf file I change this:
  host all all 0.0.0.0/0 md5
  host all all ::/0 md5

See the documentation below

https://support.qlik.com/articles/000051668

Let me know if this helps

[JustinDallas · Accepted solution]

I ended up reinstalling from scratch on another VM.  This link here made setting the ports easy as opposed to the other documents which lead to a dangerous patchwork of "off-by-one" errors.

https://support.qlik.com/articles/000007185