Problem Hash Verification failed
In cdh5.8.2 web interface cluster installation process, Parcels hash check failed.
2. Solution 1(Hoodwink)
1. Modify the hash value of manifest.JSON
[root @ hadoop – 01 parcels] # cat CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel. Sha
227d11e344698c70e654ca6768fc017735b73ae3
[root @ hadoop – 01 parcels] # sha1sum CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel
cb7c70d07e68a256a1cb3b06e79e688ac64f3432 CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel
[root @ hadoop – 01 parcels] # cat manifest. Json | grep CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel
“ParcelName” : “CDH – 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel”,
[root @ hadoop – 01 parcels] # vi manifest. The json
# by/into the search mode, the input CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel,
the hash from 227 d11e344698c70e654ca6768fc017735b73ae3 instead of cb7c70d07e68a256a1cb3b06e79e688ac64f3432
2. In the Web interface, click Back, and then click Continue
Iii. Solution 2(Root cause)
If solution 1 , still can’t solve, may parcel file damage.
so you need to download, then web interface don’t shut down, click Back , click Continue .
Delete the local CDH-5.8.2-1.CDH5.8.2.p0.3-el6.Parcel file
[root @ hadoop – 01 parcels] # rm -f CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel
2. Redownload
[root @ hadoop – 01 parcels] # wget HTTP:// http://archive.cloudera.com/cdh5/parcels/5.8.2/CDH-5.8.2-1.cdh5.8.2.p0.3-el6.parcel
3. Check the hash value again for comparison
[root @ hadoop – 01 parcels] # sha1sum CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel
227 d11e344698c70e654ca6768fc017735b73ae3 CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel
[root @ hadoop – 01 parcels] #
[root @ hadoop – 01 parcels] # cat CDH 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel. Sha
227d11e344698c70e654ca6768fc017735b73ae3
### # consistent, that means the download file is complete, not damaged
4. In the Web interface, click Back and then click Continue to find the error
ERROR:
?The Src file/opt/cloudera/parcels/flood/CDH – 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel/CDH – 5.8.2-1. Cdh5.8.2. P0.3 – el6. Parcel does not exist – hadoop – 01… and 4 others
5. In the Web interface, click Back quickly and decisively
6. To each machine manually delete the folder/opt/cloudera/parcels /. Flood and restart the agent
[root@hadoop-01 ~]# rm -rf /opt/cloudera/parcels/.flood
[root@hadoop-02 ~]# rm -rf /opt/cloudera/parcels/.flood
[root@hadoop-03 ~]# rm -rf /opt/cloudera/parcels/.flood
[root@hadoop-04 ~]# rm -rf /opt/cloudera/parcels/.flood
[root@hadoop-05 ~]# rm -rf /opt/cloudera/parcels/.flood
[root@hadoop-06 ~]# rm -rf /opt/cloudera/parcels/.flood
[root@hadoop-01 ~]# service cloudera-scm-agent restart
[root@hadoop-02 ~]# service cloudera-scm-agent restart
[root@hadoop-03 ~]# service cloudera-scm-agent restart
[root@hadoop-04 ~]# service cloudera-scm-agent restart
[root@hadoop-05 ~]# service cloudera-scm-agent restart
[root-Hadoop-06 ~]# Service Cloudera-SCM-Agent Restart
7. In the Web interface, click Continue again and find the following error
?Untar failed with return code: 2, with tar output: stdout: [], stderr: [ gzip: stdin: invalid compressed data–crc error tar: Child returned status 1 tar: Error is not recoverable: No coinages now] -Hadoop-04
8. Google, cloudera community search, unable to resolve
9. Perform step 6 again
Close the current page, open http://172.16.101.54:7180
11. Click Add Cloudera Management Service to create CMS Service
12. Click Add Cluster, create Cluster, failed, cannot click Continue, should be a bug
13. Force uninstall and clean the cluster’s files and install packages
14. Reinstall, the interface is as follows
Iv. Lessons learned:
A. Verify downloaded files
B When Hash Verification failed occurs, do not do solution 1, go to Solution 2 step 1-3, then click back and continue button
C. Simply follow steps 13-14 of Solution 2
5. Note
Encounter the problem, fight it, exhaust methods, improve yourself, start again.
From “ITPUB blog” link: http://blog.itpub.net/30089851/viewspace-2128607/, if you want to reprint, please indicate the source, otherwise will be investigated for legal responsibility.
Reproduced in: http://blog.itpub.net/30089851/viewspace-2128607/
Read More:
- CDH opens Kerberos and reports an error: ticket expired
- Failed to find target with hash string ‘android-25’ in:D:\SDK
- Failed to find target with hash string”android-21″ in:D:\AndroidVersionSdk
- CDH Namenode Abnormal stop Error: flush failed for required journal (JournalAndStream(mgr=QJM to
- Completely solve install_ FAILED_ UPDATE_ Incompatible installation error, the installation package is not consistent with the previous installation package signature on the device
- Android Error | Failed to find target with hash string ”android-23′ in…
- Android Studio | Failed to find target with hash string ‘android-26’ in: D:\Android\sdk
- AS error: failed to find target with hash string’Google Inc.:Google APIs:21′ error solution
- MySQL installation error. Netframeword installation failed
- Hash conflict and four solutions
- Solve host key verification failed [valid]
- Forbidden (403) CSRF verification failed. Request aborted. – Django
- CSRF verification failed. Request aborted.
- Verification of your TeamViewer version failed
- Android studio installation virtual machine error ® HAXM installation failed.
- 【Oracle】IMP-00010: not a valid export file, header failed verification
- Get synchronization retrieved hash chain is invalid error
- python root:code for Hash MD5 was not found. Error
- server certificate verification failed. CAfile: /etc/ssl/certs/ca-certificates.crt CRLfile: none
- Host key verification failed. fatal: Could not read from remote repository.