QlikSense 2.1.1 installation - Slave node not working

[kp_qliktech]

Hi ,

We are setting up our QlikSense production environment with a multimode set up.

1 Central and 5 slaves (1 engine, 1 scheduler, 3 proxies)

While my central node is all up and running, when I install the Engine/Scheduler/Proxy services as Slave during my installation in the server the ports only ports default ports 4444,4432 are not coming up other default ports are not showing 4242,4241 etc.

all m/cs are of same configuration except for the proxies are on VMs.

Can you help on what is causing the issues, Any quick help will be much appreciated.

Thanks

KP

[Levi_Turner]

In the QMC, when you add the RIM node, what occurs? Is the status never contacted? Services not running? Are you able to get to the point of distributing certs to the RIM node(s)?

[kp_qliktech]

Hi Levi,

Yes, after adding the RIM node I get status never contacted issue. I can add the RIM node successfully the certifificate unlock process is successful and  All Services are running fine.

But the status says "Unknown ;never contacted".

In the Proxy node repository log

Proxy Node log is showing the following error

816 2.1.1.0 20151028T081042.946+0000 ERROR TUS3QLSWEBPIN03 05938f53-eae8-4a8d-8603-fbf5b2c269f6 Command=Open connection;Result=-2146233079;ResultText=Error: Unable to connect to the remote server 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available Not available Open connection -2146233079 Web exception when contacting service uri https://localhost:4242/ 05938f53-eae8-4a8d-8603-fbf5b2c269f6

817 2.1.1.0 20151028T081042.946+0000 ERROR TUS3QLSWEBPIN03 74bd6f17-a8d1-4958-ad77-3575075df444 Command=Configure proxy;Result=-2146233079;ResultText=Error: Unable to connect to the remote server 0 0 0 INTERNAL sa_proxy 0 Not available Proxy Not available Not available Configure proxy -2146233079 Could not contact local repository to retrieve proxy service settings 74bd6f17-a8d1-4958-ad77-3575075df444

[#4]

Did you find a resolution for this?

[danieldias]

Did you find a resolution for this?

[danieldias]

Solved

There was a NAT between the servers and the connection was being blocked.

For this reason the service did not start.