Skip to main content
jiyo
jiyo
Silver ⭐️
June 24, 2021
Question

username gives error in wget

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

ask_bill_brooks
Platinum ⭐️
ask_bill_brooks
Platinum ⭐️
June 25, 2021

@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?

 

 

Translate
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.
jiyo
jiyoAuthor
Silver ⭐️
June 28, 2021

@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.google.com/mail/&ss=1&scc=1&ltmpl=default&ltmplcache=2&emr=1&osid=1# [following]
--2021-06-28 14:29:14-- https://accounts.google.com/ServiceLogin?service=mail&passive=true&rm=false&continue=https://mail.google.com/mail/&ss=1&scc=1&ltmpl=default&ltmplcache=2&emr=1&osid=1
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.

Translate
Shelton
Shelton
Gold ⭐️⭐️⭐️
June 29, 2021

@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

Translate
Terms & ConditionsAccessibility statement