Support Questions

Find answers, ask questions, and share your expertise

username gives error in wget

avatar
New Contributor

Hello,

I signed up for Cloudera to install Hadoop with Ambari, and I got an email saying that the username is my Google email address.
During the installation process, you need to download the repo file in the following way.

 

wget -O /etc/apt/sources.list.d/ambari.list https://id@gmail.com:mypasswd@archive.cloudera.com/p/ambari/ubuntu14/2.x/updates/2.7.5.0/ambari.list

 

But it doesn't work properly because of "@" in username.
Can you help?

5 REPLIES 5

avatar

@jiyo 

 

Maybe. You wrote that "it doesn't work properly because of "@" in username". Why do you say that "it doesn't work properly"? What is the exact error message you're receiving?

 

 

Bill Brooks, Community Moderator
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

avatar
New Contributor

@ask_bill_brooks 

 

Thank you for your help.

The message I received is as follows.

 

--------------------------------------------------------------------------------------------------

root@hadoop00:/home/hadoop00# wget -O /etc/apt/sources.list.d/ambari.list https://myname@gmail.com:*MyPassWd*@archive.cloudera.com/p/ambari/ubuntu14/2.x/updates/2.7.3.39/ambari.list
--2021-06-28 14:29:12-- https://myname@gmail.com/
Resolving gmail.com (gmail.com)... 142.250.76.133, 2404:6800:400a:80e::2005
connect gmail.com (gmail.com)|142.250.76.133|:443... Connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://www.google.com/gmail/ [following]
--2021-06-28 14:29:12-- https://www.google.com/gmail/
Resolving www.google.com (www.google.com)... 172.217.161.196, 2404:6800:400a:80b::2004
connect (www.google.com)|172.217.161.196|:443... Connected.
HTTP request sent, awaiting response... 302 Found
Location: https://mail.google.com/mail/ [following]
--2021-06-28 14:29:13-- https://mail.google.com/mail/
Resolving mail.google.com (mail.google.com)... 216.58.196.229, 2404:6800:400a:806::2005
connect mail.google.com (mail.google.com)|216.58.196.229|:443... Connected.
HTTP request sent, awaiting response... 302 Moved Temporarily
Location: https://accounts.google.com/ServiceLogin?service=mail&passive=true&rm=false&continue=https://mail.go... [following]
--2021-06-28 14:29:14-- https://accounts.google.com/ServiceLogin?service=mail&passive=true&rm=false&continue=https://mail.go...
Resolving accounts.google.com (accounts.google.com)... 142.250.206.237, 2404:6800:400a:804::200d
connect accounts.google.com (accounts.google.com)|142.250.206.237|:443... Connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘/etc/apt/sources.list.d/ambari.list’

/etc/apt/sources.list.d/ [ <=> ] 92.02K --.-KB/s in 0.1s

2021-06-28 14:29:14 (894 KB/s) - ‘/etc/apt/sources.list.d/ambari.list’ saved [94232]

--------------------------------------------------------------------------------------------------

 

The directory '/etc/apt/source.list.d/' contains an html document starting with "<!DOCTYPE>" has been saved. When I did "apt-get update", I received a message saying like the type of '<!DOCTYPE', the first word in document, is unknown. So I found out that I received the wrong document from wget.

avatar
Master Mentor

@jiyo 

Your attempt will fail the below explains why your gmail account is not recognized 🙂

As of February 1, 2021, access to CDH binaries for production purposes requires authentication. To access the binaries at the locations below, you must first have an active subscription agreement and obtain a license key file along with the required authentication credentials (username and password).

The license key file and authentication credentials are provided in an email sent to customer accounts from Cloudera when a new license is issued. If you have an existing license with a Cloudera Enterprise entitlement, you might not have received an email. In this instance, you can identify the authentication credentials from the license key file. If you do not have access to the license key, contact your account representative to receive a copy.
See documentation here
Hope that helps

avatar

@jiyo 

The explanation provided earlier by @Shelton isn't wrong, but I thought I would follow-up and provide some context I think would be helpful.

 

In your original question, you wrote that you "got an email saying that the username is my Google email address." This email likely was referring to the username you would use to log into the Cloudera Community, not the username you would use to access Cloudera's private repositories where the binaries for Cloudera's distributions of Hadoop and/or Ambari are now located.

As he pointed out and hopefully you are now aware, Cloudera modified its download policies and the binaries you are seeking to download are now only available in a private repository. If not, please see the announcement here: Transition to private repositories for CDH, HDP and HDF.

 

The credentials to access this private repository are not generally the same ones to access Cloudera's website or the Cloudera community. The same announcement describes new patch releases of Ambari which are required to access Cloudera’s private repositories, which now contain these new and existing releases.

 

The reason you're getting the error message from the invocation of the wget command is that the credentials to use to access the aforementioned private repositories does not depend upon your Google email address, and the command is never actually getting to the point of accessing the host archive.cloudera.com. The HTTP 301 redirects you're seeing are responses from one of google's web servers, and not Cloudera's.

 

 

Bill Brooks, Community Moderator
Was your question answered? Make sure to mark the answer as the accepted solution.
If you find a reply useful, say thanks by clicking on the thumbs up button.

avatar
Master Mentor

@ask_bill_brooks 

Thanks for the addendum and official context.

Happy hadooping