1.0 Installation and configuration > 1.6 Testing server configuration

1.6 Testing server configuration

If you have initialized TORQUE using the torque.setup script or started TORQUE using pbs_server -t create and pbs_server is still running, terminate the server by calling qterm. Next, start pbs_server again without the -t create arguments. Follow the script below to verify your server configuration. The output for the examples below are based on the nodes file example in Specifying node features and Server configuration.

# verify all queues are properly configured

> qstat -q

 

server:kmn

 

Quere   Memory   CPU Time   Walltime   Node   Run  Que  Lm  State

-----   ------   --------   --------   ----   ---  ---  --  -----

batch   --        --        --         --     0    0    --  ER

                                              ---  ---

                                              0    0

 

# view additional server configuration

> qmgr -c 'p s'

#

# Create queues and set their attributes

#

#

# Create and define queue batch

#

create queue batch

set queue batch queue_type = Execution

set queue batch resources_default.nodes = 1

set queue batch resources_default.walltime = 01:00:00

set queue batch enabled = True

set queue batch started = True

#

# Set server attributes.

#

set server scheduling = True

set server acl_hosts = kmn

set server managers = [email protected]

set server operators = [email protected]

set server default_queue = batch

set server log_events = 511

set server mail_from = adm

set server scheduler_iteration = 600

set server node_check_rate = 150

set server tcp_timeout = 300

set server job_stat_rate = 45

set server poll_jobs = True

set server mom_job_sync = True

set server keep_completed = 300

set server next_job_number = 0

 

# verify all nodes are correctly reporting

> pbsnodes -a

node001

  state=free

  np=2

  properties=bigmem,fast,ia64,smp

  ntype=cluster

  status=rectime=1328810402,varattr=,jobs=,state=free,netload=6814326158,gres=,loadave=0.21,ncpus=6,physmem=8193724kb,

availmem=13922548kb,totmem=16581304kb,idletime=3,nusers=3,nsessions=18,sessions=1876 1120 1912 1926 1937 1951 2019 2057 28399 2126 2140 2323 5419 17948 19356 27726 22254 29569,uname=Linux kmn 2.6.38-11-generic #48-Ubuntu SMP Fri Jul 29 19:02:55 UTC 2011 x86_64,opsys=linux

  mom_service_port = 15002

  mom_manager_port = 15003

  gpus = 0

# submit a basic job - DO NOT RUN AS ROOT

> su - testuser

> echo "sleep 30" | qsub

 

# verify jobs display

> qstat

 

Job id   Name   User      Time Use  S  Queue

------   -----  ----      --------  -- -----

0.kmn    STDIN  knielson         0  Q  batch

At this point, the job should be in the Q state and will not run because a scheduler is not running yet. TORQUE can use its native scheduler by running pbs_sched or an advanced scheduler (such as Moab Workload Manager). See Integrating schedulers for details on setting up an advanced scheduler.

Related topics