perfSONAR User Q&A and Other Discussion

[Mark Feit <>]

This is the first in a series of emails that will highlight useful features of perfSONAR that are new or not widely known.  Today’s tip looks at a pair of commands that can be used to troubleshoot pScheduler.

 

Very basic troubleshooting can be done with the pscheduler ping command, which connects to the pScheduler server on a host and makes sure it answers:

% pscheduler ping ps.example.net

ps.example.net: pScheduler is alive

 

% pscheduler ping alternate-port.example.net:21044

ps.example.net: pScheduler is alive

 

% pscheduler ping down-host.example.net

down-host.example.org: Request timed out

 

% pscheduler ping www.perfsonar.net

www.perfsonar.net: Not running pScheduler

 

 

There is a second command, pscheduler troubleshoot, extends ping’s testing by attempting to run an inert task:

 

% pscheduler troubleshoot

Performing basic troubleshooting of localhost.

Checking for pScheduler on localhost... OK.

Idle test on localhost.... 9 seconds.... OK.

pScheduler appears to be functioning normally.

 

It is also possible to do the same test on a remote host:

 

% pscheduler troubleshoot --host ps.example.net

Performing basic troubleshooting of ps.example.net.

Checking for pScheduler on ps.example.net... OK.

Idle test on ps.example.net.... 7 seconds.... OK.

pScheduler appears to be functioning normally.

 

Additionally, troubleshoot can be used to identify problems between the local host and another, which includes a comparison of their clocks and a simple test that streams a very small amount of data between them:

 

% pscheduler troubleshoot ps.example.net

Performing basic troubleshooting of localhost and ps.example.net.

Checking for pScheduler on localhost... OK.

Checking for pScheduler on ps.example.net... OK.

Idle test on localhost.... 9 seconds.... OK.

Idle test on ps.example.net.... 8 seconds.... OK.

Getting host clocks.... 14 seconds.... OK.

Comparing clocks... OK.

Simple stream test.... 12 seconds.... OK.

pScheduler on both hosts appears to be functioning normally.

 

As above, it is also possible to do the same test against two remote hosts:

 

% pscheduler troubleshoot --host ps1.example.net ps2.example.net

Performing basic troubleshooting of ps1.example.net and ps2.example.net.

Checking for pScheduler on ps1.example.net... OK.

Checking for pScheduler on ps2.example.net... OK.

Idle test on ps1.example.net.... 9 seconds.... OK.

Idle test on ps2.example.net.... 8 seconds.... OK.

Getting host clocks.... 14 seconds.... OK.

Comparing clocks... OK.

Simple stream test.... 12 seconds.... OK.

pScheduler on both hosts appears to be functioning normally.

 

 

Detailed help for ping and troubleshoot are available at the command line by adding the --help switch to the end.