Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Checksum mismatch Cloudera 6.2.0

Checksum mismatch Cloudera 6.2.0

New Contributor

We tried to establish a Cloudera Cluster, but the installation failed at the stage "Install Agent".
The error was the following:

 

E: Fehlschlag beim Holen von https://archive.cloudera.com/cm6/6.2.0/ubuntu1804/apt/dists/bionic-cm6/contrib/binary-amd64/Packages... Datei hat eine unerwartete Größe (1750 != 1752). Eventuell läuft gerade eine Spiegel-Synchronisierung? [IP: 151.101.12.167 443] 
Hashes of expected file: 
- Filesize:1752 [weak] 
- SHA256:d47dd51a83d1aa02f24cb1e0bee5657552fe3f8c5714d2a0fced4381608aa1e3 
- SHA1:821a5808e4562f64b2df94f6f884f65ea32bfec2 [weak] 
- MD5Sum:6add4908548b4a3f8d2d090002afd1a8 [weak] 
Release file created at: Fri, 05 Jul 2019 15:13:05 +0000

 

So how do we fix this error? We need to establish the Cluster as soon as possible.

11 REPLIES 11

Re: Checksum mismatch Cloudera 6.2.0

New Contributor

I am also having the same issue. Would like to know the resolution asap as setting up a proof of concept machine before starting the production setup.

Re: Checksum mismatch Cloudera 6.2.0

New Contributor

After further investigation we saw that the problem is in the InRelease file.

https://archive.cloudera.com/cm6/6.2.0/ubuntu1804/apt/dists/bionic-cm6.2.0/InRelease

 

MD5Sum:

8434098e03a801bddc6a6be5e22d2ded 1750 contrib/binary-amd64/Packages.gz

 

SHA1:

d10398bded3bae05f630e163b0e6cf7eb7bc392d 1750 contrib/binary-amd64/Packages.gz

 

SHA256:

b2e3a9f9815b5fb5a516200a7ef60da51792690f809f07de5871e4426ff465b5 1750 contrib/binary-amd64/Packages.gz

 

So thats why we get the unexpected size warning.

 

Please fix this asap.

Highlighted

Re: Checksum mismatch Cloudera 6.2.0

Super Guru

@ClouderaUser0and @ClouderaNewbie ,

 

Thanks for bringing this to our attention.  I'll get this to the right people in Cloudera so we can address the issue.

 

-Ben

Re: Checksum mismatch Cloudera 6.2.0

New Contributor

Thank you very much for the acknowledgement. It will be good if the issue is resolved.

 

In the mean time I started the manual installation as sugested for the production server and on the very first step "configure the repository" for Ubuntu I get the error "Ignoring file 'archive.key' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension" as below, It seems the repository doesn't have the correct files for the latest CDM6.2 for Ubuntu v18.04:

 

"/etc/apt/sources.list.d$ sudo apt-get update
Get:1 https://archive.cloudera.com/cm6/6.2.0/ubuntu1804/apt bionic-cm6.2.0 InRelease [2,155 B]
Get:2 https://archive.cloudera.com/cm6/6.2.0/ubuntu1804/apt bionic-cm6.2.0/contrib amd64 Packages [1,752 B]
Hit:3 http://archive.ubuntu.com/ubuntu bionic InRelease
Get:4 http://archive.ubuntu.com/ubuntu bionic-updates InRelease [88.7 kB]
Get:5 http://archive.ubuntu.com/ubuntu bionic-backports InRelease [74.6 kB]
Get:6 http://archive.ubuntu.com/ubuntu bionic-security InRelease [88.7 kB]
Get:7 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages [680 kB]
Get:8 http://archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages [970 kB]
Fetched 1,906 kB in 2s (1,178 kB/s)
Reading package lists... Done
N: Ignoring file 'archive.key' in directory '/etc/apt/sources.list.d/' as it has an invalid filename extension

Re: Checksum mismatch Cloudera 6.2.0

Super Guru

Quick update:

 

Our engineering team is investigating regarding the cause.  The install was fine when we tested, but it seems that something has touched the files recently and we are looking into what that was and why.

 

We'll notify you in this thread of updates as they come.

 

Ben

Re: Checksum mismatch Cloudera 6.2.0

Super Guru

@ClouderaNewbie,

 

"archive.key" shouldn't be in there so I wonder how it got there.

 

Can you try moving it out of the /etc/apt/sources.list.d dir and try the update again?

 

Since the failure during the original Install Wizard method failed when attempting to install the agent package, I would expect the same error to happen during manual install too. 

Re: Checksum mismatch Cloudera 6.2.0

Super Guru

@ClouderaUser0and @ClouderaNewbie ,

 

We believe we have tracked down what happened and we are working to verify and correct it.

A big thanks to you for alerting us to this issue!

 

We don't have an ETA for the fixed bits yet, but we'll post once we do have more info.

Re: Checksum mismatch Cloudera 6.2.0

Super Guru

UPDATE:

 

We believe we have a fix but we want to test to confirm.  We should have further updates on July 10 (U.S. PDT hours)

Re: Checksum mismatch Cloudera 6.2.0

New Contributor

It seems that there is a mistake in Packages(https://archive.cloudera.com/cm6/6.2.0/ubuntu1804/apt/dists/bionic-cm6.2.0/contrib/binary-amd64/Pack...).

File name of deb package is wrong.

 

e.g.: cloudera-manager-daemons package

 

Pacakge:

Package: cloudera-manager-daemons
Source: enterprise
Version: 6.2.0~1243844.ubuntu1804
Architecture: all
Maintainer: Cloudera Inc. <https://issues.cloudera.org>
Installed-Size: 1391555
Depends: perl
Homepage: http://www.cloudera.com
Priority: extra
Section: misc
Filename: pool/contrib/e/enterprise/cloudera-manager-daemons_6.2.0~1243844.ubuntu1804_all.deb
Size: 1223501526
SHA256: e07fc0079ddb180ba1a0d9f7327d7d8c55d44cbbab14d106dd79a3f16274493a
SHA1: 279f8c00c148ff4d0a11571987e681592acd9214
MD5sum: 03996a3fdb80e94266a60a118457b6bc
Description: Provides daemons for monitoring Hadoop and related tools.
 Provides daemons for monitoring Hadoop and related tools.

deployed deb file:

スクリーンショット 2019-07-10 14.14.25.png