1.0 Installation and configuration > 1.1 TORQUE installation overview > Installing TORQUE

1.1.2 Installing TORQUE

Build the distribution on the machine that will act as the TORQUE server - the machine which monitors and controls all compute nodes by running the pbs_server daemon.

The built distribution package works only on compute nodes of a similar architecture. Nodes with different architecture must have the installation package built on them individually.

To install TORQUE

  1. Download the TORQUE distribution file from http://www.adaptivecomputing.com/support/download-center/torque-download/. You can also download source code using Subversion from the repository at https://github.com/adaptivecomputing/torque/. Use the following command to display all branches:

    2. svn list https://github.com/adaptivecomputing/torque/

    If you're checking source out from SVN, read the README.building-40 file in the repository.

  2. Extract the packaged file and navigate to the unpackaged directory.

    3. > tar -xzvf torque-4.1.4.tar.gz

    > cd torque-4.1.4/

  3. Do the following to configure the package:

    1. Run ./configure. TORQUE has many options you can specify to configure your installation. For more information, see Customizing the install.

      By default, make install installs all files in /usr/local/bin, /usr/local/lib, /usr/local/sbin, /usr/local/include, and /usr/local/man . You can specify an installation prefix other than /usr/local by using --prefix as an argument to ./configure. Note that TORQUE cannot be installed into a directory path that contains a space.

      2. > ./configure

      You may need the libssl-devel and libxml2-devel packages to build 4.1.4. The package names may vary.

  4. Run make and make install.

    5. TORQUE must be installed by a root user. If running sudo fails, switch to root with su -.

    > make

    > sudo make install

    OSX 10.4 users need to change #define __TDARWIN in src/include/pbs_config.h to #define __TDARWIN_8.

  5. After installation, verify that you have the PATH environment variable configured to include /usr/local/bin/ and /usr/local/sbin/.

    6. By default, make install creates a directory at /var/spool/torque. This directory is referred to as TORQUE_HOME. TORQUE_HOME has several sub-directories, including server_priv/, server_logs/, mom_priv/, mom_logs/, and other directories used in the configuration and running of TORQUE.

  6. Verify you have environment variables configured so your system can find the shared libraries and binary files for TORQUE.

    7. To set the library path, add the directory where the TORQUE libraries are installed. For example, if your TORQUE libraries are installed in /usr/local/lib (if you changed the default library path at configure time, use that path instead.), execute the following:

    > echo '/usr/local/lib' > /etc/ld.so.conf.d/torque.conf

    > ldconfig

  7. Initialize serverdb by executing the torque.setup script.

    [root]# ./torque.setup root

  8. Add nodes to the /var/spool/torque/server_priv/nodes file. As an example, the install server was automatically added to the nodes file as a compute node. For information on syntax and options for specifying compute nodes, see Node manager (MOM) configuration.
  9. Configure the MOMs if necessary. See Configuring TORQUE on compute nodes.
  10. Configure pbs_server and pbs_mom to start automatically at system boot, then start their daemons. See Enabling TORQUE as a service.

    If you are upgrading TORQUE from version 2.5.9, start pbs_server with -u the first time after upgrading.

    [root]# pbs_server -u

While Adaptive Computing distributes the RPM files as part of the build, it does not support those files. Not every Linux distribution uses RPM. Adaptive Computing provides a single solution using make and make install that works across all Linux distributions and most UNIX systems. We recognize the RPM format provides many advantages for deployment but it is up to the individual site to repackage the TORQUE installation to match their individual needs.

Related topics 

 

© 2012 Adaptive Computing