Warning

There are known security vulnerabilities in Open XDMoD versions ≤11.0.2. We strongly encourage upgrading immediately to the latest version of Open XDMoD, 11.0.3, which contains fixes for these vulnerabilities.

To upgrade version 9.0 to 11.0.3, you will first need to upgrade to version 9.5.0, then upgrade to version 10.0.3, then upgrade to version 10.5.1, then upgrade to version 11.0.3.

If you cannot upgrade immediately, you can follow the instructions below to manually patch your installation as a temporary workaround before upgrading later.

Workaround instructions
  1. First, make sure you are on the correct web page for your version of Open XDMoD. The web page you are on now is for version 9.0. Other versions' pages are linked below:
  2. Download the patch file for your version:
  3. Copy the patch file to your Open XDMoD web server.
  4. Make sure you have the patch command installed; it can be installed with dnf install patch.
  5. Apply the patch by running the command below, replacing [PATH_TO_XDMOD_SHARE_DIR] with the path to the share directory (/usr/share/xdmod for RPM-based installs, /opt/xdmod/share or another location for source code installs) and replacing [PATH_TO_PATCH_FILE] with the path to the patch file. 
    # patch -p1 -d [PATH_TO_XDMOD_SHARE_DIR] < [PATH_TO_PATCH_FILE]
    NOTE: A previous version of this web page instructed you to manually patch the file classes/Realm/GroupBy.php. If you did so, you will see the following prompt: 
    patching file classes/Realm/GroupBy.php
    Reversed (or previously applied) patch detected!  Assume -R? [n]
    Make sure to choose n, and when it asks "Apply anyway? [n]", choose n again.
  6. Upgrade to the latest version of Open XDMoD as soon as you can.

Installing → Installation Guides → RPM Installation Guide

Install Prerequisites

See the Software Requirements for details.

Install the RPM

# yum install xdmod-9.0.0-1.0.el7.noarch.rpm

Configure Open XDMoD

Be sure MySQL is running before using the setup command.

# xdmod-setup

See the Configuration Guide for more details.

Shred Data

Depending on which resource manager you use, your accounting logs may be stored in a single file, a directory containing multiple files or in a database that is queried using a specific command. Each of these is handled with different options in Open XDMoD.

See the Shredder Guide and the resource manager notes for more details.

PBS stores its accounting logs in a directory where the name of each file corresponds to the end date of the jobs it contains. A directory such as this can be specified using the -d option:

$ xdmod-shredder -v -r *resource* -f pbs \
      -d /var/spool/pbs/server_priv/accounting

SGE stores its accounting logs in a single file so the -i (input) option should be used:

$ xdmod-shredder -v -r *resource* -f sge \
      -i /var/lib/gridengine/default/common/accounting

Slurm stores its accounting logs in a database that can be queried using the sacct command. Since the accounting data is not directly accessible in files Open XDMoD provides a helper script that writes the data to a file and then shreds that file:

$ xdmod-slurm-helper -v -r *resource*

The resource name here must match the one supplied to the setup script.

NOTE: This command only works if Open XDMoD is on a machine with the sacct command or if you have configured your portal_settings.ini file with a command that accepts the same arguments as sacct (such as using ssh with a public key to run the command on another machine).

Ingest Data

See the Ingestor Guide for more details.

Reload Apache

# systemctl reload httpd.service

Now you should be able to view the Open XDMoD portal at the URL used during the configuration process.