(Click to open topic with navigation)
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.
The following software is required to run TORQUE 4.2.7:
Important: If you intend to use TORQUE 4.2.7 with Moab, you must run Moab version 7.1 or later. TORQUE 4.2.7 will not work with versions earlier than Moab 7.1.
To install TORQUE
Install the gcc, libssl-devel, and libxml2-devel packages to build 4.2.7. The package names may vary.
Use these commands to install the packages on the following operating systems:
RHEL, CentOS, and Scientific Linux:
[root]# yum update
[root]# yum install libxml2-devel openssl-devel gcc gcc-c++
SLES (You must have a licensed installation of SuSE and have installed the SuSE Linux Enterprise Software Development Kit and added the ISO to the repository):
[root]# zypper update
[root]# zypper install libxml2-devel libopenssl-devel gcc gcc-c++
For more information on configuring ports, see Configuring Ports.
[root]# git clone https://github.com/adaptivecomputing/torque.git -b 4.2.7 4.2.7
To download a different version, replace each 4.2.7 with the desired version. After downloading a copy of the repository, you can list the current branches by typing git branch -a from within the directory of the branch you cloned.
If you're checking source out from git, read the README.building-40 file in the repository.
[root]# tar -xzvf torque-4.2.7.tar.gz
[root]# cd torque-4.2.7/
If you decide to use --prefix to specify a custom directory and that directory does not already exist, you must create it before running ./configure --prefix=....
[root]# ./configure
TORQUE must be installed by a root user. If running sudo fails, switch to root with su -.
[root]# make
[root]# make install
OSX 10.4 users need to change #define __TDARWIN in src/include/pbs_config.h to #define __TDARWIN_8.
* If Debian distribution, do the following *
[root]# cp contrib/init.d/debian.trqauthd /etc/init.d/trqauthd
* If SLES distribution, do the following *
[root]# cp contrib/init.d/suse.trqauthd /etc/init.d/trqauthd
* If RHEL distribution, do the following *
[root]# cp contrib/init.d/trqauthd /etc/init.d/
[root]# chkconfig --add trqauthd
[root]# echo /usr/local/lib > /etc/ld.so.conf.d/torque.conf
[root]# ldconfig
[root]# service trqauthd start
You will also want to scp the init.d scripts to the compute nodes and install them there.
The TORQUE initialization scripts are provided in the /init.d directory as a courtesy and may be modified at your discretion to work on your system.
[root]# echo <pbs_server's_hostname> > /var/spool/torque/server_name
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.
Verify you have environment variables configured so your system can find the shared libraries and binary files for TORQUE. This step is not necessary if the shared libraries are in their default locations.
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:
[root]# echo '/usr/local/lib' > /etc/ld.so.conf.d/torque.conf
[root]# ldconfig
[root]# ./torque.setup root
If you are upgrading from TORQUE 2.5.9, run pbs_server -u before running torque.setup.
[root]# pbs_server -u
While Adaptive Computing distributes the spec files to create RPMs, it doesn't support RPM installation. 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.
If you have a multi-homed host, or if your host name resolves to the loopback address, you may encounter an "unauthorized request" error when running qmgr. The resolution is to as a manager manually add the host name of the specified interface to the serverdb file with the attributes tag.
<managers>[email protected]</managers>
Related topics