Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • This command checks whether there is a network configuration or an error packet.

    Code Block
    themeDJango
    languagebash
    Shell> netstat -in
    Kernel Interface table
    Iface      MTU    RX-OK RX-ERR RX-DRP RX-OVR    TX-OK TX-ERR TX-DRP TX-OVR Flg
    enp5s0    1500 11116829      0 126934 0         74209      0      0      0 BMRU
    enp7s0    1500        0      0      0 0             0      0      0      0 BMU
    lo       65536  4709762      0      0 0       4709762      0      0      0 LRU

    If a problem occurs between sender and receiver on a packet, the value of R(T)X-ERR/R(T)X-DRP/R(T)X-OVR increases. In this case, there may be some problem on the network, so take measures to have the administrator check.

...

  • This command checks system memory, disk, swap in/out, and CPU status at intervals set by the user.

    Code Block
    themeDJango
    languagebash
    Shell> vmstat 1 5 (Display 5 times per second)
    procs   -----------memory---------- ---swap--  -----io---- -system-- ------cpu-----
     r  b   swpd   free   buff  cache   si   so      bi    bo   in   cs  us sy id wa st
     1  0      0 14407272 377356 472884    0    0     0     1    1    1  0  0 100  0  0
     1  0      0 14405904 377356 472884    0    0     0     0  150  381  0  0 99  0  0
     1  0      0 14406332 377356 472884    0    0     0     0   56  111  0  0 100  0  0
     0  0      0 14406332 377356 472884    0    0     0     0   36   67  0  0 100  0  0
     0  0      0 14407200 377356 472884    0    0     0    16   45  104  0  0 100  0  0

    The main indicators to be checked are as follows.

     Description
    proc rThe number of threads waiting to occupy the CPU. If the value is large, it can be judged that a CPU bottleneck occurs.
    memory freeFree space on physical memory
    swap si, soAn increase of si/so means that disk I/Os between the swap disk and memory are issued
    CPU us sy id wa stChange trends for each item should be observed

...

  • Altibase is developed in the thread structure, and this command is used to check which thread occupies and uses a lot of CPU in some cases.

    Code Block
    themeDJango
    languagebash
    Shell> prstat -L -p <process id> <refresh interval>
    Ex) prstat -L -p 22951 1   (Means to view the process in 1 second)
    PID      USERNAME      SIZE   RSS   STATE  PRI NICE   TIME  CPU   PROCESS/LWPID
    22951    altibase      502M  106M   sleep   59    0   0:22:50   1.7%   altibase/5
    22951    altibase      502M  106M   sleep   59    0   0:23:49   0.3%   altibase/4
    22951    altibase      502M  106M   sleep   59    0   0:00:10   0.1%   altibase/12
    22951    altibase      502M  106M   sleep   59    0   0:00:05   0.1%   altibase/47
    22951    altibase      502M  106M   sleep   59    0   0:25:28   0.0%   altibase/6
    22951    altibase      502M  106M   sleep   59    0   0:22:19   0.0%   altibase/9
    22951    altibase      502M  106M   sleep   59    0   0:23:13   0.0%   altibase/8

...

  • During the technical support, if the user needs to find the cause from outside, SUN should check /var/adm/messages. The file extension means the week the log was recorded, and the log of the week including today is recorded in the messages file.

    Code Block
    themeDJango
    languagebash
    Shell> vi /var/adm/messages
    Feb 24 18:08:24 v880    Corrupt label; wrong magic number
    Feb 24 18:08:24 v880 scsi: [ID 107833 kern.warning] WARNING: /pci@9,700000/fibre-channel@4/fp@0,0/ssd@w210000d023041a42,7 (ssd13):
    Feb 24 18:08:24 v880    Corrupt label; wrong magic number
    Feb 24 18:08:24 v880 scsi: [ID 107833 kern.warning] WARNING: /pci@9,700000/fibre-channel@4/fp@0,0/ssd@w210000d023041a42,7 (ssd13):
    Feb 24 18:08:24 v880    Corrupt label; wrong magic number

    The system log is difficult to understand clearly unless the user is an expert of each vendor, but when providing technical support dude to a failure, etc., make sure to check if there is any important log at a specific time.

...

  • The same results can be checked as SUN's pstack.

    Code Block
    themeDJango
    languagebash
    Shell> procstack <process id>
    ---------- tid# 6901809 (pthread ID:    258) ----------
    0x0900000000062a14  write(??, ??, ??) + 0x1c8
    0x00000001000b9a60  cmnSockSend(cmbBlock*,cmnLinkPeer*,int,PDL_Time_Value*,idvStatIndex)() + 0x308
    0x00000001000b8d38  cmnLinkPeerSendTCP(cmnLinkPeer*,cmbBlock*)() + 0x30
    0x000000010007f28c  cmiWriteBlock(cmiProtocolContext*,idBool)() + 0x24c
    0x000000010007ccc0  cmiFlushProtocol(cmiProtocolContext*,idBool)() + 0xa8
    0x00000001000cd838  mmtServiceThread::executeTask()() + 0xc1c
    0x00000001000cbb80  mmtServiceThread::multiplexingAsShared()() + 0x84
    0x00000001000cc594  mmtServiceThread::run()() + 0x4c4
    0x0000000100077bd4  idtBaseThread::staticRunner(void*)() + 0x28
    0x09000000004a44f4  _pthread_body(??) + 0xdc

    In the same way as the method of interpreting the result of pstack, it is divided into paragraph units based on tid# for each thread and interpreted from bottom to top. In the above result, it can be seen that the transmission part of the communication thread about the result is recorded after a certain query is executed.

...

  • The same results can be checked as SUN's pfiles

    Code Block
    themeDJango
    languagebash
    Shell> pfiles -n <process id>
    1802540 : /home/altibase/altibase_home/bin/altibase -p boot from admin
    Current rlimit: 100 file descriptors
    0: S_IFREG mode:0200 dev:53,1 ino:2731329 uid:222 gid:1 rdev:0,0 O_WRONLY | O_APPEND size:451248  name:/home/altibase/altibase_home/trc/altibase_boot.log 
    1: S_IFREG mode:0222 dev:53,1 ino:2731337 uid:222 gid:1 rdev:0,0 O_WRONLY | O_APPEND size:3014040  name:/home/altibase/altibase_home/trc/altibase_sm.log

    -The used file can also be checked by using the -n option. 

 

 

 

 

 

 

 

 

 

 

 

 

System Log

...

  • It is used to check the system log if an error has occurred in the operating equipment. Since the log for disk device errors, network device errors, or abnormal termination of processes can be checked, the user must check the system log when to find the cause from outside during the technical support.

    Code Block
    themeDJango
    languagebash
    Shell> errpt -a | more
    ---------------------------------------------------------------------------
    LABEL:          CORE_DUMP
    IDENTIFIER:     C69F5C9B
    Date/Time:       Thu Feb 25 03:59:12 KORST 2010
    Sequence Number: 23893
    Machine Id:      00C76BFD4C00
    Node Id:         aix53-p5
    Class:           S
    Type:            PERM
    Resource Name:   SYSPROC         
    Description
    SOFTWARE PROGRAM ABNORMALLY TERMINATED
    Probable Causes
    SOFTWARE PROGRAM

HP-UX

...

  • Depending on the type of HP CPU, it is classified into PA-RISK/ITANIUM, but some commands may not be supported by PA-RISK equipment.

CPU usage by thread with glance

...

  • In the case of HP, CPU usage for each thread can be checked with a monitoring tool called glance.

    Code Block
    themeDJango
    languagebash
    Run through Shell> glance
    If you press the <s> key, you can enter a specific process id.
    If you press the <G> key, you can check the CPU usage for each thread of the process.

pstack

...

  • This shows the same results as SUN's pstack.

    Code Block
    themeDJango
    languagebash
    Shell> pstack <process id>
    --------------------------------  lwpid : 3486042   -------------------------------
    0: c000000000446910 : (unknown) () (unknown)
    1: c0000000001a75a0 : (unknown) () (unknown)
    2: c0000000000e1130 : (unknown) () (unknown)
    3: c0000000000e40c0 : (unknown) () (unknown)
    4: 4000000001330fd0 : rpxSender::sleepForNextConnect()() + 0x3b0 (/home/ckh0618/altibase_home/bin/altibase)
    5: 4000000001340cc0 : rpxSender::attemptHandshake(idBool*)() + 0x4c0 (/home/ckh0618/altibase_home/bin/altibase)
    6: 4000000001326f80 : rpxSender::run()() + 0x1a0 (/home/ckh0618/altibase_home/bin/altibase)
    7: 4000000001e108a0 : idtBaseThread::staticRunner(void*)() + 0x60 (/home/ckh0618/altibase_home/bin/altibase)
    8: c0000000000fa220 : (unknown) () (unknown)

    lwpid means the unique number of the thread. Similarly, paragraphs are separated by lwpid and interpreted from bottom to top. In the above case, the operation to connect the replication Sender Thread with the other party is shown.

     

pfiles

...

  • This shows the same results as SUN's pfiles.

    Code Block
    themeDJango
    languagebash
    Shell> pfiles <process id>
    0: S_ISREG mode:666 dev:64,65537 ino:8490324 uid:124 gid:20 size:530024 flags = O_WRONLY|O_APPEND|O_LARGEFILE file  = /home/ckh0618/altibase_home/trc/altibase_boot.log
    1: S_ISREG mode:666 dev:64,65537 ino:8490373 uid:124 gid:20 size:8466361 flags = O_WRONLY|O_APPEND|O_LARGEFILE file  = /home/ckh0618/altibase_home/trc/altibase_sm.log

System Log

...

  • To check the system log in HP, check as follows.

    Code Block
    themeDJango
    languagebash
    Shell> vi /var/adm/syslog/syslog.log
    Feb 24 10:32:07 rx5670 vmunix:     System Console is on the Built-In Serial Interface
    Feb 24 10:32:07 rx5670 vmunix: igelan0: INITIALIZING HP A6794-60001 PCI 1000Base-T at hardware path 0/1/1/0/4/0
    Feb 24 10:32:07 rx5670 vmunix: Logical volume 64, 0x3 configured as ROOT
    Feb 24 10:32:07 rx5670 vmunix: Logical volume 64, 0x2 configured as SWAP
    Feb 24 10:32:07 rx5670 vmunix: Logical volume 64, 0x2 configured as DUM