<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Issue with version April2018 Patch2 and RIM nodes? in Management &amp; Governance</title>
    <link>https://community.qlik.com/t5/Management-Governance/Issue-with-version-April2018-Patch2-and-RIM-nodes/m-p/1514174#M11922</link>
    <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I want to share an experience I did last days with Qlik Sense April2018.&lt;/P&gt;&lt;P&gt;I have a customer with a central node running Qlik Sense April2018 Patch2 that needed to add a rim node scheduler to his infrastructure.&lt;/P&gt;&lt;P&gt;I installed Qlik Sense April2018 Patch2 to a new server and tryed to add the node from QMC in the cetral node, but I received the well known error on certificate distribution and port 4444.&lt;/P&gt;&lt;P&gt;Indeed the RIM node was not listening on port 4444 as per netstat command, also many information regarding the dispatcher were logged in event viewer.&lt;/P&gt;&lt;P&gt;So following advices, I tryed to repair the installation on RIM node and had to remove the Patch2 before proceeding, after removing and repairing I executed netstat and the port 4444 was listening.&lt;/P&gt;&lt;P&gt;Re-applying Patch2 the port 4444 was again not listening.&lt;/P&gt;&lt;P&gt;So I removed from the RIM node Patch2 and was able to add the new node from central QMC and to distribute certificates and to generate unlock password for the RIM node.&lt;/P&gt;&lt;P&gt;Now the slave scheduler is operational but I am not sure if I can apply Patch2 to it.&lt;/P&gt;&lt;P&gt;Had ever anyone have the same issue?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Nicola&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 29 Nov 2018 11:38:13 GMT</pubDate>
    <dc:creator>npapapicco</dc:creator>
    <dc:date>2018-11-29T11:38:13Z</dc:date>
    <item>
      <title>Issue with version April2018 Patch2 and RIM nodes?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Issue-with-version-April2018-Patch2-and-RIM-nodes/m-p/1514174#M11922</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;I want to share an experience I did last days with Qlik Sense April2018.&lt;/P&gt;&lt;P&gt;I have a customer with a central node running Qlik Sense April2018 Patch2 that needed to add a rim node scheduler to his infrastructure.&lt;/P&gt;&lt;P&gt;I installed Qlik Sense April2018 Patch2 to a new server and tryed to add the node from QMC in the cetral node, but I received the well known error on certificate distribution and port 4444.&lt;/P&gt;&lt;P&gt;Indeed the RIM node was not listening on port 4444 as per netstat command, also many information regarding the dispatcher were logged in event viewer.&lt;/P&gt;&lt;P&gt;So following advices, I tryed to repair the installation on RIM node and had to remove the Patch2 before proceeding, after removing and repairing I executed netstat and the port 4444 was listening.&lt;/P&gt;&lt;P&gt;Re-applying Patch2 the port 4444 was again not listening.&lt;/P&gt;&lt;P&gt;So I removed from the RIM node Patch2 and was able to add the new node from central QMC and to distribute certificates and to generate unlock password for the RIM node.&lt;/P&gt;&lt;P&gt;Now the slave scheduler is operational but I am not sure if I can apply Patch2 to it.&lt;/P&gt;&lt;P&gt;Had ever anyone have the same issue?&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;Nicola&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 29 Nov 2018 11:38:13 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Issue-with-version-April2018-Patch2-and-RIM-nodes/m-p/1514174#M11922</guid>
      <dc:creator>npapapicco</dc:creator>
      <dc:date>2018-11-29T11:38:13Z</dc:date>
    </item>
    <item>
      <title>Re: Issue with version April2018 Patch2 and RIM nodes?</title>
      <link>https://community.qlik.com/t5/Management-Governance/Issue-with-version-April2018-Patch2-and-RIM-nodes/m-p/1543671#M12531</link>
      <description>&lt;P&gt;Best practice is to have all the Central and RIMs at the same version/patch, but I have never seen that issue to be honest, the only I can think of, the only reason 4444 wasn't listening is because the repository service on that RIM was failing to load up, when you install the RIM, the Logs/repo/trace/system_repo should give a entry that states that it is ready to receive the distributed certificate from central, if it does not get to that message and for some reason it fails or there's a fatal error, it will shut down the repo service and as a result, nothing will listen to port 4444 on that node.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 13 Feb 2019 13:52:18 GMT</pubDate>
      <guid>https://community.qlik.com/t5/Management-Governance/Issue-with-version-April2018-Patch2-and-RIM-nodes/m-p/1543671#M12531</guid>
      <dc:creator>Giuseppe_Novello</dc:creator>
      <dc:date>2019-02-13T13:52:18Z</dc:date>
    </item>
  </channel>
</rss>

