|What is LON-CAPA? Who is LON-CAPA? Documentation Installation Scholarship Developers Events|
|The LearningOnline Network with CAPA|
|Home » Installation » Documentation/Download » SuSE Linux Enterprise Server 10 Install|
SuSE Linux Enterprise Server 10 Install
Installing LON-CAPA on a minimal SuSE Linux Enterprise Server (SLES) 10
This document guides you through the process of setting up a new LON-CAPA server running SuSE Linux Enterprise Server 10 (SLES 10) with a minimum of packages installed. The computer will be configured solely as a LON-CAPA server and will be expected to have no other services running. Your server is expected to have a reasonably fast connection to the internet.
More information is available at http://install.lon-capa.org/.
Before you begin
Installing Linux is getting easier and easier. You will be required to log in to the machine and execute some routine Unix commands. Familiarity with the Apache web server, mod_perl, perl, and MySQL are not required to install and run LON-CAPA.
The installation process takes the following steps:
SuSE ISO files can be obtained from the Novell site: http://www.novell.com/products/server/.
You will need to know the following network settings for your installation. Note:You must have a static IP address to use LON-CAPA. DHCP is not supported.
Installing SuSE Linux Enterprise Server is quite easy if you've installed Linux products
before. Some documentation is available from
Once you system has rebooted, you will use yast to complete the configuration. Change the following settings:
Finish installing your server, read the "readme", reboot and log in as root.
Configure Firewall Settings
After reboot you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.
You will use yast to import packages required for LON-CAPA.
Select "Change Source of Installation". The media you used to install SLES10 will be listed as an installation source. If you do not already have a SLES10 installation source at your location, you may want to consider creating one from the 4 iso files for CDs 1 - 4, to avoid the need to flip CDs during LON-CAPA installation. Proceed as follows (e.g., for 32 bit):
mkdir -p sles10/CD1 mount -o ro,loop SLES-10-x86-CD1.iso /mnt cp -rv /mnt/* sles10/CD1 umount /mnt
Repeat those steps with CD2, CD3 and CD4.
Add an additional installation source
Add the LON-CAPA SLES 10 repository as an additional installation source, so software installation in yast will have access to at least two repositories - a SuSE/Novell source (for packages included for the standard distribution) and the LON-CAPA repository (for extra packages needed to run LON-CAPA). For the LON-CAPA source you will use:
After saving this configuration information for the LON-CAPA repository, quit yast.
yast -i LONCAPA-prerequisites
This may take some minutes due to LON-CAPA's large number of dependencies.
Retrieve and execute LON-CAPA setup program
Retrieve the LON-CAPA setup with one of the following commands:
Extract the archive with the following command:
tar xf install.tar
This creates a directory named installation. Change to it and execute the setup script with the following commands:
cd installation ./install.pl
The script is used to prepare a Linux system to run LON-CAPA, and can also be used to check the configuration of a system on which LON-CAPA has already been installed. Typically, though, you will run this script only once, when you first install LON-CAPA.
The script will analyze your system to determine which actions are recommended. The script will then prompt you to choose the actions you would like taken. Once a choice has been entered for all nine possible actions, required changes will be made.
The possible actions are:
Determine LON-CAPA Settings
LON-CAPA requires a number of identifying parameters to be set in order for it to function at all. Below is a list with descriptions.
To configure and install LON-CAPA, execute the following commands:
cd /root/loncapa-X.Y.Z (X.Y.Z should correspond to a version number like '2.10.0') ./UPDATE
You will need to enter the LON-CAPA configuration information you determined in the previous section.
After installing LON-CAPA, and taking any actions included in the WARNINGS file created during installation, it is recommended that you set loncontrol to start automatically on boot, by executing the following command:
/sbin/chkconfig --level 35 loncontrol on
You will need at least one user at your site who has the role of 'domain coordinator'. This user creates accounts for other users and grants them additional privileges. The make_domain_coordinator.pl script invoked below requires that you enter the user's password. Feel free to use the "passwd username" command to change it later. Replace USERNAME and DOMAIN with an appropriate user name and your domain.
cd /root/loncapa-X.Y.Z/loncom/build perl make_domain_coordinator.pl USERNAME DOMAIN
The LON-CAPA network services take a moment to start. Most misconfigurations will be apparent at this step.
/etc/init.d/loncontrol start /etc/init.d/apache2 start
If you receive warnings when starting the httpd about missing perl modules, please make sure you followed the instructions in Installing LON-CAPA Dependencies. If you still have errors, please contact the LON-CAPA group.
Point a web browser at your new machine and log in as the domain coordinator. Congratulations!
If things aren't working right
If you've followed the steps above and the server doesn't start or you think
there's something wrong, please get in touch with the LON-CAPA group.
You can submit a help request using our web form:
Contact Us: email@example.com
Supported by the National Science Foundation under NSF-ITR 0085921, NSF-CCLI-ASA 0243126, and NSF-CCLI 0717790. Any opinions, findings, and conclusions or recommendations expressed in this publication are those of the author(s) and do not necessarily reflect the views of the National Science Foundation. Initial funding for CAPA has been provided by the Alfred. P. Sloan Foundation and the Andrew W. Mellon Foundation.
|©2013 Michigan State University Board of Trustees.|