Annotation of doc/build/alma9_install.frag, revision 1.3
1.1 raeburn 1: <h1>Installing LON-CAPA on a minimal AlmaLinux 9 System</h1>
2: <p>
3: This document guides you through the process of setting up a new LON-CAPA
4: server or virtual machine running AlmaLinux 9 with a minimum of packages installed.
5: The server or virtual machine will be configured solely as a LON-CAPA server and will be
6: expected to have no other services running. Your server or virtual machine is expected to have
7: a fast connection to the internet.
8: </p><p>
9: More information is available at
10: <a href="http://install.lon-capa.org/">http://install.lon-capa.org/</a>.
11: </p>
12:
13: <h2>Before you begin</h2>
14: <p>
15: Installing Linux is straightforward.
16: You will be required to log in to the machine and execute
17: some routine Unix commands. Familiarity with the Apache web server, mod_perl,
18: perl, and MySQL are not required to install and run LON-CAPA.
19: </p>
20:
21: <h2>Installation Overview</h2>
22: <p>
23: The installation process takes the following steps:
24: </p>
25: <ol>
26: <li><a href="#obt">Obtain AlmaLinux 9 installation iso file</a></li>
27: <li><a href="#net">Determine Network Settings</a></li>
28: <li><a href="#lin">Install AlmaLinux 9</a></li>
29: <li><a href="#upd">Update your system</a></li>
30: <li><a href="#ilc">Install LON-CAPA</a></li>
31: <li><a href="#cdc">Create a Domain Coordinator</a></li>
32: <li><a href="#sts">Start/Restart services</a></li>
33: <li><a href="#log">Log in to LON-CAPA</a></li>
34: </ol>
35:
36: <hr />
37: <h2>1. <a id="obt">Obtain AlmaLinux 9</a></h2>
38: <p>
39: AlmaLinux 9 isos can be obtained from links included on the
40: <a href="https://mirrors.almalinux.org/isos.html">AlmaLinux download page</a>.
41: Either download the Minimal iso or the DVD iso.
42: </p>
43:
44: <h2>2. <a id="net">Determine Network Settings</a></h2>
45: <p>
46: You will need to know the following network settings for your installation.
47: <b>Note: </b>You must have a static IP address to use LON-CAPA.
48: DHCP is <em>not</em> supported.
49:
50: <ul>
51: <li>ip address </li>
52: <li>netmask </li>
53: <li>hostname </li>
54: <li>gateway </li>
55: <li>domain name server(s) </li>
56: </ul>
57:
58: <h2>3. <a id="lin">Minimal AlmaLinux 9 Install</a></h2>
59: <p>
60: Most of the installation screens are self explanatory.
61: There are a few steps that require comment and are dealt with below.
62: </p>
63: <dl style="list-style:square outside none">
64: <dt>Installation Language</dt>
65: <dd>Use English as your installation language.</dd>
66: <dt>Installation Destination</dt>
67: <dd>For a fresh install may want to use the automatic partitioning feature of the installer.
68: If you want to customize partitioning check the "I will configure partitioning" radio button.
69: LON-CAPA resource files are stored in the /home directory, so the
70: majority of the disk space should be allocated here. If you have 20 GB
71: of space for AlmaLinux, /home should receive at least 10 to 12 GB.
72: Since Mariadb uses the /var filesystem to store its databases you should
73: have at least 4 GB of space available on /var. Be sure to
74: include adequate swap space. A minimum is 512 MB, but you should
75: typically have 1 or 2x as much swap space as you do physical RAM.</dd>
76: <dt>Network and Hostname</dt>
77: <dd>LON-CAPA will <b>not</b> work with a machine set up to use a dynamic
78: IP address. When configuring your network card, be sure to unselect
79: the DHCP option and enter your network information. Enter your hostname</dd>
80: <dt>Software Selection</dt>
81: <dd>Check the "Minimal Install" radio button in the "Base Environment" panel,
82: and check the "Standard" checkbox in the "Additional software for Selected Environment" panel.</dd>
83: </dl>
84: <p>
85: Finish installing your server, reboot it, and log in as root.
86: </p>
1.2 raeburn 87: <h3>Optionally add a user who can login using ssh</h3>
88: <p>
89: The default is to disallow login for root using ssh, so if you plan to allow remote access via ssh, it is recommended to create a user account, replacing <username> with the desired username in the commands below. If you prefer, you can skip this step and simply use the Linux user account which you will create later at step 6 ("Creating a Domain Coordinator") for ssh access.
90: <pre>
1.3 ! raeburn 91: /sbin/adduser <username>
! 92: passwd <username>
1.2 raeburn 93: </pre>
1.1 raeburn 94: <h3>Firewall Configuration</h3>
95: <p>
96: LON-CAPA can use Firewalld, available by default for AlmaLinux 9. Enable access to standard
97: web server ports (i.e., http and https):
98: </p>
99: <pre>
100: systemctl enable firewalld
101: systemctl start firewalld
102: firewall-cmd --zone=public --permanent --add-service=http
103: firewall-cmd --zone=public --permanent --add-service=https
104: firewall-cmd --reload
105: </pre>
106:
107: <h2>4. <a id="upd">Update your system</a></h2>
108: <p>
109: Update your system to the latest versions of the system software using dnf.
110: </p>
111: <pre>
112: dnf update
113: </pre>
114: <p>
115: If the kernel was updated, reboot your system before continuing with the installation.
116: </p>
117:
118: <h3>Set up access to package repositories</h3>
119: <p>
120: Enable access to the EPEL repository
121: </p>
122: <pre>
123: dnf install epel-release
124: </pre>
125: <p>
126: Enable the AlmaLinux 9 CRB repository
127: </p>
128: <pre>
129: dnf config-manager --set-enabled crb
130: </pre>
131: <p>
132: Install wget and then the loncapa.repo file from the LON-CAPA install site:
133: </p>
134: <pre>
135: dnf install wget
136: wget -O /etc/yum.repos.d/loncapa.repo http://install.loncapa.org/versions/alma/9/loncapa.repo
137: </pre>
138: <p>
139: Verify the required repositories are enabled:
140: </p>
141: <pre>
142: dnf repolist enabled
143: </pre>
144: <p>
145: The list of enabled repos should be as follows:
146: </p>
147: <table style="border: 0px; border-collapse: collapse;">
148: <tr><th>repo id</th><th>repo name</th></tr>
149: <tr><td>appstream</td><td>AlmaLinux 9 - AppStream</td></tr>
150: <tr><td>baseos</td><td>AlmaLinux 9 - BaseOS</td></tr>
151: <tr><td>powertools</td><td>AlmaLinux 9 - CRB</td></tr>
152: <tr><td>epel</td><td>Extra Packages for Enterprise Linux 9 - x86_64</td></tr>
153: <tr><td>extras</td><td>AlmaLinux 9 - Extras</td></tr>
154: <tr><td>loncapa-updates-basearch</td><td>AlmaLinux 9 LON-CAPA x86_64 Updates</td></tr>
155: <tr><td>loncapa-updates-noarch</td><td>AlmaLinux 9 LON-CAPA noarch Updates</td></tr>
156: </table>
157:
158: <h3>Install and enable a Mail Transfer Agent (MTA), e.g., postfix</h3>
159: <pre>
160: dnf install postfix
161: systemctl enable postfix
162: systemctl start postfix
163: </pre>
164:
165: <h3>Configure SELinux</h3>
166: <p>
167: The default AlmaLinux 9 installation includes SELinux enabled. Until such time as an SELinux security policy has been created for LON-CAPA, SELinux should be disabled.
168: Retrieve the loncapa_selinux_config file from the LON-CAPA install site:
169: </p>
170: <pre>
171: wget http://install.loncapa.org/versions/alma/9/loncapa_selinux_config
172: </pre>
173: <p>
174: Install the selinux config file
175: </p>
176: <pre>
177: mv /etc/selinux/config /etc/selinux/config.backup
178: mv loncapa_selinux_config /etc/selinux/config
179: reboot
180: </pre>
181:
182: <h2>5. <a id="ilc">Installing LON-CAPA</a></h2>
183: <h3>Install prerequisites</h3>
184: <p> Execute: </p>
185: <pre>
186: dnf install LONCAPA-prerequisites
187: </pre><p>
188: This may take some minutes due to LON-CAPA's large number of dependencies.
189: </p>
190: <h3>Set locale to en_US.UTF-8</h3>
191: <p>Execute the command:</p>
192: <pre>
193: /usr/bin/localectl set-locale LANG=en_US.UTF-8
194: </pre>
195: <h3>Retrieve and execute LON-CAPA setup program</h3>
196: <p>
197: Retrieve the LON-CAPA setup with the following command:
198: </p>
199: <pre>
200: wget http://install.loncapa.org/linux/install.tar
201: </pre>
202: <p>
203: Extract the archive with the following command:
204: </p>
205: <pre>
206: tar xf install.tar
207: </pre>
208: <p>
209: This creates a directory named <span style="font-family: 'Lucida Console','Menlo','Monaco','Courier', monospace;">installation</span>.
210: Change to it and execute the setup script with the following commands:
211: </p>
212: <pre>
213: cd installation
214: ./install.pl
215: </pre>
216: <p>
217: The script is used to prepare a Linux system to run LON-CAPA, and can also be
218: 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.
219: </p>
220: <p>
221: 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.
222: Once a choice has been entered for all nine possible actions, required changes will be made.
223: </p>
224: <p>The possible actions are:</p>
225: <ul>
226: <li>Create the www user/group</li>
227: <li>Install the package LON-CAPA uses to authenticate users.</li>
228: <li>Set-up the MySQL (Mariadb) database</li>
229: <li>Set-up MySQL (Mariadb) permissions</li>
230: <li>Configure Apache web server</li>
231: <li>Configure start-up of services</li>
232: <li>Check firewall settings</li>
233: <li>Stop services not used by LON-CAPA, e.g., services for a print server: cups daemon</li>
234: <li>Download LON-CAPA source code in readiness for installation</li>
235: </ul>
236: <h3>Determine LON-CAPA Settings</h3>
237: <p>
238: LON-CAPA requires a number of identifying parameters to be set in order
239: for it to function at all. Below is a list with descriptions.
240: </p>
241: <dl>
242: <dt>Host Type (library or access)</dt>
243: <dd>The server must be designated a 'library' or an 'access' server. In
244: general you should have a library server for your instructors to create
245: their course content on and run their courses. Students should connect
246: to access servers. If you are doing the first install of LON-CAPA at
247: your site, or if you are playing with it for your own edification you
248: should make your machine a 'library' server.</dd>
249: <dt>LON-CAPA domain</dt>
250: <dd>Each site or school which installs LON-CAPA needs its own domain.
251: Here at MSU we use 'msu'. You should choose something short but
252: meaningful. <i>Restriction: One word, no underscores, and no special
253: characters except . or -</i> .<br />Domain names which include a departmental
254: abbreviation are not recommended as although LON-CAPA may start in
255: a single department, other departments frequently join subsequently.
256: For a domain name: 'msu' is a superior choice to 'msuphys' for example.
257: </dd>
258: <dt>LON-CAPA host id</dt>
259: <dd>Each LON-CAPA server requires a unique internal name. We use names
260: such as "msul1" for the first library server. <i>Restriction: One word,
261: no underscores, and no special characters except -</i> .
262: </dd>
263: <dt>Domain's Primary Library Server ID</dt>
264: <dd>If you are setting up a domain with a single library server, then the domain's primary library server ID will be the LON-CAPA host id of that server (e.g., msul1). Once your domain grows and you need to add more servers, one of the library servers in the domain should be assigned as the domain's primary library server. This will be where domain-wide settings will be stored.<dd>
265: <dt>Host administrator email</dt>
266: <dd>The amount of email sent to this address is relatively minimal. Messages
267: are sent every time the system starts up, or if the system is in
268: serious trouble. If you are installing a LON-CAPA instance on a laptop,
269: because you are planning to contribute to LON-CAPA development,
270: make this <span style="font-family: 'Lucida Console','Menlo','Monaco','Courier', monospace;">
271: root@localhost</span>.
272: </dd>
273: <dt>Support email address</dt>
274: <dd>Enter an e-mail address here, so users of the system
275: will be able to click an "Ask Helpdesk" link in the system to
276: display a web form which they will complete to request support from
277: your institution's helpdesk. On form submission the contents
278: will be sent to the e-mail address you specify.
279: </dd>
280: </dl>
281:
282: <h3>Configuring LON-CAPA</h3>
283: <p>
284: To configure and install LON-CAPA, execute the following commands:
285: </p>
286: <pre>
287: cd /root/loncapa-X.Y.Z (X.Y.Z should correspond to a version number like '2.11.4')
288: ./UPDATE
289: </pre>
290: <p>
291: You will need to enter the LON-CAPA configuration information you determined
292: in the previous section.
293: </p>
294:
295: <h2>6. <a id="cdc">Creating a Domain Coordinator</a></h2>
296: <p>
297: You will need at least one user at your site who has the role of
298: 'domain coordinator'. This user creates accounts for other users and
299: grants them additional privileges. The make_domain_coordinator.pl script
300: invoked below requires that you enter the user's password.
301: Feel free to use the "passwd username" command to change it later.
302: Replace USERNAME and DOMAIN with an appropriate user name and your domain.
303: If installing a library server and an access server on separate machines or VMs
304: you need only run make_domain_coordinator.pl on the library server.
305: </p>
306: <pre>
307: cd /root/loncapa-X.Y.Z/loncom/build
308: perl make_domain_coordinator.pl USERNAME DOMAIN
309: </pre>
310:
311: <h2>7. <a id="sts">Start/Restart Services</a></h2>
312: <p>
313: The LON-CAPA network services take a moment to start. Most misconfigurations
314: will be apparent at this step.
315: </p>
316: <pre>
317: /home/httpd/perl/loncontrol start
318: systemctl start httpd
319: </pre>
320: <p>
321: If you receive warnings about missing perl modules, when starting the httpd service
322: please make sure that the LONCAPA-prerequisites rpm is installed using this command:
323: </p>
324: <pre>
325: rpm -q LONCAPA-prerequisites rpm
326: </pre>
327: <p>
328: If it is not installed, ensure that the required Linux repositories are enabled (see
329: the "Set up access to package repositories" section above), then install it:
330: </p>
331: <pre>
332: dnf install LONCAPA-prerequisites
333: </pre>
334: <p>
335: If you still have errors, please contact the LON-CAPA Helpdesk: helpdesk at loncapa.org
336: </p>
337: <p>Ensure that LON-CAPA network services and the httpd service are set to start on boot:
338: <pre>
339: systemctl enable loncontrol
340: systemctl enable httpd
341: </pre>
342:
343: <h2>8. <a id="log">Log in to your LON-CAPA Machine</a></h2>
344: <p>
345: Point a web browser at your new machine and log in as the domain
346: coordinator. Congratulations!
347: </p>
348:
349: <hr>
350: <h2>If things aren't working right</h2>
351: <p>
352: If you've followed the steps above and the server doesn't start or you think
353: there's something wrong, please contact the LON-CAPA helpdesk.
354: Installation/update support is available from: helpdesk at loncapa.org
355: (replace " at " with @).
356: If there were errors in installation of the dependency RPMs or errors during the
357: automatic setup, please send us as much information as possible.
358: If some part of this document is unclear please let us know.
359: </p>
FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>
![[BACK]](/icons/back.gif){kind=icon}
Return to alma9_install.frag CVS log ![[TXT]](/icons/text.gif){kind=icon}
![[DIR]](/icons/dir.gif){kind=icon}
Up to [LON-CAPA] / doc / build