Support Questions
Find answers, ask questions, and share your expertise

Testing the JVM's JCE policy to see it if supports an unlimited key length looping process during HDP installation

New Contributor

Hello,

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.

Ambari agent log its as follows:

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.

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

ERROR: Exiting with exit code 1. REASON: Downloading or installing JDK failed: 'Fatal exception: Failed to download JDK: <urlopen error [Errno -2] Name or service not known>. Please check that the JDK is available at http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz. Also you may specify JDK file location in local filesystem using --jdk-location command line argument., exit code 1'. Exiting.

What could be the problem? It's first time that this happen to me.

I' ll tried to donwload http://public-repo-1.hortonworks.com/ARTIFACTS/jdk-8u112-linux-x64.tar.gz tar manually decompressing it and use that resultant jre route in Custom JDK option instead existing openjdk

Thank you in advance.

1 ACCEPTED SOLUTION

Explorer

Hi, @Emilio Lopez,

The agent log looks OK, it's sending hearbeats with different "id" each time.

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.

View solution in original post

1 REPLY 1

Explorer

Hi, @Emilio Lopez,

The agent log looks OK, it's sending hearbeats with different "id" each time.

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.

; ;