AppResponse Upgrade process appears to have stalled or frozen

Categories:
AppResponse (AppResponse Xpert Appliance)
Solution Number:
S26687
Last Modified:
2017-02-21
Issue

 While trying to upgrade to 9.x.x via the WebUI the process appears to have stalled. The installation progress bar on the WebUI had timed out at ~62% complete. It appeared that the installation process might have hung.

Solution

The WebUI progress bar used to track the completion of the update installation ocassionaly times out giving the appearnce that the update /upgrade process has frozen or hung.

If this happens use the process outined below to determine the true status of the update /upgrade process.

  1.  Log into the AppResponse using SSH and check the installed code version by reviewing the output of the release-current command 
cli> release-current 
 
The command output shows the AppResponse is running version 9.6.1. See below for a sample of the release-current command output 
 
xxx.supportlab.nbttech.com> release-current
Release 9.6.1 Version 9.6.201606240910 running on xxx

 

  1. Check the configuration using the top command to determine if the normal processes are running post update . 

cli>top

TOP showed the list of processes we would expect to see on a normally functioning AppResponse.  Here is a sample of what the expected output looks like:
 
       [-U username] [number]
xxx.supportlab.nbttech.com> top
last pid: 41344;  load averages:  0.61,  0.77,  0.82   up 12+08:32:32  16:59:58
727 processes: 1 running, 725 sleeping, 1 zombie
CPU:  0.0% user,  0.0% nice,  0.0% system,  0.0% interrupt,  100% idle
Mem: 15G Active, 4786M Inact, 2892M Wired, 400M Cache, 2047M Buf, 324M Free
Swap: 24G Total, 30M Used, 24G Free
 
  PID USERNAME    THR PRI NICE   SIZE    RES STATE   C   TIME   WCPU COMMAND
 3655 root         27  45    0  1853M  1496M select  0  33.1H 11.04% PilotServe
 2562 root          6  48   r4  3496M  1440M select 10  18.8H  3.52% harvester
 2732 root          1  46    0 89296K 13948K nanslp  9 378:21  1.46% dispatch
 2532 root          1  44    0   411M 34096K nanslp  9  78:55  0.98% atserv
 2729 root          1  46    0 89296K 15508K nanslp  2 379:23  0.59% dispatch
 2540 root          1  44    0   411M 25684K nanslp  0 138:17  0.49% atserv
 2542 root          1  44    0   411M 25660K nanslp  0 138:06  0.49% atserv
 1648 root         57  44    0   137M 64688K select  0  29:28  0.49% python2.7
 2538 root          1  44    0   411M 25704K nanslp  2 138:16  0.39% atserv
 2535 root          1  44    0   411M 25684K nanslp  6 138:05  0.39% atserv
 2539 root          1  44    0   411M 25700K nanslp  7 138:11  0.29% atserv
 2537 root          1  44    0   411M 25696K nanslp  6 138:08  0.29% atserv
 2536 root          1  44    0   411M 25696K nanslp  6 138:08  0.29% atserv
 2541 root          1  44    0   411M 25692K nanslp  9 138:04  0.29% atserv
 4154 root          8  60  r16  2744M  1107M ucond   8 476:09  0.10% mt-hcfesta
 2739 root          1  45    0 89296K 13720K nanslp  0 378:08  0.10% dispatch
xxx.supportlab.nbttech.com>
 
 
 
Based on this information,  the update to version 9.6.1 had completed successfully.
 

Next step: Force a refresh of the WebUI by using the CTL+F5 keyboard combination. 

 
You should see a WeUI login screen.
 
Log into the WebUI.  You should able to confirm the update process had completed and the new version was 9.6.1. 
 
Test launch and log into the Java console from within the WebUI to confirm connectivity functionality. 
 
It appears the update was successful. 
 
 NOTE: these instructions are valid for any update version which is executed from the WebUI.
Environment

 NOTE: these instructions are valid for any update which is executed from the WebUI.

Attachments
NOTICE: Riverbed® product names have changed. Please refer to the Product List for a complete list of product names.
Can't find an answer? Create a case