Installation of the PBSpro client
Looks like you need to built RPMs after you install the server and install client using them.
Unlike torque, pbspro uses
ProstresSQL to store information about nodes, queues, jobs etc. It should be installed as a
prerequisite on the headnode. That means that most information about Torque installation is
not applicable. configuration is also different. In other words this is a different product.
For example, in order to add nodes you need to execute the command qmgr -c "create node
$NODE_HOSTNAME" for each such node. You can do multiple notes in a loop:
while read line; do
[ -n "$line" ] && qmgr -c "create node $line";
done < ./nodefile
where ./nodefile contains the list of nodes, one per line.
You'll find the administration and other guides here:
http://www.pbsworks.com/SupportGT.aspx?d=PBS-Professional,-Documentation113
As usual they are not very useful. Useful posts are mostly scattered in various discussion forums.
In recent version the commercial version of the Installation Guide no longer applies to
the OSS release because the INSTALL script is no longer needed, but you still may find some
(minimal) information in it useful.
PBS Pro does not require a shared filesystem to function unless you are employing the server
failover feature. In this case data store should be on the shared filesystem which is mounted only
on the active headnode.
In
general, you will want to install the RPMs as follows:
- pbspro-server: This should be installed only on the headnode (or two if you employ
failover) in your cluster where the server and scheduler will run. Most admins prefer not to run
jobs on this node, but it is certainly possible. This RPM also installs everything you would get
with the execution and client packages.
- pbspro-execution: This package should be installed on all nodes where you want your
jobs to run. It provides the pbs_mom daemon, but not the server or scheduler. Admins generally
restrict login access to these nodes to prevent users from logging in and impacting running jobs.
This RPM also includes everything you would get with the client package.
- pbspro-client: Allows users to submit and control their jobs. This is
connected with the concept of login nodes: this package should
be installed on nodes where users are allowed login access, like their workstations. It does not
contain any daemons, but allows users to submit and control their jobs.
There are also two optional packages:
- pbspro-debuginfo: Only required when trying to debug an issue via gdb. You won't need this unless
you manage to crash something in PBS Pro that creates a core dump.
- pbspro-*-src: This is the source code for PBS Pro, also used for debugging.
mkaro,
Sep '16
PBS Pro does not require a shared filesystem to function unless you are employing the server failover
feature. Chapter 1 of the installation guide provides some illustrations of possible configurations.
Step 12 in the quick start guide provides some commands you may use to test your PBS Pro configuration.
Running "pbsnodes -a" will show the status of your execution nodes. The state of each node should
be "free" when there are no jobs running.
If user IDs are common across your cluster (perhaps you use NIS, LDAP, etc.) you will want to
enable "flatuid" on the server. If you utilize a shared filesystem on your cluster, you will want
to add "$usecp" to the mom_priv/config files. Details of these and many other features are provided
in the admin guide.
Joey,
Jun '16
Thanks for your reply. I rebuild the CentOS72 rpm with the src from Centos7.zip
- installed pbspro-server-14.1.0-13.1.x86_64.rpm on my headnode
- installed pbspro-execution-14.1.0-13.1.x86_64.rpm on my compute node.
On the head node
create /var/spool/pbs/server_priv/nodes with following:
computenode1 np=1
/etc/pbs.conf:
PBS_SERVER=headnode
PBS_START_SERVER=1
PBS_START_SCHED=1
PBS_START_COMM=1
PBS_START_MOM=0
PBS_EXEC=/opt/pbs
PBS_HOME=/var/spool/pbs
PBS_CORE_LIMIT=unlimited
PBS_SCP=/bin/scp
on the compute node
/var/spool/pbs/mom_priv/config as following
$logevent 0x1ff
$clienthost headnode
$restrict_user_maxsysid 999
/etc/pbs.conf
PBS_SERVER=headnode
PBS_START_SERVER=0
PBS_START_SCHED=0
PBS_START_COMM=0
PBS_START_MOM=1
PBS_EXEC=/opt/pbs
PBS_HOME=/var/spool/pbs
PBS_CORE_LIMIT=unlimited
PBS_SCP=/bin/scp
after that I start the pbs on headnode and compute node without error:
#/etc/init.d/pbs start
But when I try to run pbsnodes -a, it tells me:
pbsnodes: Server has no node list
If I run a script it will just Queue there.
Both server firewalld are turned off and pingable.
Can anyone give me some help? Thanks
subhasisb
Jul '16
Hi @Joey,
Unlike torque, pbspro uses a real relational database underneath to store information about nodes,
queues, jobs etc. Thus creating a nodes file is not supported under pbspro.
To add a node to pbs cluster, use the qmgr command as follows:
qmgr -c "create node hostname"
HTH
regards,
Subhasis
Joey
Jul '16
Thanks for your reply. I thought PBS and torque are the same except one is open source and one
is commercial.
subhasisb
Jul '16
Hi @Joey
They might feel similar since Torque was based on the OpenPBS codebase. OpenPBS was a version
of PBS released as opensource many years back.
Post that, Altair engineering has put in a huge amount of effort towards PBS Professional and
added tons of features and improvements in terms of scalability, robustness and ease of use over
decades which resulted in it becoming the number one work load manager in the HPC world. Altair has
now open-sourced PBS Professional.
So, pbspro is actually very different from torque in terms of capability and performance, and
is actually a completely different product.
Let us know if you need further information in switching to pbspro.
Thanks and Regards,
Subhasis
sxy
Apr 18
Hi Subhasis,
To add a node to pbs cluster, use the qmgr command as follows:
qmgr -c "create node hostname"
if a site has a few hundreds of compute nodes, the above method is very tedious. Would there be any easy/quick ways to register computer nodes with pbs server like the nodes file
in torque?
Thanks,
Sue
mkaro
Apr 18
This is one way to accomplish it...
while read line; do [ -n "$line" ] && qmgr -c "create node $line"; done <nodefile
where nodefile contains the list of nodes, one per line.
Softpanorama Recommended
...
Society
Groupthink :
Two Party System
as Polyarchy :
Corruption of Regulators :
Bureaucracies :
Understanding Micromanagers
and Control Freaks : Toxic Managers :
Harvard Mafia :
Diplomatic Communication
: Surviving a Bad Performance
Review : Insufficient Retirement Funds as
Immanent Problem of Neoliberal Regime : PseudoScience :
Who Rules America :
Neoliberalism
: The Iron
Law of Oligarchy :
Libertarian Philosophy
Quotes
War and Peace
: Skeptical
Finance : John
Kenneth Galbraith :Talleyrand :
Oscar Wilde :
Otto Von Bismarck :
Keynes :
George Carlin :
Skeptics :
Propaganda : SE
quotes : Language Design and Programming Quotes :
Random IT-related quotes :
Somerset Maugham :
Marcus Aurelius :
Kurt Vonnegut :
Eric Hoffer :
Winston Churchill :
Napoleon Bonaparte :
Ambrose Bierce :
Bernard Shaw :
Mark Twain Quotes
Bulletin:
Vol 25, No.12 (December, 2013) Rational Fools vs. Efficient Crooks The efficient
markets hypothesis :
Political Skeptic Bulletin, 2013 :
Unemployment Bulletin, 2010 :
Vol 23, No.10
(October, 2011) An observation about corporate security departments :
Slightly Skeptical Euromaydan Chronicles, June 2014 :
Greenspan legacy bulletin, 2008 :
Vol 25, No.10 (October, 2013) Cryptolocker Trojan
(Win32/Crilock.A) :
Vol 25, No.08 (August, 2013) Cloud providers
as intelligence collection hubs :
Financial Humor Bulletin, 2010 :
Inequality Bulletin, 2009 :
Financial Humor Bulletin, 2008 :
Copyleft Problems
Bulletin, 2004 :
Financial Humor Bulletin, 2011 :
Energy Bulletin, 2010 :
Malware Protection Bulletin, 2010 : Vol 26,
No.1 (January, 2013) Object-Oriented Cult :
Political Skeptic Bulletin, 2011 :
Vol 23, No.11 (November, 2011) Softpanorama classification
of sysadmin horror stories : Vol 25, No.05
(May, 2013) Corporate bullshit as a communication method :
Vol 25, No.06 (June, 2013) A Note on the Relationship of Brooks Law and Conway Law
History:
Fifty glorious years (1950-2000):
the triumph of the US computer engineering :
Donald Knuth : TAoCP
and its Influence of Computer Science : Richard Stallman
: Linus Torvalds :
Larry Wall :
John K. Ousterhout :
CTSS : Multix OS Unix
History : Unix shell history :
VI editor :
History of pipes concept :
Solaris : MS DOS
: Programming Languages History :
PL/1 : Simula 67 :
C :
History of GCC development :
Scripting Languages :
Perl history :
OS History : Mail :
DNS : SSH
: CPU Instruction Sets :
SPARC systems 1987-2006 :
Norton Commander :
Norton Utilities :
Norton Ghost :
Frontpage history :
Malware Defense History :
GNU Screen :
OSS early history
Classic books:
The Peter
Principle : Parkinson
Law : 1984 :
The Mythical Man-Month :
How to Solve It by George Polya :
The Art of Computer Programming :
The Elements of Programming Style :
The Unix Hater’s Handbook :
The Jargon file :
The True Believer :
Programming Pearls :
The Good Soldier Svejk :
The Power Elite
Most popular humor pages:
Manifest of the Softpanorama IT Slacker Society :
Ten Commandments
of the IT Slackers Society : Computer Humor Collection
: BSD Logo Story :
The Cuckoo's Egg :
IT Slang : C++ Humor
: ARE YOU A BBS ADDICT? :
The Perl Purity Test :
Object oriented programmers of all nations
: Financial Humor :
Financial Humor Bulletin,
2008 : Financial
Humor Bulletin, 2010 : The Most Comprehensive Collection of Editor-related
Humor : Programming Language Humor :
Goldman Sachs related humor :
Greenspan humor : C Humor :
Scripting Humor :
Real Programmers Humor :
Web Humor : GPL-related Humor
: OFM Humor :
Politically Incorrect Humor :
IDS Humor :
"Linux Sucks" Humor : Russian
Musical Humor : Best Russian Programmer
Humor : Microsoft plans to buy Catholic Church
: Richard Stallman Related Humor :
Admin Humor : Perl-related
Humor : Linus Torvalds Related
humor : PseudoScience Related Humor :
Networking Humor :
Shell Humor :
Financial Humor Bulletin,
2011 : Financial
Humor Bulletin, 2012 :
Financial Humor Bulletin,
2013 : Java Humor : Software
Engineering Humor : Sun Solaris Related Humor :
Education Humor : IBM
Humor : Assembler-related Humor :
VIM Humor : Computer
Viruses Humor : Bright tomorrow is rescheduled
to a day after tomorrow : Classic Computer
Humor
The Last but not Least Technology is dominated by
two types of people: those who understand what they do not manage and those who manage what they do not understand ~Archibald Putt.
Ph.D
Copyright © 1996-2021 by Softpanorama Society. www.softpanorama.org
was initially created as a service to the (now defunct) UN Sustainable Development Networking Programme (SDNP)
without any remuneration. This document is an industrial compilation designed and created exclusively
for educational use and is distributed under the Softpanorama Content License.
Original materials copyright belong
to respective owners. Quotes are made for educational purposes only
in compliance with the fair use doctrine.
FAIR USE NOTICE This site contains
copyrighted material the use of which has not always been specifically
authorized by the copyright owner. We are making such material available
to advance understanding of computer science, IT technology, economic, scientific, and social
issues. We believe this constitutes a 'fair use' of any such
copyrighted material as provided by section 107 of the US Copyright Law according to which
such material can be distributed without profit exclusively for research and educational purposes.
This is a Spartan WHYFF (We Help You For Free)
site written by people for whom English is not a native language. Grammar and spelling errors should
be expected. The site contain some broken links as it develops like a living tree...
Disclaimer:
The statements, views and opinions presented on this web page are those of the author (or
referenced source) and are
not endorsed by, nor do they necessarily reflect, the opinions of the Softpanorama society. We do not warrant the correctness
of the information provided or its fitness for any purpose. The site uses AdSense so you need to be aware of Google privacy policy. You you do not want to be
tracked by Google please disable Javascript for this site. This site is perfectly usable without
Javascript.
Last modified: March, 29, 2020
