A nice quiet evening with the family was interrupted with a critical alert coming through my phone.<\/p>\n\n\n\n
Once again server patching had knocked off our Qlik Replicate node.<\/p>\n\n\n\n
Logging in I could see that Enterprise manager could not reach one of our nodes with the following error message in the log:<\/p>\n\n\n
\n2022-12-15 19:15:40 [ServerDto ] [ERROR] Test connection failed for server:MY_QR_CLUSTER. Message:'Unable to connect to the remote serverA 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 xxx.xxx.xxx.xxx:443'.\n<\/pre><\/div>\n\n\nI have seen this problem before and it is usually resolved by:<\/p>\n\n\n\n
\n- Failing over the QR windows cluster<\/li>\n\n\n\n
- Restarting the new passive node<\/li>\n<\/ol>\n\n\n\n
Our IT team is aware of the problem and have been researching into a cause and a fix. Their prevailing theory was that when the cluster gets failed over in server patching – there are some residual connections to the previous active node.<\/p>\n\n\n\n
But tonight after multiple failovers and stopping and starting the QR roles – still Enterprise manager couldn’t connect to that QR node.<\/p>\n\n\n\n
I did the following checks:<\/p>\n\n\n\n
\n- The log repsrv.log log file had no error messages and the service Web UI service was active<\/li>\n\n\n\n
- From the Enterprise manager; I could ping the QR cluster address and the active node successfully\u00a0<\/li>\n\n\n\n
- From a Chrome session on the Enterprise manager server; I could not get<\/em><\/strong> to the QR Web console<\/li>\n\n\n\n
- From a Chrome session on the QR server; I could get<\/strong><\/em> to the QR Web console<\/li>\n<\/ol>\n\n\n\n
A senior IT member joined the troubleshooting call and suggested that we reboot the Enterprise manager server.<\/p>\n\n\n\n
So we did and then we couldn’t access Enterprise manager console.<\/p>\n\n\n\n
At this point I wanted to quit IT and become a nomad in Mongolia.<\/p>\n\n\n\n
Then the senior IT member worked it out.<\/p>\n\n\n\n
The Windows server was randomly turning on the Windows Firewall<\/em><\/p>\n\n\n\nThis was blocking our inbound connections; making the console inaccessible from other locations – except when you were logged onto the server.<\/p>\n\n\n\n
This also explains why when this problem previously arise; restarting the server will eventually work because the server group policy will eventually get applied and turn off the Windows firewall. <\/p>\n\n\n\n
Lessons learnt<\/h3>\n\n\n\n
If you come above this problem in your environment try accessing the QR console from multiple locations:<\/p>\n\n\n\n
\n- From the Enterprise Manager server<\/li>\n\n\n\n
- From within the QR server with a local address like: https:\/\/localhost\/attunityreplicate\/login\/<\/li>\n<\/ul>\n\n\n\n
Good luck<\/p>\n","protected":false},"excerpt":{"rendered":"
A nice quiet evening with the family was interrupted with a critical alert coming through my phone. Once again server patching had knocked off our Qlik...<\/p>\n","protected":false},"author":1,"featured_media":1076,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[13,16],"tags":[],"class_list":["post-1070","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-code","category-qlik-replicate"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t