Testing the Worker Node: Difference between revisions
From Gridkaschool
Jump to navigationJump to search
(Created page with "You can test if the required services are running on the worker node by using the netstat command. #netstat -tnlp tcp 0 0 0.0.0.0:15002 0.0.0.0:* LISTEN …") |
(No difference)
|
Latest revision as of 18:25, 28 December 2012
You can test if the required services are running on the worker node by using the netstat command.
#netstat -tnlp tcp 0 0 0.0.0.0:15002 0.0.0.0:* LISTEN /pbs_mom tcp 0 0 0.0.0.0:15003 0.0.0.0:* LISTEN /pbs_mom tcp 0 0 :::22 :::* LISTEN /sshd
Testing the batch system software on the worker node can be done via the momctl command. -d speficies the debug level of the output
# momctl -d 3 Host: XXXX/XXXXXXXXXXXX Version: 2.3.6 PID: 5659 Server[0]: XXXXXXXXXXXXXXXXXXXXXXXXXX (XXX.XXX.XXX.XXX:15001) Init Msgs Received: 0 hellos/1 cluster-addrs Init Msgs Sent: 1 hellos Last Msg From Server: 802 seconds (CLUSTER_ADDRS) Last Msg To Server: 36 seconds HomeDirectory: /var/spool/pbs/mom_priv stdout/stderr spool directory: '/var/spool/pbs/spool/' (1367451 blocks available) NOTE: syslog enabled MOM active: 804 seconds Check Poll Time: 45 seconds Server Update Interval: 45 seconds LogLevel: 0 (use SIGUSR1/SIGUSR2 to adjust) Communication Model: RPP MemLocked: TRUE (mlock) TCP Timeout: 20 seconds Prolog: /var/spool/pbs/mom_priv/prologue (disabled) Alarm Time: 0 of 10 seconds Trusted Client List: [...] Copy Command: /usr/bin/scp -rpB NOTE: no local jobs detected diagnostics complete
Now it is time to go back to here and test the job submission.