How to make sure port 4432 is listening as it's used to connect to repository database.

[Henriko]

Hi,

I'm trying to configure a RIM node.  On the central node, the port 4432 is not  Listening, meaning the connectivity between RIM and Central node is failing. 

Could you please let me know how I can make the QLIK app to change the port status on the central node? 

Thank you in advance for your help,

Best Regards,

Henri.

[rohitk1609]

If there is connectivity problem, test it with telnet. 

Is it a fresh installation of RIM node?

[Benoit_C]

Hi @Henriko,

From the central node you can check the port with a netstat -ano | find "4432"

For ports checking you can use below article:

https://community.qlik.com/t5/Knowledge/How-to-check-which-program-is-using-a-specific-port/ta-p/171...

[Henriko]

Yes, it's a fresh new install of a Rim node.

Telnet is not working on port 4432, but it's working well on other ports. 

so it's not a general connectivity issue between the two servers.

On the node itself, telnet to the node ip address on port 4432 is not working neither. 

But telnet on the host name is working fine. Really weird.

Should the port be in listening state to allow the connectivity? 

[rohitk1609]

Yes, port listen should work, which confirms that port is open.

[Henriko]

Hi Benoit,

Only the local host is establishing connection on port 4432

I guess I should also have the local server ip address. Is this something generated by the QLIK app? Something wrongly configured on the node server? 

[Benoit_C · Accepted solution]

Hi @Henriko,
 

This result is interesting. It means that your Repository Database is only listening with localhost (127.0.0.1).

It's most probably because the postgresql.conf is incorrect.

See this article:
https://community.qlik.com/t5/Knowledge/PostgreSQL-postgresql-conf-and-pg-hba-conf-explained/ta-p/17...
 

I guess in listen_addresses field, you are having something like:
listen_addresses = 'localhost'

[Henriko]

Hi Benoit,

Thank you very much for your help, this really looks like exactly what I was looking for! 

I'll test this tomorrow afternoon, as I'll have to restart the service and this is a production server. 

I'll let you know the result!

Btw, listen_address was just commented, not sure why the localhost was listening, but anyway, this was not correctly configured. 

[Benoit_C]

Hi @Henriko,

Perfect, please confirm if it was the solution.

Thank you,
Benoit

[Henriko]

Hi Benoit,

It is well solved now, 

Thanks again for your great help, really appreciated! 

Have a nice week-end,

Cheers,

Henri.