qping

• Introduction
• Parameters
• Options
• Examples

Introduction

Utility qping is used to validate the runtime status of a Sun Grid Engine service daemon. The current Sun Grid Engine implementation allows one to query the SGE_QMASTER daemon and any running SGE_EXECD daemon. The qping command is used to send a SIM (Status Information Message) to the destination daemon.

The communication layer of the specified daemon will respond with a SIRM (Status Information Response Message) which contains status information about the consulted daemon.

The qping -dump and -dump_tag options allowing an administrator to observe the communication protocol data flow of a Sun Grid Engine service daemon. The qping -dump instruction must be started with root account and on the same host where the observed daemon is running.

qping mysite54
OGE 6.2u7
usage: qping [-help] [-noalias] [-ssl|-tcp] [ [ [-i ] [-info] [-f] ] | [ [-dump_tag tag [param] ] [-dump] [-nonewline] ] ]    
   -i         : set ping interval time
   -info      : show full status information and exit
   -f         : show full status information on each ping interval
   -noalias   : ignore $SGE_ROOT/SGE_CELL/common/host_aliases file
   -ssl       : use SSL framework
   -tcp       : use TCP framework
   -dump      : dump communication traffic (see "communication traffic output options" for additional information)
                   (provides the same output like -dump_tag MSG)
   -dump_tag  : dump communication traffic (see "communication traffic output options" for additional information)
                   tag=ALL  - show all
                   tag=APP  - show application messages
                   tag=MSG               - show commlib protocol messages
                            - ERROR, WARNING, INFO, DEBUG or DPRINTF
   -nonewline : dump output will not have a linebreak within a message
   -help      : show this info
   host       : host name of running component
   port       : port number of running component
   name       : name of running component (e.g.: "qmaster" or "execd")
   id         : id of running component (e.g.: 1 for daemons)

Parameters

1. host Host where daemon is running.
2. port Port which daemon has bound (should be sge_qmaster/sge_execd port number). Typically 6445 <
3. name  ("qmaster" or "execd")
4. id Id of communication endpoint ("1" for daemons) 

Options

Prints a list of all options.

-i interval

Set qping interval time.

The default interval time is one second. Qping will send a SIM (Status Information Message) on each interval time.

-info

Show full status information (see -f for more information) and exit. The exit value 0 indicates no error. On errors qping returns with 1.

-noalias

Ignore host_aliases file, which is located at <sge_root>/<cell>/common/host_aliases. If this option is used it is not necessary to set any Sun Grid Engine environment variable.

-ssl

This option can be used to specify an SSL (Secure Socket Layer) configuration. The qping will use the configuration to connect to services running SSL. If the SGE settings file is not sourced, you have to use the -noalias option to bypass the need for the SGE_ROOT environment variable. The following environment variables are used to specify your certificates: SSL_CA_CERT_FILE - CA certificate file SSL_CERT_FILE - certificates file SSL_KEY_FILE - key file SSL_RAND_FILE - rand file

-tcp

This option is used to select TCP/IP as the protocol used to connect to other services.

-nonewline

Dump output will not have a linebreak within a message and binary messages are not unpacked.

-dump

This option allows an administrator to observe the communication protocol data flow of a Sun Grid Engine service daemon. The qping -dump instruction must be started as root and on the same host where the observed daemon is running.

The output is written to stdout. The environment variable "SGE_QPING_OUTPUT_FORMAT" can be set to hide columns, set a default column width or to set a hostname output format. The value of the environment variable can be set to any combination of the following specifiers separated by a space character:

"h:X"   -> hide column X
"s:X"   -> show column X
"w:X:Y" -> set width of column X to Y
"hn:X"  -> set hostname output parameter X.
           X values are "long" or "short"

Start qping -help to see which columns are available.

-dump_tag tag [param]

This option has the same the same meaning as -dump, but can provide more information by specifying the debug level and message types qping should print:

-dump_tag ALL <debug level>

This option shows all possible debug messages (APP+MSG) for the debug levels, ERROR, WARNING, INFO, DEBUG and DPRINTF. The contacted service must support this kind of debugging. This option is not currently implemented.

-dump_tag APP <debug level>

This option shows only application debug messages for the debug levels, ERROR, WARNING, INFO, DEBUG and DPRINTF. The contacted service must support this kind of debugging. This option is not currently implemented.

-dump_tag MSG

This option has the same behavior as the -dump option.

Examples

qping -info master 6444 qmaster 1 # check status of master from the node

[0]root@master1: # qping -info master1 6444 qmaster 1
11/06/2014 21:57:43:
SIRM version:             0.1
SIRM message id:          1
start time:               11/06/2014 21:01:22 (1415325682)
run time [s]:             3338
messages in read buffer:  0
messages in write buffer: 0
no. of connected clients: 2
status:                   0
info:                     MAIN: R (3337.61) | signaler000: R (3337.57) | event_master000: R (0.45) | timer000: R (8.45) | worker000: R (23.45) | worker001: R (23.45) | listener000: R (3.36) | listener001: R (1.36) | scheduler000: R (8.45) | OK
Monitor:                  disabled

qping -info myhost16 6445 execd 1         # check status of execd from master NOTE execd 1

Communication traffic output options

h:X   -> hide column X
s:X   -> show column X
w:X:Y -> set width of column X to Y
hn:X  -> set hostname output parameter X. X values are "long" or "short"

   nr active name      description
   == ====== ====      ===========
   01 yes    time      time of debug output creation
   02 yes    local     endpoint service name where debug client is connected
   03 yes    d.        message direction
   04 yes    remote    name of participating communication endpoint
   05 yes    format    message data format
   06 yes    ack type  message acknowledge type
   07 yes    msg tag   message tag information
   08 yes    msg id    message id
   09 yes    msg rid   message response id
   10 yes    msg len   message length
   11 yes    msg time  time when message was sent/received
   12  no    msg dump  message content dump (xml/bin/cull)
   13  no    info      additional information
   14 yes    msg ltime commlib linger time
   15 yes    con count nr. of connections
ERROR! no option argument

Recommended Links

Softpanorama Recommended

Top articles

Sites

Top articles

Sites

qping(1) - Linux man page

UGE Manual Pages

Grid Engine Documentation

Etc

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

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, 12, 2019