Symptoms
During the Upgrade ViPR SRM is hung and has not made any progress on the Frontend after several hours have passed.
Cause
Tomcat service was not stopped cleanly, after reviewing the logs, in the Update GUI we found the following:
INFO: The hook is about the reboot the server, exitting...
! WARNING: A more recent version of the module-manager is available. It is strongly recommended to upgrade it before anything else.
* Stopping 'topology-mapping-service Default'... [ OK ]
* Stopping 'tomcat Default'... [ not-running ]
* Stopping 'task-scheduler Default'... [ OK ]
* Stopping 'collector-manager emc-watch4net-health'... [ OK ]
* Stopping 'webservice-gateway Default'... [ OK ]
Oct 06, 2016 11:48:00 AM com.watch4net.apg.webservice.server.HttpServer start
INFO: Creating web service server...
Oct 06, 2016 11:48:00 AM com.watch4net.apg.webservice.server.HttpServer start
Resolution
Please allow the system enough time to upgrade, once it determined that the upgrade is hung, do the following:-restart all ViPR SRM Hosts-Manually upgrade the Host that was hung during the upgrade via CLI or Rerun the upgrade through GUITo Manually upgrade a host run the following:- To get a list modules still needed to updated run,
/opt/APG/bin/manage-modules.sh list
- One-by-one run,
/opt/APG/bin/manage-modules.sh install
-Continue to do this until all the modules have been update on effected hostsOnce the host has been upgraded manually, please continue the upgrade process by upgrading Solution Packs as suggested by the Upgrade guide.
