<?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>question Re: Testing the JVM's JCE policy to see it if supports an unlimited key length looping process during HDP installation in Archives of Support Questions (Read Only)</title>
    <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Testing-the-JVM-s-JCE-policy-to-see-it-if-supports-an/m-p/212893#M74424</link>
    <description>&lt;P&gt;Hi, &lt;A rel="user" href="https://community.cloudera.com/users/66206/emilio1204lopez9.html" nodeid="66206"&gt;@Emilio Lopez&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;The agent log looks OK, it's sending hearbeats with different "id" each time.&lt;/P&gt;&lt;P&gt;Please take a look at the contents of /var/lib/ambari-agent/data -- look for output*txt which contain "Host checks started.", and corresponding error*txt files (eg. output-2.txt and error-2.txt).  Those might have some info about the problem.  Also search for check_host in ambari-agent.log.&lt;/P&gt;</description>
    <pubDate>Tue, 13 Feb 2018 06:39:57 GMT</pubDate>
    <dc:creator>adoroszlai</dc:creator>
    <dc:date>2018-02-13T06:39:57Z</dc:date>
    <item>
      <title>Testing the JVM's JCE policy to see it if supports an unlimited key length looping process during HDP installation</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Testing-the-JVM-s-JCE-policy-to-see-it-if-supports-an/m-p/212892#M74423</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;During Ambari Wizard Confirm Hosts after installation, process remains cheking for potential problems indefinitely doing Testing the JVM's JCE policy to see it if supports an unlimited key length process.&lt;/P&gt;&lt;P&gt;Ambari agent log its as follows:&lt;/P&gt;&lt;PRE&gt;INFO 2018-02-08 14:56:42,677 logger.py:75 - Testing the JVM's JCE policy to see it if supports an unlimited key length. INFO 2018-02-08 14:56:42,941 Hardware.py:176 - Some mount points were ignored: /, /dev, /dev/shm, /run, /sys/fs/cgroup, /boot, /boot/efi, /home, /run/user/1000, /run/user/42 INFO 2018-02-08 14:56:42,942 Controller.py:320 - Sending Heartbeat (id = 158) INFO 2018-02-08 14:56:42,946 Controller.py:333 - Heartbeat response received (id = 159) INFO 2018-02-08 14:56:42,946 Controller.py:342 - Heartbeat interval is 10 seconds INFO 2018-02-08 14:56:42,946 Controller.py:380 - Updating configurations from heartbeat INFO 2018-02-08 14:56:42,946 Controller.py:389 - Adding cancel/execution commands INFO 2018-02-08 14:56:42,947 Controller.py:406 - Adding recovery commands INFO 2018-02-08 14:56:42,947 Controller.py:475 - Waiting 9.9 for next heartbeat INFO 2018-02-08 14:56:52,847 Controller.py:482 - Wait for next heartbeat over INFO 2018-02-08 14:57:52,282 Controller.py:304 - Heartbeat (response id = 165) with server is running... INFO 2018-02-08 14:57:52,282 Controller.py:311 - Building heartbeat message INFO 2018-02-08 14:57:52,284 Heartbeat.py:90 - Adding host info/state to heartbeat message. INFO 2018-02-08 14:57:52,418 logger.py:75 - Testing the JVM's JCE policy to see it if supports an unlimited key length. INFO 2018-02-08 14:57:52,673 Hardware.py:176 - Some mount points were ignored: /, /dev, /dev/shm, /run, /sys/fs/cgroup, /boot, /boot/efi, /home, /run/user/1000, /run/user/42 INFO 2018-02-08 14:57:52,674 Controller.py:320 - Sending Heartbeat (id = 165) INFO 2018-02-08 14:57:52,678 Controller.py:333 - Heartbeat response received (id = 166) INFO 2018-02-08 14:57:52,679 Controller.py:342 - Heartbeat interval is 10 seconds INFO 2018-02-08 14:57:52,679 Controller.py:380 - Updating configurations from heartbeat INFO 2018-02-08 14:57:52,679 Controller.py:389 - Adding cancel/execution commands INFO 2018-02-08 14:57:52,679 Controller.py:406 - Adding recovery commands INFO 2018-02-08 14:57:52,679 Controller.py:475 - Waiting 9.9 for next heartbeat INFO 2018-02-08 14:58:02,580 Controller.py:482 - Wait for next heartbeat over INFO 2018-02-08 14:59:02,013 Controller.py:304 - Heartbeat (response id = 172) with server is running... INFO 2018-02-08 14:59:02,013 Controller.py:311 - Building heartbeat message INFO 2018-02-08 14:59:02,015 Heartbeat.py:90 - Adding host info/state to heartbeat message.&lt;/PRE&gt;&lt;P&gt;During ambari server setup I used openjdk installed instead of using option 1 with Oracle JDK 1.8 because appears error when using first option&lt;/P&gt;&lt;PRE&gt;ERROR: Exiting with exit code 1. REASON: Downloading or installing JDK failed: 'Fatal exception: Failed to download JDK: &amp;lt;urlopen error [Errno -2] Name or service not known&amp;gt;. Please check that the JDK is available at &lt;A href="http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz" target="_blank"&gt;http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz&lt;/A&gt;. Also you may specify JDK file location in local filesystem using --jdk-location command line argument., exit code 1'. Exiting.&lt;/PRE&gt;&lt;P&gt;What could be the problem? It's first time that this happen to me.&lt;/P&gt;&lt;P&gt;I' ll tried to donwload &lt;A href="http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz" target="_blank"&gt;http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz&lt;/A&gt; tar manually decompressing it and use that resultant jre route in Custom JDK option instead existing openjdk&lt;/P&gt;&lt;P&gt;Thank you in advance.&lt;/P&gt;</description>
      <pubDate>Thu, 08 Feb 2018 22:25:48 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Testing-the-JVM-s-JCE-policy-to-see-it-if-supports-an/m-p/212892#M74423</guid>
      <dc:creator>emilio1204lopez</dc:creator>
      <dc:date>2018-02-08T22:25:48Z</dc:date>
    </item>
    <item>
      <title>Re: Testing the JVM's JCE policy to see it if supports an unlimited key length looping process during HDP installation</title>
      <link>https://community.cloudera.com/t5/Archives-of-Support-Questions/Testing-the-JVM-s-JCE-policy-to-see-it-if-supports-an/m-p/212893#M74424</link>
      <description>&lt;P&gt;Hi, &lt;A rel="user" href="https://community.cloudera.com/users/66206/emilio1204lopez9.html" nodeid="66206"&gt;@Emilio Lopez&lt;/A&gt;,&lt;/P&gt;&lt;P&gt;The agent log looks OK, it's sending hearbeats with different "id" each time.&lt;/P&gt;&lt;P&gt;Please take a look at the contents of /var/lib/ambari-agent/data -- look for output*txt which contain "Host checks started.", and corresponding error*txt files (eg. output-2.txt and error-2.txt).  Those might have some info about the problem.  Also search for check_host in ambari-agent.log.&lt;/P&gt;</description>
      <pubDate>Tue, 13 Feb 2018 06:39:57 GMT</pubDate>
      <guid>https://community.cloudera.com/t5/Archives-of-Support-Questions/Testing-the-JVM-s-JCE-policy-to-see-it-if-supports-an/m-p/212893#M74424</guid>
      <dc:creator>adoroszlai</dc:creator>
      <dc:date>2018-02-13T06:39:57Z</dc:date>
    </item>
  </channel>
</rss>

