Installation Manual for 2.17 on Oracle (and related) Linux

From WeBWorK_wiki
Revision as of 11:15, 11 September 2022 by Alex Jordan (talk | contribs)
Jump to navigation Jump to search

Under Construction

These instructions cover the installation of WeBWorK 2.17 from scratch onto an Oracle Linux 8 server. These instructions might work on related Linux distributions, but here and there the details may differ. It may help to cross-reference with other OS-specific installation guides at Manual Installation Guides.

If you are just upgrading WeBWorK, especially if you already have existing WeBWorK courses, see Upgrading WeBWorK from 2.16 to 2.17.

OS Users

These instructions reference four OS users.

  • You should have a personal account with sudo privileges. These instructions will use "myname" as the name of that user.
  • root
  • apache
  • wwadmin (we will create below)

It can be critical that you act as whatever user these instructions tell you to act as at each step. Do not act as root unless specifically instructed to.

Furthermore, when you will need to act as root, either use sudo su or sudo <command> as the instructions say. In certain places, actually switching users to root with sudo su or entering a root shell when a mere sudo someCommand was indicated will result in bad things that will not become apparent until later in the installation.


Now some comments on notation we will be using. We will use <key> to indicate that you should press a specific key (e.g. <Enter>, <Tab>, <F12>, etc.). Sometimes we will also use e.g. <wwadmin password> to indicate you have to enter the wwadmin password.

  • Code blocks that begin with $ should be run as myname.
  • Code blocks that begin with # should be run as root (via either a root shell or switching users to root with sudo su).
  • Code blocks that begin with @ should be run as wwadmin (for which you can use sudo su wwadmin).

You are not intended to type the $, or #, or @ characters as part of the provided commands.


We assume that you already have Oracle (or a closely related Linix distribution) installed, but that you haven't done much with yet.

We assume that you have a user account myname with sudo privileges.

Install MariaDB

After logging in to your server:

$ sudo yum install mariadb-server mariadb-connector-c mariadb-connector-c-devel

Answer y if it asks if this is OK. (For the remainder of these instructions, such trivial details might be omitted.) Now fire it up.

$ sudo systemctl enable mariadb
$ sudo systemctl start mariadb

Check that it is active with

$ sudo systemctl status mariadb

Now secure the server.

$ sudo mysql_secure_installation

This asks you for the database root password, which is nothing at this point. You should just hit <Enter>. Next there are five questions. Answer as indicated:

  • Set root password? n
  • Remove anonymous users? n
  • Disallow root login remotely? Y
  • Remove test database and access to it? Y
  • Reload privilege tables now? Y

Test that things work:

$ sudo mysql

You should see something close to:

Welcome to the MariaDB monitor.  Commands end with ; or \g.

MariaDB [(none)]> 

Now lets check the MariaDB users. To see the users, do the following

MariaDB> SELECT user,authentication_string,plugin,host FROM mysql.user;

You should see a table with only three users: root, root and root, each with a different host.

Now exit MariaDB

MariaDB> exit

Check perl version

The Oracle distribution used for this installation write-up has perl 5.26.3. Check if perl is installed and what its version is.

$ perl --version

Apache 2 and mod_perl

Install apache (httpd) and mod_perl.

$ sudo yum install httpd
$ sudo yum install mod_perl
$ sudo yum install libapreq2

Enable httpd service.

$ sudo systemctl enable httpd.service

Now enable the MPM-prefork module (and disable the MPM-event module)

$ sudo vim /etc/httpd/conf.modules.d/00-mpm.conf

Uncomment the mpm_prefork_module statement and comment out the mpm_event_module

LoadModule mpm_prefork_module modules/
#LoadModule mpm_event_module modules/

Next we add configuration files that will add the mod_perl and Apache request modules.

$ sudo vim /etc/httpd/conf.modules.d/02-perl.conf

Add the line LoadModule perl_module modules/ and save the file.

$ sudo vim /etc/httpd/conf.modules.d/apreq.conf

Add the line LoadModule apreq_module modules/ and save the file.

Then we configure Apache with our basic server info

$ sudo vim /etc/httpd/conf/httpd.conf

Uncomment and change the server name:


And finally, we need to make sure that the shared libraries have been properly identified

$ sudo ldconfig -v

You should now be able to start up the httpd service

$ sudo systemctl start httpd

Check its status just to confirm it's up.

$ sudo systemctl status httpd

For this installation write-up, the server's fully qualified domain name was already set up. You can confirm if this is the case for you by running:

$ hostname; hostname --fqdn

If your server's fully qualified domain name is not yet set up, run the command

$ sudo hostnamectl set-hostname <webwork>

where of course you should replace <webwork> by whatever your server's name is.

Again, you can check these settings by running the commands

$ hostname; hostname --fqdn

The first gives the server's fully qualified domain name (e.g. and the second the server's name (e.g. webwork).

Note that if your server can not find its fully qualified domain name, certain tools may not start.

Now restart Apache

$ sudo systemctl restart httpd

and test your server by connecting to your server from a web browser using the fully qualified domain name. You should see the Apache 2 Test Page indicating that Apache is running.

Install LaTeX

The Oracle/RHEL package for texlive is likely to be a few years out of date, so we will install texlive directly. At the time of this installation write-up, the current version is 2022. In the steps that follow, replace "2022" with whatever is current. Note the very last option --paper=letter is only if you actually want letter to be the default paper size. Leave that off if you would like it to be A4.

$ cd /tmp # working directory of your choice
$ sudo yum install wget
$ wget
$ zcat install-tl-unx.tar.gz | tar xf -
$ cd install-tl-*/
$ sudo perl ./install-tl --no-interaction --paper=letter

This could take a while because it is a full installation. A full installation is probably unnecessary, but now that WeBWorK can use LaTeX to make images, it's simpler to just go ahead and install everything so you are not surprised later by a missing package.

Now you might want to clean up the installation files.

$ cd ..
$ sudo rm -r install-tl* 

Install some graphics packages and npm

Some graphics tools were installed with our new LaTeX installation: dvipng and dvisvgm. We need a few more.

$ sudo yum install gd-devel netpbm-progs ImageMagick

And we will need Node Package Manager, npm:

$ sudo yum install npm

Downloading the WeBWorK System Software and Problem Libraries

Create the wwadmin user and give that user a password that you store securely somehwere. Having a wwadmin user who is distinct from your personal user account will help in the future when others might take over management of the server, or assist with management.

$ sudo useradd wwadmin
$ sudo passwd wwadmin

Give wwadmin some secure password.

We are finally at the point where we can start downloading and installing WeBWorK itself. We will use Git to download WeBWorK from Github.

$ cd /opt
$ sudo mkdir webwork
$ sudo chown wwadmin:wwadmin webwork
$ sudo su wwadmin
@ cd webwork
@ git clone
@ git clone
@ git clone
@ mkdir courses
@ mkdir libraries
@ mv webwork-open-problem-library libraries 

Important Note. The above commands retrieve the main branch which gives the latest stable release of the software package (webwork2, pg, etc) with bug fixes. If a stable release newer than 2.17 exists, that will be downloaded and these instructions may be a little out of date. So it is a good idea to check before downloading. The best way to do that is to look at and

Set Up Model Course

Now pull the model course from webwork2 into courses

@ cd /opt/webwork/webwork2/courses.dist
@ cp *.lst /opt/webwork/courses/
@ rsync -a modelCourse /opt/webwork/courses/

Setting Permissions

The PG installation directory and files should be owned by wwadmin and not writable by other users:

@ cd /opt/webwork/pg
@ chmod -R u+rwX,go+rX .

Most WeBWorK directories and files should also be owned by wwadmin and not writable by other users:

@ cd /opt/webwork/webwork2
@ chmod -R u+rwX,go+rX .
@ exit

Certain data directories need to be writable by the web server. These are DATA, courses, htdocs/tmp, logs, and tmp. Now we make these directories that need to be writable by the web server have apache as their group.

$ sudo bash
# cd /opt/webwork/webwork2/
# chgrp -R apache DATA ../courses htdocs/tmp logs tmp
# chmod -R g+w DATA ../courses htdocs/tmp logs tmp
# find DATA/ ../courses/ htdocs/tmp logs/ tmp/ -type d -a -exec chmod g+s {} \;
# chcon -R -t httpd_sys_rw_content_t DATA ../courses htdocs/tmp logs tmp

The chcon line is specific to SELinux to give the apache user certain privileges in those folders that are denied by default. Here is some more SELinux stuff to run.

# yum install policycoreutils-python-utils
# semanage fcontext -a -t httpd_sys_content_t '/opt/webwork(/.*)?' 
# semanage fcontext -a -t httpd_sys_rw_content_t '/opt/webwork/courses(/.*)?'
# semanage fcontext -a -t httpd_sys_rw_content_t '/opt/webwork/webwork2/logs(/.*)?'
# semanage fcontext -a -t httpd_sys_rw_content_t '/opt/webwork/webwork2/htdocs/tmp(/.*)?'
# setsebool -P httpd_can_sendmail 1
# setsebool -P httpd_can_network_connect on
# restorecon -vFR /opt

We also want to allow httpd to send pings during startup, which means we have to tell SELinux that's okay too. Create a new file called my-ping.te in wwadmin's home folder.

# vim /home/wwadmin/my-ping.te

Paste the following into the empty file:

module my-ping 1.0;

require {
       type httpd_t;
       class icmp_socket create;
       class rawip_socket { create getopt setopt write read };
       class capability net_raw;

#============= httpd_t ==============
allow httpd_t self:capability net_raw;
allow httpd_t self:icmp_socket create;
allow httpd_t self:rawip_socket { create getopt setopt write read };

Exit and save the file, then compile and install the policy:

# checkmodule -M -m -o my-ping.mod /home/wwadmin/my-ping.te
# semodule_package -o my-ping.pp -m my-ping.mod
# semodule -X 300 -i my-ping.pp

It is convenient to give WeBWorK administrators access to the five directories mentioned above as well, so they can perform administrative tasks such as removing temporary files, creating and editing courses from the command line, managing logs, and so on. We will add our user, wwadmin, to the apache group. Run the command

# usermod -a -G apache wwadmin
# exit

Compile color.c

$ cd /opt/webwork/pg/lib/chromatic
$ sudo yum install gcc
$ sudo su wwadmin
@ gcc color.c -o color
@ exit

You may see some warning messages which you can safely ignore.

Configuring the Shell

To make working with WeBWorK easier, there are a couple of changes you can make to your shell environment.

Add the WeBWorK bin directory to your path. This will allow you to run WeBWorK command-line utilities without typing the full path to the utility. Go to your home directory and backup your .bashrc file

$ cd
$ cp .bashrc .bashrc.bak1

Now edit .bashrc. (Alternatively, these edits can be applied to /etc/profile, which will apply to all users.)

$ vim .bashrc

After the last line add the following three lines. But note that when we installed LaTeX earlier, it maybe landed in a different place. The "2022" and "x86_64-linux" might be different for you. You can run ls -la /usr/local/texlive/*/bin/*/pdflatex to identify the appropriate values.

export PATH=/usr/local/texlive/2022/bin/x86_64-linux:$PATH:/opt/webwork/webwork2/bin
export WEBWORK_ROOT=/opt/webwork/webwork2
export PG_ROOT=/opt/webwork/pg

Then save the file and Quit.

Close your Terminal Window and open a new one so the above changes take effect. You can check that they have by

$ echo $PATH
$ echo $PG_ROOT

Checking Module Dependencies

WeBWorK includes a script called (in the directory /opt/webwork/webwork2/bin) that verifies that the needed programs and Perl modules are installed on your system. Run this script to make sure you have installed the required programs and Perl modules.

$ apache2

You probably see a lot is missing, as indicated by **.

In the executables section, the only thing that should be missing is pdf2svg, which we will not be using. If you see LaTeX executables missing, check that you correctly added the path to LaTeX executables in PATH as described above. If anything else is missing in the executables section, check if it was explicitly mentioned already in this guide, and that you completed those steps of the guide. Otherwise, maybe it just did not come with your OS installation and you should install it. You can search using yum search someExecutable and if found, install it using yum install someExecutable.

Now we will install the missing perl modules. While writing this guide, this missing ones are the ones indicated in the command a few lines below. You might need to modify.

$ sudo perl -MCPAN -e shell

You might be prompted to auto-configure. Say yes. You should be in the cpan shell and see the prompt:


Then run as follows, but compare the list of perl modules to the ones that were missing when you ran check_modules. Also, we are not using DBD::mysql even though that probably was missing. We are, however, going to need DBD::MariaDB, which was maybe not being checked for by check_modules. So include DBD::MariaDB, not DBD::mysql.

This may take a while! Keep an eye on it though because there may be occasional prompts asking if you want to conduct certain tests. Say yes to the tests unless you have a good reason not to.

cpan[1]> install Array::Utils CGI CGI::Cookie Class::Accessor Data::Dump Data::UUID Date::Format Date::Parse DateTime DBD::MariaDB DBI Email::Address::XS Email::Sender::Simple Email::Sender::Transport::SMTP Email::Stuffer Exception::Class File::Find::Rule GD HTML::Entities HTML::Scrubber HTML::Tagset HTML::Template HTTP::Async IO::Socket::SSL Iterator Iterator::Util JSON JSON::MaybeXS Locale::Maketext::Lexicon LWP::Protocol::https Net::IP Net::LDAPS Net::OAuth Net::SSLeay PadWalker Path::Class PHP::Serialization Pod::WSDL SOAP::Lite Statistics::R::IO String::ShellQuote Template Text::CSV Tie::IxHash Time::Zone Types::Serialiser UUID::Tiny XML::Parser XML::Parser::EasyTree XML::Simple XML::Writer XMLRPC::Lite YAML::XS Apache2::Request

Now run check_modules as before to see if something didn't work.

You may see some warning messages like

Prototype mismatch: sub main::from_json: none vs ($@) at (eval 188) line 2.
Prototype mismatch: sub main::to_json: none vs ($@) at (eval 188) line 2.

This seems to be a known bug in libjson-perl and can be safely ignored.

For me, Apache2::Request failed.

install Apache::Test install ExtUtils::XSBuilder

Now we check that all necessary LaTeX packages have been installed. Run the commands

$ cd
$ pdflatex /opt/webwork/webwork2/bin/check_latex.tex

and look for missing packages.

$ sudo su wwadmin
@ cd /opt/webwork/webwork2/conf
@ cp webwork.apache2.4-config.dist webwork.apache2.4-config
@ exit
$ sudo ln -s /opt/webwork/webwork2/conf/webwork.apache2.4-config /etc/httpd/conf.d/webwork.conf

More to come; this page is under construction