Torque - Revision history

Craigje at 12:54, 3 June 2020

2020-06-03T12:54:52Z

← Older revision		Revision as of 12:54, 3 June 2020
Line 1:		Line 1:
	~~A hub~~ for ~~notes~~ about ~~torque~~.		If you're a sysadmin you want the information about [[Sysadmin:Slurm\|the Slurm scheduler]] instead of Torque. This page is only for reference and to satisfy idle curiosity about how we did this in days of yore.

			= Archival Torque notes =

	== Installing torque ==		== Installing torque ==

Craigje: /* Installing torque */

2019-09-26T18:34:54Z

Installing torque

← Older revision		Revision as of 18:34, 26 September 2019
Line 14:		Line 14:
	**build the client packages and install # both mom and clients as per the webmo link		**build the client packages and install # both mom and clients as per the webmo link
	**qmgr -c �set server scheduling = True�		**qmgr -c �set server scheduling = True�

	**test with <tt>qsub -I</tt>, <tt>qsub --version</tt>, and <tt>pbsnodes -a</tt> (all compute nodes in the last command should be listed as "up")		**test with <tt>qsub -I</tt>, <tt>qsub --version</tt>, and <tt>pbsnodes -a</tt> (all compute nodes in the last command should be listed as "up")
	**reboot server and test again		**reboot server and test again

Craigje: /* Installing torque */

2019-07-08T19:07:16Z

Installing torque

← Older revision		Revision as of 19:07, 8 July 2019
Line 14:		Line 14:
	**build the client packages and install # both mom and clients as per the webmo link		**build the client packages and install # both mom and clients as per the webmo link
	**qmgr -c �set server scheduling = True�		**qmgr -c �set server scheduling = True�
	**test with <tt>qsub -I</tt>, <tt>qsub --version</tt>, and <tt>pbsnodes -a</tt>		**test with <tt>qsub -I</tt>, <tt>qsub --version</tt>, and <tt>pbsnodes -a</tt> (all compute nodes in the last command should be listed as "up")
	**reboot server and test again		**reboot server and test again

Craigje at 19:06, 8 July 2019

2019-07-08T19:06:38Z

@@ Line 1: / Line 1: @@
 A hub for notes about torque.
 == Uninstalling Torque from modules ==
@@ Line 22: / Line 38: @@
 *(aside, fix the python 3.5 install, s/bronte/pollock in setup files, change to correct version (3.6), reset paths)

Craigje at 13:15, 1 July 2019

2019-07-01T13:15:53Z

@@ Line 37: / Line 37: @@
 **qmgr -c �set server scheduling = True�
 **test with qsub -I
 **reboot server and test again

Craigje at 16:52, 25 June 2019

2019-06-25T16:52:18Z

← Older revision		Revision as of 16:52, 25 June 2019
Line 23:		Line 23:
	*(aside, fix the python 3.5 install, s/bronte/pollock in setup files, change to correct version (3.6), reset paths)		*(aside, fix the python 3.5 install, s/bronte/pollock in setup files, change to correct version (3.6), reset paths)

	*install torque		== Installing torque ==
	**(references: https://www.webmo.net/support/torque.html, http://docs.adaptivecomputing.com/torque/6-0-1/help.htm#topics/hpcSuiteInstall/manual/1-installing/installingTorque.htm)		**(references: https://www.webmo.net/support/torque.html, http://docs.adaptivecomputing.com/torque/6-0-1/help.htm#topics/hpcSuiteInstall/manual/1-installing/installingTorque.htm)
	**stop and disable the local firewalld (service stop and service disable)		**stop and disable the local firewalld (service stop and service disable)
Line 39:		Line 39:
	**reboot server and test again		**reboot server and test again

	*install mothur into modules		===install mothur into modules ===
	*(aside, cleanup mess in /mounts/pollock/software/mothur)		*(aside, cleanup mess in /mounts/pollock/software/mothur)
	**download latest version (1.41.3 as of this writing) in source form (NOT binary) into /mounts/pollock/software/mothur		**download latest version (1.41.3 as of this writing) in source form (NOT binary) into /mounts/pollock/software/mothur

Craigje at 13:54, 21 March 2019

2019-03-21T13:54:49Z

← Older revision		Revision as of 13:54, 21 March 2019
Line 6:		Line 6:

	*uninstall torque from modules		*uninstall torque from modules
			**Make a tarball of /mounts/pollock/software/torque and save it to the root or sysadmin directory (this will save you problems)
	**rm -rf /mounts/pollock/software/Modules/MODVER/modulefiles/torque		**rm -rf /mounts/pollock/software/Modules/MODVER/modulefiles/torque
	**rm -rf /mounts/pollock/software/torque		**rm -rf /mounts/pollock/software/torque

Craigje at 18:33, 10 March 2019

2019-03-10T18:33:01Z

← Older revision		Revision as of 18:33, 10 March 2019
Line 1:		Line 1:
	A hub for notes about torque.		A hub for notes about torque.

	# Uninstalling Torque from modules		== Uninstalling Torque from modules ==

	Torque should always be a system program, not a module. These are the steps for pollock, as done by Charlie. Substitute appropriate server names, and note that different systems have different ways of configuring software to launch on system start.		Torque should always be a system program, not a module. These are the steps for pollock, as done by Charlie. Substitute appropriate server names, and note that different systems have different ways of configuring software to launch on system start.

Craigje: Created page with "A hub for notes about torque. # Uninstalling Torque from modules Torque should always be a system program, not a module. These are the steps for pollock, as done by Charlie...."

2019-03-10T18:32:47Z

Created page with "A hub for notes about torque. # Uninstalling Torque from modules Torque should always be a system program, not a module. These are the steps for pollock, as done by Charlie...."

New page

A hub for notes about torque.

# Uninstalling Torque from modules

Torque should always be a system program, not a module. These are the steps for pollock, as done by Charlie. Substitute appropriate server names, and note that different systems have different ways of configuring software to launch on system start.

*uninstall torque from modules
**rm -rf /mounts/pollock/software/Modules/MODVER/modulefiles/torque
**rm -rf /mounts/pollock/software/torque
**check with �module avail�

*uninstall boost from modules
**as above with s/torque/boost/

*install torque dependencies
**yum install libxml2-devel openssl-devel gcc gcc-c++ boost boost-devel

*(aside, install locate, yum install mlocate and updatedb as root)

*(aside, fix modules install, cleanup /etc/bashrc, profile, and profile.d/modules.sh; this fixed the MANPATH problem too)

*(aside, fix the python 3.5 install, s/bronte/pollock in setup files, change to correct version (3.6), reset paths)

*install torque
**(references: https://www.webmo.net/support/torque.html, http://docs.adaptivecomputing.com/torque/6-0-1/help.htm#topics/hpcSuiteInstall/manual/1-installing/installingTorque.htm)
**stop and disable the local firewalld (service stop and service disable)
**download tarball from adaptive computing (v6.0.0.1), unpack, cd
**./configure && make && make install
**check file contents of /var/spool/torque/server_name
**add trqauthd to system startup and start
**./torque.setup root
**setup /var/spool/torque/server_priv/nodes #see http://docs.adaptivecomputing.com/torque/6-0-1/help.htm#topics/torque/1-installConfig/specifyComputeNodes.htm
**add pbs_server to system startup and start
**add pbs_sched to system startup and start
**build the client packages and install # both mom and clients as per the webmo link
**qmgr -c �set server scheduling = True�
**test with qsub -I
**reboot server and test again

*install mothur into modules
**(aside, cleanup mess in /mounts/pollock/software/mothur*)
**download latest version (1.41.3 as of this writing) in source form (NOT binary) into /mounts/pollock/software/mothur
**unpack tarball, rename directory to use version (e.g. 1.41.3) (note this is the pattern to follow for all packages that we maintain multiple versions of) Leave tarball.
**Edit the Makefile # for reference, `diff Makefile Makefile.original`
**make (this takes a bit, -j 4 helps a bit)
**quick test of the resulting binary ./mothur -v
**either make /mounts/pollock/software/Modules/MODVER/modulefiles/mothur or add a version file to it as appropriate
**test with module load mothur and mothur -v