15.00 - nodecheck - Teradata Database

Teradata Database Utilities

Product
Teradata Database
Release Number
15.00
Content Type
Configuration
Publication ID
B035-1102-015K
Language
English (United States)
Last Update
2018-09-25

nodecheck

Purpose  

nodecheck is a command‑line diagnostic tool that finds node‑level resource values on the local node. nodecheck provides summary data by node to syscheck for analyses or provides detailed output to the nodecheck log file, which is used later for analysis by syscheck.

Syntax  

 

Syntax Element

Description

-D

Displays threshold values for ‑nodeonly and ‑timercontrol tunables in syscheckrc format.

Use this option to redirect the output to quickly create a syscheckrc file that you can customize. Then use the ‑r rscfile option to read from that customized syscheckrc file.

-f log

Overrides the default log file location as specified in the ‑L option.

The ‑f option must be used with the ‑L option.

The directory path must previously exist. If you specify a file, that file is written. If you specify a directory, then the default filename specified in the ‑L option is written to that directory.

-h

Provides basic help on command line options.

-I

Lists threshold values for ‑nodeonly and ‑timercontrol tunables.

-L

Logs the output to a file in the /tpi‑data directory on the node where nodecheck is run.

The default log filename is nodecheck with an extension indicating the TPA cyclecount at the time of the run (for example, nodecheck.2).

You can specify a specific log filename or location using the ‑f log option. Additional tools are executed during logging mode, but their output is sent only to the resulting file.

-r rscfile

Specifies an additional resource file whose values will override those in the default syscheckrc file (and optional syscheckrc file, if one exists). For information on the syscheckrc file, see “syscheckrc File” on page 886.

-t

Directs nodecheck to read node‑level resource data from one of the following previously created log files.

  • If you use n, nodecheck reads data from the /tpi-data/nodecheck.n file, where n indicates the TPA cyclecount at the time of the run.
  • If you use log, nodecheck reads data from a user-defined path or filename that contains the log information.
  • -v

    Displays the current resource values on the local node, evaluates the resource values, and notifies you of the status of all tunable resources, regardless of level.

    Usage Notes  

    If you invoke nodecheck without any options, then nodecheck does the following:

  • Displays the current resource values on the local node
  • Evaluates the resource values
  • Notifies you of resources which have reached WARN or ALERT levels
  • The defined node‑level resource names and values are located in the ‑nodeonly section of the syscheckrc configuration file. The syscheckrc file is read and processed at the following locations:

  • /usr/pde/etc directory (default)
  • /pde directory (optional)
  • Note: When executed through syscheck, nodecheck will only read and process the local syscheckrc file. This means that changes to the ‑timercontrol section must be propagated to all nodes in order for nodecheck to run similarly on each node.

    Creating a Log File

    To run a single instance of nodecheck, creating a log file for later analysis, do the following:

    ✔ type:

    nodecheck -L -f log 

    where log is the eventual location (a user‑defined path or filename) that contains the log information. nodecheck will still print and evaluate the current resources.

    Example

    The following is an example of running nodecheck with no options.

    nodecheck 
    Reading Node Resources... please wait...
    Which Linux are we:  SuSE
     
    FreeMemory(Pages) and FreeSwap(Blocks)
    /usr/bin/sar -r 2 5
    FREEMEM        13648.5
    FREESWAP       65396880
     
    PDE Msg Daemon Queue length
    /usr/pde/bin/pdeglobal msg -knode
    MSGEVCOUNT     0
     
    BNS Block Queue
    /usr/pde/bin/puma -D BlockStats/d
    BNSBLKQ        0
     
    Available AMP Worker Tasks
    /usr/pde/bin/puma -c
    Count   Vproc
    55      0
    56      1
    56      2
    56      3
    56      4
    56      5
     
    BNS reject% for different Message types
    /usr/pde/bin/tdnstat -a 5 2
    SBR_FCount%    Message Type
    0              RXGRPREC
    0              RXGRPSEG
    0              RXP2PREC
    0              RXP2PSEG
    SegTblFull%    Message Type
    0              RXGRPSEG
    0              RXP2PSEG
     
    Evaluating results... please wait...
     
    No tunables show status of WARN or ALERT

    Example

    The following is an example of running syscheck with the ‑D option to display ‑nodeonly and ‑timercontrol tunables in syscheckrc format.

    nodecheck -D
    -nodeonly
    AMPWT          WARN      -0       ALERT     -0
    BNSBLKQ        WARN      500      ALERT     100
    FREEMEM        WARN      -1000    ALERT     -500
    FREESWAP       WARN      -2000    ALERT     -1000
    MSGEVCOUNT     WARN      100      ALERT     300
    RXMSGFC        WARN      90       ALERT     100
    SEGTBLFULL     WARN      80       ALERT     100
    -timercontrol
    SARSAMPLE      5
    SARSLEEP       2
    TDNSTATSAMPLE  2
    TDNSTATSLEEP   5

    Example

    The following is an example of running syscheck with the ‑I option to display ‑nodeonly and ‑timercontrol tunables.

    nodecheck -I
    Tunable        WARN      ALERT
    AMPWT          <=0       <=0
    BNSBLKQ        >=500     >=100
    FREEMEM        <=1000    <=500
    FREESWAP       <=2000    <=1000
    MSGEVCOUNT     >=100     >=300
    RXMSGFC        >=90      >=100
    SEGTBLFULL     >=80      >=100
    Tunable        Value
    SARSAMPLE      5
    SARSLEEP       2
    TDNSTATSAMPLE  2
    TDNSTATSLEEP   5

    Example

    The following is an example of running nodecheck with the ‑L option.

    nodecheck -L
    Writing to log file: /tpi-data/nodecheck.8
    Reading Node Resources... please wait...
    Which Linux are we:  SuSE
     
    FreeMemory(Pages) and FreeSwap(Blocks)
    /usr/bin/sar -r 2 5
    FREEMEM        13591.25
    FREESWAP        65396880
     
    PDE Msg Daemon Queue length
    /usr/pde/bin/pdeglobal msg -knode
    MSGEVCOUNT     0
     
    BNS Block Queue
    /usr/pde/bin/puma -D BlockStats/d
    BNSBLKQ        0
     
    Available AMP Worker Tasks
    /usr/pde/bin/puma -c
    Count   Vproc
    55      0
    56      1
    56      2
    56      3
    56      4
    56      5
     
    BNS reject% for different Message types
    /usr/pde/bin/tdnstat -a 5 2
    SBR_FCount%    Message Type
    0              RXGRPREC
    0              RXGRPSEG
    0              RXP2PREC
    0              RXP2PSEG
    SegTblFull%    Message Type
    0              RXGRPSEG
    0              RXP2PSEG
     
    Evaluating results... please wait...
     
    No tunables show status of WARN or ALERT

    Example

    The following is an example of running nodecheck with the -v option.

    nodecheck -v
    Reading Node Resources... please wait...
    Which Linux are we:  SuSE
     
    FreeMemory(Pages) and FreeSwap(Blocks)
    /usr/bin/sar -r 2 5
    FREEMEM        13319.5
    FREESWAP       65396880
     
    PDE Msg Daemon Queue length
    /usr/pde/bin/pdeglobal msg -knode
    MSGEVCOUNT     0
     
    BNS Block Queue
    /usr/pde/bin/puma -D BlockStats/d
    BNSBLKQ        0
     
    Available AMP Worker Tasks
    /usr/pde/bin/puma -c
    Count   Vproc
    55      0
    56      1
    56      2
    56      3
    56      4
    56      5
     
    BNS reject% for different Message types
    /usr/pde/bin/tdnstat -a 5 2
    SBR_FCount%    Message Type
    0              RXGRPREC
    0              RXGRPSEG
    0              RXP2PREC
    0              RXP2PSEG
    SegTblFull%    Message Type
    0              RXGRPSEG
    0              RXP2PSEG
     
    Evaluating results... please wait...
     
    Resource                    Current   Current   Threshold  Vproc Number/
    Description                 Level     Value     Value      Message Type
     
    FreeMemory(Pages)           OK        13319.5
    FreeSwap(Blocks)            OK        65396880
    PDE Msg Daemon Queue Length OK        0
    BNS Block Queue Length      OK        0
    Available AMP Worker Tasks  OK        55                   0
    Available AMP Worker Tasks  OK        56                   1
    Available AMP Worker Tasks  OK        56                   2
    Available AMP Worker Tasks  OK        56                   3
    Available AMP Worker Tasks  OK        56                   4
    Available AMP Worker Tasks  OK        56                   5
    BNS Msg Reject%(FC)         OK        0                    RXGRPREC
    BNS Msg Reject%(FC)         OK        0                    RXGRPSEG
    BNS Msg Reject%(FC)         OK        0                    RXP2PREC
    BNS Msg Reject%(FC)         OK        0                    RXP2PSEG
    BNS Msg Reject%(SEGTBLFULL) OK        0                    RXGRPSEG
    BNS Msg Reject%(SEGTBLFULL) OK        0                    RXP2PSEG

    Example

    The following is an example of running nodecheck with the ‑v option and reading output from a previously generated log file. The TPA cyclecount is specified to gain access to the recently created default log file.

    nodecheck -t 8 -v
    Reading from log file: /tpi-data/nodecheck.8
    Which Linux are we:  SuSE
     
    FreeMemory(Pages) and FreeSwap(Blocks)
    /usr/bin/sar -r 2 5
    FREEMEM        13591.25
    FREESWAP       65396880
     
    PDE Msg Daemon Queue length
    /usr/pde/bin/pdeglobal msg -knode
    MSGEVCOUNT     0
     
    BNS Block Queue
    /usr/pde/bin/puma -D BlockStats/d
    BNSBLKQ        0
     
    Available AMP Worker Tasks
    /usr/pde/bin/puma -c
    Count   Vproc
    55      0
    56      1
    56      2
    56      3
    56      4
    56      5
     
    BNS reject% for different Message types
    /usr/pde/bin/tdnstat -a 5 2
    SBR_FCount%    Message Type
    0              RXGRPREC
    0              RXGRPSEG
    0              RXP2PREC
    0              RXP2PSEG
    SegTblFull%    Message Type
    0              RXGRPSEG
    0              RXP2PSEG
     
    Evaluating results... please wait...
     
    Resource                 Current     Current   Threshold   Vproc Number/
    Description              Level       Value     Value       Message Type
     
    FreeMemory(Pages)            OK       13591.25
    FreeSwap(Blocks)             OK       65396880
    PDE Msg Daemon Queue Length  OK       0
    BNS Block Queue Length       OK       0
    Available AMP Worker Tasks   OK       55                    0
    Available AMP Worker Tasks   OK       56                    1
    Available AMP Worker Tasks   OK       56                    2
    Available AMP Worker Tasks   OK       56                    3
    Available AMP Worker Tasks   OK       56                    4
    Available AMP Worker Tasks   OK       56                    5
    BNS Msg Reject%(FC)          OK       0                     RXGRPREC
    BNS Msg Reject%(FC)          OK       0                     RXGRPSEG
    BNS Msg Reject%(FC)          OK       0                     RXP2PREC
    BNS Msg Reject%(FC)          OK       0                     RXP2PSEG
    BNS Msg Reject%(SEGTBLFULL)  OK       0                     RXGRPSEG
    BNS Msg Reject%(SEGTBLFULL)  OK       0                     RXP2PSEG

    Messages

    nodecheck displays the following types of messages.

     

    The message...

    Appears...

    Error

    nodecheck encounters any error to extract the resource value.

    An Error message could occur if nodecheck cannot find or execute the related PDE tool to extract the resource value. If STDERR output exists, it displays.

    Warning

    invalid information is found during processing of the syscheckrc file or for other reasons.