Installation (Ubuntu)

From vWiki
Jump to navigation Jump to search

Whilst this page was written with the installation of a Ubuntu Server 10.04 LTS in mind, it can also be used for Ubuntu 12.

Prepare Virtual Machine

  1. Create a virtual machine with the following options (use Custom)
    • Guest OS: Linux > Ubuntu 64bit
    • CPU: 1
    • Memory: 512 MB
    • Disk: 36GB
  2. Then add a second 36GB disk on a separate physical datastore (if you intend to use software RAID)
  3. Attach Ubuntu install ISO to the CD-ROM

Note that the specs above should be altered to suit your purposes. Whilst there is no need to use a 64 bit OS as opposed to 32 bit if you don't need to address lots of memory, it is standard these days.

OS Installation

Installing Ubuntu Server (LTS) is relatively painless, its generally a case of following the default or sensible choices for your locale. However, below are step-by-step instructions, which you probably won't require, but may help if you're not familiar with the terminology.

If you're completely new make sure you read through the instructions 1st, so that you're prepared for the information you'll need to provide.

  1. Select language for installer
  2. Select Install Ubuntu Server
  3. Choose Language screens
    1. Select language for server (and remainder of the installer)
    2. Select location
  4. Ubuntu Installer Main Menu screens
    1. Select Yes for questions to determine appropriate keyboard, or No to just select a keyboard layout
  5. Configure the network screen
    1. Enter the hostname for the server (not a FQDN, so hostname rather than hostname.domain.com)
  6. Configure the clock screen
    1. Select Yes to accept the suggested timezone, or No to alter
  7. Partition disks screens
    1. Select Guided - use entire disk and set up LVM
    2. Select the disk to partition and install the OS onto
    3. Select Yes to Write the changes to disks and configure LVM
    4. Accept the full amount to partition
    5. Select Yes to Write the changes to disks
  8. Set up users and passwords screens
    1. Enter your name
    2. Enter your username (that you will use to login with)
    3. Enter your password
      • If you use a weak password (eg less that 8 characters) you'll be asked to confirm this is OK once you've verified it
    4. Re-enter (verify) your password
    5. Select No to not Encrypt your home drive
      • If you are really worried about your dat being compromised you should consider encrypting the whole drive during its partitioning
  9. Configure the package manager screen
    1. Enter proxy server details if required for server to access the internet for updates
  10. Select and install software screen
    1. Select No automatic updates if you want to control how updates are applied yourself, otherwise select Install security updates automatically
  11. Software selection screens
    1. Select OpenSSH Server (press [Space] when item is highlighted), this allows you to Putty/SSH to the server
    2. Select any other required software, eg
      • DNS Server - Only required if you want your server to be a DNS server; or in order to configure split DNS, which is required for an exchange server install
      • LAMP Server - Only required for Apache webserver (with MySQL and PHP)
  12. Configuring grub-pc screen
    1. Select Yes to Install the GRUB boot loader to the master boot record
  13. Finish the installation screen
    1. Select Continue

Install on Software RAID

On the Partition Disks screens use the following to setup software RAID during OS installation.

  • If setting up software RAID follow the steps below, otherwise just select Guided - use entire disk and set up LVM
  1. Select "Manual
  2. Then create a partition...
    1. Select the first disk (sda) and on the next screen, Yes, to Create new empty partition table on this device?
    2. Select the FREE SPACE, then Create a new Partition, and use all but the last 2GB of space,
    3. And then select type of Primary, and create at Beginning
    4. Change Use as to physical volume for RAID, and change the Bootable flag to Yes, the select Done setting up this partition
  3. Repeat the above on the remaining FREE SPACE on sda, to create another primary physical volume for RAID, but 'not bootable
  4. Select the second disk, sdb, and repeat the steps taken for sda to create two identical partitions
  5. On the same screen, select the Configure Software RAID option (at the top), and then confirm through the next screen
  6. Create a RAID pack/multidisk...
    1. Select Create MD device, then select RAID1 (ie a mirror), then confirm 2 Active devices, and 0 Spare devices
    2. Select both /dev/sda1 and /dev/sdb1 partitions, and then select Finish
  7. Repeat the above to create a RAID volume using /dev/sda2 and /dev/sdb2 partitions
  8. Now select the RAID device #0 partition (select the #1 just under RAID1 device line), and change the Use as and select Ext3...
  9. Change the Mount point to /, then select Done configuring this partition
  10. Now select the RAID device #1 partition (select the #1 just under RAID1 device line), and change the Use as and select Swap area
  11. Then select Done configuring this partition then finally Finish partitioning and write changes to disk, and confirm to Write the changes to disks
  12. Accept the "The kernel was unable to re-read...system will need to restart" complaints for each RAID multidisk, after which the install will continue (note there's a little more to do post install to ensure you can boot using the second disk should the first fail).

Much of this page was originally borrowed heavily from the following pages - they are well worth a read!

Post OS Install Config

Enable Root

  1. Use the command sudo passwd root
  2. Enter your user password
  3. Enter a strong password for the root account

For Ubuntu 18...

  1. Use the command sudo passwd
  2. Enter your user password
  3. Enter a strong password for the root account

Finish Software RAID config

Only if configured during install

  1. Start-up grub (by entering grub and enter the following commands (seems to work better via SSH than direct console)...
    • device (hd1) /dev/sdb
    • root (hd1,0)
    • setup (hd1)
    • quit
  2. Then edit the /boot/grub/menu.lst config file. Go to the end of the file where the boot options are, and create a copy of the first option and edit the following lines
    • title Add "Primary disk fail" or something similar to end
    • root Change hd0 to hd1
  3. To check the RAID setup of your drives use
    • mdadm --misc -D /dev/md0
    • mdadm --misc -D /dev/md1

Change IP Address

v8 Hardy Heron / v10 Lucid Lynx

  • Edit the /etc/network/interfaces file in the following fashion to set static address details
# The primary network interface
auto eth0
iface eth0 inet static
        address 192.168.1.150
        netmask 255.255.255.0
        network 192.168.1.0
        broadcast 192.168.1.255
        gateway 192.168.1.1
  • Then check the local hosts file /etc/hosts, so that the IP v4 part looks like this (so the host can resolve itself)...
127.0.0.1       localhost
192.168.1.150   hostname.domain.com   hostname
  • Check that DNS resolution is setup correctly in /etc/resolv.conf. Add additional DNS nameservers as required, as found in in order of preference. You can also add the domain of the server (domain), and add domain suffix searches (search), both are optional. For example...
nameserver 192.168.1.20
nameserver 127.0.0.1
domain domain.com
search domain.com
search domain.com
  • Then restart networking
    • /etc/init.d/networking restart
  • Confirm network config is as expected with
    • ifconfig

v12 Precise Pangolin

  • Edit the /etc/network/interfaces file in the following fashion to set static address details
# The primary network interface
auto eth0
iface eth0 inet static
        address 192.168.1.150
        netmask 255.255.255.0
        gateway 192.168.1.1

dns-nameservers 192.168.1.20 8.8.8.8
dns-domain localdomain.com
dns-search localdomain.com anotherdomain.com
        
  • Then check the local hosts file /etc/hosts, so that the IP v4 part looks like this (so the host can resolve itself)...
127.0.0.1       localhost
192.168.1.150   hostname.domain.com   hostname
  • Then restart networking
    • service networking restart
  • Confirm network interface config is as expected with
    • ifconfig
  • Confirm DNS config is as expected with
    • less /etc/resolv.conf

Persistent Route

To add a persistent route to an interface, add using the following syntax (example sends traffic to 172.32.1.0/24 via eth1 to 192.168.1.100

up route add -net 172.32.1.0/24 gw 192.168.1.100 dev eth1

Additional IPs / Multihome

To add additional IP addresses to an interface, create sub-interfaces as below.

auto eth0:1
auto eth0:2 

# Sub 1
iface eth0:1 inet static
    address 192.168.1.160
    netmask 255.255.255.0

# Sub 2
iface eth0:2 inet static
    address 192.168.1.161
    netmask 255.255.255.0

RTNETLINK answers: File exists - Note that you can't use the same default gateway twice, doing so will cause this error

Update the OS

  1. Run the following command to update the apt package database
    • apt-get update
  2. To install any updates
    • apt-get upgrade
    • If updates are being held back (eg linux image), then use aptitude safe-upgrade
  3. If running in VMware VM, install VM Tools

Remove Old Version

Old kernel images will tend to linger in /boot and source code will remain in /user/src. These can be safely removed so long as you're completely certain which you are using (normally the latest)

  1. Get the versions currently installed
    • dpkg --get-selections | grep linux-image
  2. Remove unwanted versions (don't remove the current or base/unversioned image)
    • EG apt-get purge linux-image-3.2.0-32-virtual
    • If you've got lots to remove its easier to do lots in one go
      • EG apt-get purge linux-image-3.2.0-51-virtual linux-image-3.2.0-52-virtual

To remove old source, just delete manually,

  • EG rm -fr /usr/src/linux-headers-3.2.0-51

NTP

Not required if your server doesn't really need bang on accurate time

Out of the box your server will sync every time its restarted and drift a bit in-between. There is an additional resource demand in running the NTP daemon so unless you need to, there's no need to install the full blown NTP daemon.

I tend to have one or two servers updating from remote (public) servers, and then all others updating from those.

  1. Install the service
    • apt-get install ntp
  2. Update the NTP config file, /etc/ntp.conf (Example below is for a server updating from public European servers - see http://www.pool.ntp.org/)
    • server 0.europe.pool.ntp.org
    • server 1.europe.pool.ntp.org
    • server 2.europe.pool.ntp.org
    • server 3.europe.pool.ntp.org
  3. Restart the NTP service
    • service ntp restart
  4. Verify using the following commands
    • ntpq -np
    • date