Versions Compared

Key

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

...

  • 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
    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
    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