cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
748
Views
0
Helpful
1
Replies

WAAS High CPU after upgrade to 5.3.5, 99.0% NICE

james
Level 1
Level 1

So after I upgraded to WAAS version 5.3.5 a lot of the devices have 100% CPU for the next few days!!!!!!!!!!!!!!

 

Sometimes a reboot brings it back down, sometimes not.

Appears to be low priority NICE processes, right?

Would lt-db_verify   be doing a database check?

--------------------------------------------------------------------------------

Cpu(s):  0.3%us,  0.3%sy, 98.7%ni,  0.0%id,  0.0%wa,  0.3%hi,  0.3%si,  0.0%st

 

 

 6138 admin     30  10 68024 2584 2464 R 96.5  0.1 163:38.99 lt-db_verify  

 

 

#sh proc cpu | exc  0      0
Average CPU utilization since reload: 100.00%

CPU utilization since reload:
CPU name     User     Nice   System     Idle   IOwait      IRQ  softIRQ    Steal
    cpu:    0.39%   96.20%    1.72%    1.00%    0.17%    0.08%    0.43%    0.00%
   cpu0:    0.39%   96.20%    1.72%    1.00%    0.17%    0.08%    0.43%    0.00%
Average:    0.31%   97.62%    2.07%    0.00%    0.00%        -        -    0.00%

    User - Percent of CPU time that the system spent in user mode.
    Nice - Percent of CPU time that the system spent on low priority tasks.
  System - Percent of CPU time that the system spent in system mode.
    Idle - Percent of CPU time when the system is idle.
  IOwait - Percent of CPU time when the system is waiting for I/O to complete.
     IRQ - Percent of CPU time when the system is servicing interrupts.
 softIRQ - Percent of CPU time when the system is servicing softirqs.
   Steal - Percent of CPU time that the system spent on involuntary wait.
 Average - Average CPU utilization since reload.

--------------------------------------------------------------------

 PID  STATE PRI User T  SYS T        COMMAND      
----- ----- --- ------ ------ --------------------
    1    S   0   3596    491 (init)
 2069    S   0   2917   5912 (nhm_start.sh)
 2070    S  10  10728   3077 (nodemgr)
 2092    S  10    558     74 (dataserver)
 3310    S  10      2      1  (imd)
 3340    S  10     37     34 (postmaster)
 3348    S  10      2      4 (aoim)
 3349    S  10      6      1 (rbcpd)
 3425    S  10     36     29 (parser_server)
 4490    S  10     29     13 (snmpced)
 4491    S  10      6      6 (sysmon)
 4610    S  10      2      0 (rpc_httpd)
 4719    S  10     12      8 (smartd)
 4790    S  10    102     46 (netcm)
 5019    S  10     56      7  (fda)
 5060    S  10    169    134 (ntpd)
 5063    S  10     66     11 (java)
 5312    S  10     55      7 (sslao)
 5313    S  10    111     13 (epm_adapter)
 5314    S  10     64      9 (ica_ao)
 5315    S  10     65      9 (nfs_ao)
 5316    S  10     65     11 (mapi_ao)
 5318    S  10     57      9 (cifs_start.sh)
 5319    S  10     67      9 (httpmuxd)
 5320    S  10    476     54 (CheckLicenseAnd)
 5321    S  10     65     10 (wsao)
 5323    S  10      3      3 (device_mgr_wrap)
 5324    S  10      1      1 (actastor_wrappe)
 5325    S  10     19      4 (so_dre)
 5431    S  10      5      8 (stats_serialize)
 5433    S  10    903    106 (java)
 5479    S  10     99      8 (srserverd)
 5574    S  10   1342   1075 (so_dre)
 5621    S  10    235     40 (so_dre)
 6039    S  10  17235   4545 (java)
 6088    S  10   3018    731 (java)
 6180    S  10      6      0 (sslao)
 6181    S  10      5      0 (sslao)
 6661    S  10     63     71 (java)
20996    S   0    362    135 (exec)
21881    S  10    202     56 (crond)
WMAOPT001#

1 Reply 1

cschneid
Cisco Employee
Cisco Employee

James,

lt-db_verify is a database verification application.  Does the CPU every drop back down or is it consistent?  Also, what version of code did you upgrade from and what WAE platforms are you seeing this issue on?

Have you opened a TAC case on this yet?

Thanks,

Chip

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: