Install apache ambari using local repository
Create Date: July 22, 2019 at 03:09 PM         | Tag: HORTONWORKS         | Author Name: Sun, Charles |
you can download the Obtain the compressed tape archive file (tarball) for the repository you want to create from here : https://docs.hortonworks.com/HDPDocuments/Ambari-2.7.0.0/bk_ambari-installation/content/ambari_repositories.html
Install apache ambari using local repository
New Comment
Installing HDP with Ambari
Create Date: July 15, 2019 at 04:14 PM         | Tag: HORTONWORKS         | Author Name: Sun, Charles |
Passwordless SSH
ssh-keygen
ll .ssh
scp .ssh/id_rsa.pub root@192.168.50.129:id_rsa.pub
ssh root@192.168.50.129
mkdir .ssh
cd .ssh
mv ../id_rsa.pub id_rsa.pub
cat id_rsa.pub >> authorized_keys
on the server, you can ssh the other servers without password:
ssh root@192.168.50.129
installing Ambari Agent:
New CommentInstalling Cloudera
Create Date: July 03, 2019 at 09:53 AM         | Tag: CLOUDERA         | Author Name: Sun, Charles |
Installing Cloudera Manager, CDH, and Managed Services
Common mistakes occurs here!
- this step sometimes creates confusion
- after you install Cloudera manager server
- run a script to configure external db
- before cdh service db configuration
- if you start cdh deployment using cm
- end witha non production cluster
- or an exception and no starting cm
Solution: configure scm to use external database
the database can be on the different node (recommended)
acces mysql:
mysql -u root -p
grant all on *.* to 'temp' identified by 'temp' with grant option;
grant all privileges on *.* to 'scm_user' identified by 'scm_pwd';
I need to repeat all these processes on every node to make Cloudera work: Step 1: Configure a Repository for Cloudera Manager
Ubuntu
- Download the cloudera.list file for your OS version to the /etc/apt/sources.list.d/ directory on the Cloudera Manager Server host.
You can find the URL in the Repo File column in the Cloudera Manager 6 Version and Download Information table for the Cloudera Manager version you want to install.
- Import the repository signing GPG key:
wget https://archive.cloudera.com/cm6/6.2.0/ubuntu1604/apt/archive.key sudo apt-key add archive.key
- Update your system package index by running:
sudo apt-get update
How To Install the Apache Web Server on Ubuntu 16.04
Step 1: Install Apache
Apache is available within Ubuntu's default software repositories, so we will install it using conventional package management tools.
We will begin by updating the local package index to reflect the latest upstream changes. Afterwards, we can install the apache2
package:
sudo apt-get update
sudo apt-get install apache2
After confirming the installation, apt-get
will install Apache and all required dependencies.
Step 2: Adjust the Firewall
Before we can test Apache, we need to modify our firewall to allow outside access to the default web ports. Assuming that you followed the instructions in the prerequisites, you should have a UFW firewall configured to restrict access to your server.
During installation, Apache registers itself with UFW to provide a few application profiles. We can use these profiles to simplify the process of enabling or disabling access to Apache through our firewall.
We can list the ufw
application profiles by typing:
sudo ufw app list
You should get a listing of the application profiles:
Output
Available applications: Apache Apache Full Apache Secure OpenSSH
As you can see, there are three profiles available for Apache:
- Apache: This profile opens only port 80 (normal, unencrypted web traffic)
- Apache Full: This profile opens both port 80 (normal, unencrypted web traffic) and port 443 (TLS/SSL encrypted traffic)
- Apache Secure: This profile opens only port 443 (TLS/SSL encrypted traffic)
For our purposes, we will allow incoming traffic for the Apache Full profile by typing:
sudo ufw allow 'Apache Full'
You can verify the change by typing:
sudo ufw status
You should see HTTP traffic allowed in the displayed output:
Output
Status: active To Action From -- ------ ---- OpenSSH ALLOW Anywhere Apache Full ALLOW Anywhere OpenSSH (v6) ALLOW Anywhere (v6) Apache Full (v6) ALLOW Anywhere (v6)
As you can see, the profile has been activated to allow access to the web server.
Step 3: Check your Web Server
At the end of the installation process, Ubuntu 16.04 starts Apache. The web server should already be up and running.
We can check with the systemd
init system to make sure the service is running by typing:
sudo systemctl status apache2
Output
◠apache2.service - LSB: Apache2 web server Loaded: loaded (/etc/init.d/apache2; bad; vendor preset: enabled) Drop-In: /lib/systemd/system/apache2.service.d └─apache2-systemd.conf Active: active (running) since Fri 2017-05-19 18:30:10 UTC; 1h 5min ago Docs: man:systemd-sysv-generator(8) Process: 4336 ExecStop=/etc/init.d/apache2 stop (code=exited, status=0/SUCCESS) Process: 4359 ExecStart=/etc/init.d/apache2 start (code=exited, status=0/SUCCESS) Tasks: 55 Memory: 2.3M CPU: 4.094s CGroup: /system.slice/apache2.service ├─4374 /usr/sbin/apache2 -k start ├─4377 /usr/sbin/apache2 -k start └─4378 /usr/sbin/apache2 -k start May 19 18:30:09 ubuntu-512mb-nyc3-01 systemd[1]: Stopped LSB: Apache2 web server. May 19 18:30:09 ubuntu-512mb-nyc3-01 systemd[1]: Starting LSB: Apache2 web server... May 19 18:30:09 ubuntu-512mb-nyc3-01 apache2[4359]: * Starting Apache httpd web server apache2 May 19 18:30:09 ubuntu-512mb-nyc3-01 apache2[4359]: AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 127.0.1.1. Set the 'ServerName' directive globally to suppress this message May 19 18:30:10 ubuntu-512mb-nyc3-01 apache2[4359]: * May 19 18:30:10 ubuntu-512mb-nyc3-01 systemd[1]: Started LSB: Apache2 web server.
As you can see above, the service appears to have started successfully. However, the best way to test this is to actually request a page from Apache.
You can access the default Apache landing page to confirm that the software is running properly. You can access this through your server's domain name or IP address.
If you are using DigitalOcean and do not have a domain name set up for your server, you can follow our guide how to set up a domain with DigitalOcean to set one up.
If you do not want to set up a domain name for your server, you can use your server's public IP address. If you do not know your server's IP address, you can get it a few different ways from the command line.
Try typing this at your server's command prompt:
hostname -I
You will get back a few addresses separated by spaces. You can try each in your web browser to see if they work.
An alternative is typing this, which should give you your public IP address as seen from another location on the internet:
sudo apt-get install curl
curl -4 icanhazip.com
When you have your server's IP address or domain, enter it into your browser's address bar:
http://server_domain_or_IP
You should see the default Ubuntu 16.04 Apache web page, which should look something like this:
New Comment