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.

Cloudera APT repository broken atm

Cloudera APT repository broken atm

New Contributor

Hello guys,

 

I get several errors like this when trying to update my cluster:

 

Err http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/ wheezy-cdh5/contrib hadoop-hdfs-zkfc all 2.6.0+cdh5.5.2+992-1.cdh5.5.2.p0.10~wheezy-cdh5.5.2
  404  Not Found
Err http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/ wheezy-cdh5/contrib zookeeper-server all 3.4.5+cdh5.5.2+92-1.cdh5.5.2.p0.10~wheezy-cdh5.5.2
  404  Not Found

Maybe it's time to trigger repository metadata refresh ;-)

 

Thanks in advance for fixing this

 

Adam

10 REPLIES 10

Re: Cloudera APT repository broken atm

Master Collaborator

@acecile, thank you for the report, we are investigating this.  Will report back with our findings.

Re: Cloudera APT repository broken atm

New Contributor

Great.

 

I checked the file inside your repo and clearly something went wrong with latest build of zookeeper stuff. All package are missing for the newer version referenced in metadata files.

Re: Cloudera APT repository broken atm

Master Collaborator

I think we've got it resolved now, would you mind checking again?  Thanks

Re: Cloudera APT repository broken atm

New Contributor

Guess we are not on the same tz, tomorrow ;)

Re: Cloudera APT repository broken atm

New Contributor

Hello,

 

Not it's not:

Err http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/ wheezy-cdh5/contrib hadoop-hdfs-zkfc all 2.6.0+cdh5.5.2+992-1.cdh5.5.2.p0.10~wheezy-cdh5.5.2
404 Not Found

Err http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/ wheezy-cdh5/contrib zookeeper-server all 3.4.5+cdh5.5.2+92-1.cdh5.5.2.p0.10~wheezy-cdh5.5.2
404 Not Found

Err http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/ wheezy-cdh5/contrib hadoop-hdfs-journalnode all 2.6.0+cdh5.5.2+992-1.cdh5.5.2.p0.10~wheezy-cdh5.5.2
404 Not Found

 

 

Look at here for example:

http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/pool/contrib/z/zookeeper/

 

There's nothing versionned as 5.5.2...

 

Regards, Adam.

Re: Cloudera APT repository broken atm

Master Collaborator

Adam,

 

  That's correct.  CDH 5.5.2 was retracted, the next release that will appear in the repo will be 5.5.3.  What version are you currently running?  If you're on 5.5.1, that is currently the latest and you'll have to wait until we release 5.5.3, I'm afraid.

 

Regards

Re: Cloudera APT repository broken atm

New Contributor

Ok, I just managed to get it working by complety purging my apt-get update cache:

rm /var/lib/apt/lists/*

 

Now it doesn't try anymore to get some 5.5.2 files. I don't understand why my apt did not spot the metadata updates.

I have an idea about this: did you rollback to 5.5.1 using backup for example ? If so you probably rolled back metadata file with modification time older than the 5.5.2 ones. In that case, any apt client will get the new metatdata.

You should probably just "touch" the file to make them looks newer:

http://archive.cloudera.com/cdh5/debian/wheezy/amd64/cdh/dists/wheezy-cdh5/contrib/binary-amd64/

 

See, it's from january, the 11th. I'm pretty sure there was at some time Package.* files newer than these ones.

 

Best regards, Adam.

Re: Cloudera APT repository broken atm

New Contributor

I would suggest asking your sysadmin to go into the apt repository folder and simply do:

 

find /path/to/apt/repo/ -exec touch {} \;

 

It will update the timestamp so my apt will understand there's newer file to download. Do you want me to keep some server broken to confirm this command fixed the issue ?

 

Best regards, Adam.

Re: Cloudera APT repository broken atm

Master Collaborator

@acecile, thanks for confirming.  No, don't worry about leaving any server in a broken state.  You are correct that we temporarily had 5.5.2 on the repo then rolled it back.  It appears they hadn't fixed the metadata until after you tried to download it.  Their suggestion was more or less what you ended up doing.  The following command should have cleared up your cache:

 

apt-get clean all

 

I apologize about the headaches, we will do this correctly next time, should there be a next time.  I think our repo is in a stable state now.  


Regards