You are here: RPM Installation > Installation and Configuration > Installing Torque Resource Manager

3.7 Installing Torque Resource Manager

If you intend to use Torque Resource Manager 6.1.0 with Moab Workload Manager, you must run Moab version 8.0 or later. However, some Torque functionality may not be available. See Compatibility Requirements in the Moab HPC Suite Release Notes for more information.

This topic contains instructions on how to install, configure, and start Torque Resource Manager (Torque).

For Cray systems, Adaptive Computing recommends that you install Moab and Torque Servers (head nodes) on commodity hardware (not on Cray compute/service/login nodes).

However, you must install the Torque pbs_mom daemon and Torque client commands on Cray login and "mom" service nodes since the pbs_mom must run on a Cray service node within the Cray system so it has access to the Cray ALPS subsystem.

See Installation Notes for Moab and Torque for Cray in the Moab Workload Manager Administrator Guide for instructions on installing Moab and Torque on a non-Cray server.

In this topic:

3.7.1 Open Necessary Ports
3.7.2 Install Torque Server
3.7.3 Install Torque MOMs
3.7.4 Configure Data Management

3.7.1 Open Necessary Ports

If your site is running firewall software on its hosts, you will need to configure the firewall to allow connections to the necessary ports.

Location	Ports	Functions	When Needed
Torque Server Host	15001	Torque Client and MOM communication to Torque Server	Always
Torque MOM Host (Compute Nodes)	15002	Torque Server communication to Torque MOMs	Always
Torque MOM Host (Compute Nodes)	15003	Torque MOM communication to other Torque MOMs	Always

See also:

2.11 Opening Ports in a Firewall for general instructions and an example of how to open ports in the firewall.
Configuring Ports in the Torque Resource Manager Administrator Guide for more information on how to configure the ports that Torque uses for communication.

3.7.2 Install Torque Server

You must complete the prerequisite tasks earlier in this topic before installing the Torque Server. See 3.7 Installing Torque Resource Manager.

On the Torque Server Host, do the following:

If you are installing the Torque Server on its own host (recommend) and not on the same host where you installed another server (such as Moab Server), verify you completed the steps to prepare the host. See 3.3 Preparing for RPM Installs for more information.
Install the Torque Server RPM.
```
[root]# yum install moab-torque-server
```
Source the following file to add the Torque executable directories to your current shell $PATH environment.
```
[root]# . /etc/profile.d/torque.sh
```
Add the hostnames of your Torque MOMs (which is commonly all of your compute nodes) to the /var/spool/torque/server_priv/nodes file. You can remove the hostname entry for the Torque server node unless you will be running a Torque MOM daemon on this host. See Managing Nodes in the Torque Resource Manager Administrator Guide for information on syntax and options for specifying compute nodes.
Example:
```
[root]# vi /var/spool/torque/server_priv/nodes

node01 np=16
node02 np=16
...
```

Start the Torque server.

[root]# service pbs_server start
[root]# service trqauthd start

3.7.3 Install Torque MOMs

In most installations, you will install a Torque MOM on each of your compute nodes.

Do the following:

From the Torque Server Host, copy the hwloc, moab-torque-common, and moab-torque-mom RPM files to each MOM node. It is also recommended that you install the moab-torque-client RPM so you can use client commands and submit jobs from compute nodes.

[root]# scp <dir>/RPMs/hwloc*.rpm <torque-mom-host>:
[root]# scp <dir>/RPMs/moab-torque-common-*.rpm <torque-mom-host>:
[root]# scp <dir>/RPMs/moab-torque-mom-*.rpm <torque-mom-host>:
[root]# scp <dir>/RPMs/moab-torque-client-*.rpm <torque-mom-host>:

On each Torque MOM Host, confirm that cgroups have been mounted; if not, mount them.
1. Run lssubsys -am.
2. If the command is not found, or you do not see something similar to the following, then cgroups are not mounted, continue with these instructions.
```
ns
perf_event
net_prio
cpuset /cgroup/cpuset
cpu /cgroup/cpu
cpuacct /cgroup/cpuacct
memory /cgroup/memory
devices /cgroup/devices
freezer /cgroup/freezer
net_cls /cgroup/net_cls
blkio /cgroup/blkio
```
3. Install the cgroup library package and mount cgroups.
```
[root]# yum install libcgroup
[root]# service cgconfig start
```
4. Run lssubsys -am again and confirm cgroups are mounted.

On each Torque MOM Host, install the RPMs in the order shown.

[root]# yum install hwloc* moab-torque-common-*.rpm moab-torque-mom-*.rpm moab-torque-client-*.rpm

On each Torque MOM Host, create or edit the /var/spool/torque/server_name file to contain the hostname of the Torque server.
```
[root]# echo <torque_server_hostname> > /var/spool/torque/server_name
```
On each Torque MOM Host, edit the /var/spool/torque/mom_priv/config file. This file is identical for all compute nodes and can be created on the Torque Server and distributed in parallel to all systems.
```
[root]# vi /var/spool/torque/mom_priv/config

$logevent      225                        # bitmap of which events to log
```
On each Torque MOM Host, start the pbs_mom daemon.
```
[root]# service pbs_mom start
```
If you installed the Torque Client RPM on the MOMs, then on each Torque MOM Host, start the trqauthd daemon.
```
[root]# service trqauthd start
```

3.7.4 Configure Data Management

When a batch job completes, stdout and stderr files are generated and placed in the spool directory on the master Torque MOM Host for the job instead of the submit host. You can configure the Torque batch environment to copy the stdout and stderr files back to the submit host. See Configuring Data Management in the Torque Resource Manager Administrator Guide for more information.