Loading...
Loading...
During the Upgrade, ViPR SRM stops responding and has not progressed on the Frontend after several hours have passed.
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
Allow the system enough time to upgrade, once it determined that the upgrade stopped responding, do the following: Restart all ViPR SRM Hosts Manually upgrade the Host that stopped responding during the upgrade using CLI or Rerun the upgrade through GUI To Manually upgrade a host, run the following: To get a list of modules that still must be updated, run: /opt/APG/bin/manage-modules.sh list One-by-one run, /opt/APG/bin/manage-modules.sh install <module-name> Continue to do this until all the modules have been update on effected hosts Once the host has been upgraded manually, continue the upgrade process by upgrading Solution Packs as suggested by the Upgrade guide.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.