GUI upgrade for the vOPS virtual appliance going from 5.0 to 5.1 does not complete successfully
Under specific circumstances, a GUI upgrade of 5.0 to 5.1 will display various different error pop ups, even before login on to the GUI web page. Restarting the vOPS services resolve this issue.
To do so:
Log into the console of the virtual appliance, either directly in vSphere Client/Hyper V Manager or establish an ssh connection using a suitable application.
VKernel-vOPS:~ # /usr/local/vkernel/scripts/restartVkServices.sh
Stopping VKernel collector...
Initiated collector shutdown. It will take some time for the running collection tasks to complete.
VKernel collector has been stopped
Stopping VKernel monitor...
VKernel monitor has been stopped
Stopping tomcat...
Using CATALINA_BASE: /usr/local/tomcat
Using CATALINA_HOME: /usr/local/tomcat
Using CATALINA_TMPDIR: /usr/local/tomcat/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar
Tomcat stopped
java: no process found
Shutting down PostgreSQL
Starting PostgreSQL
Starting VKernel collector...
VKernel vOPS Server 5.1. Build: 120709.1709. Schema: 8-11.04
VKernel collector has been started
Starting VKernel monitor...
VKernel vOPS Server 5.1. Build: 120709.1709. Schema: 8-11.04
VKernel monitor has been started
Starting tomcat...
Using CATALINA_BASE: /usr/local/tomcat
Using CATALINA_HOME: /usr/local/tomcat
Using CATALINA_TMPDIR: /usr/local/tomcat/temp
Using JRE_HOME: /usr
Using CLASSPATH: /usr/local/tomcat/bin/bootstrap.jar:/usr/local/tomcat/bin/tomcat-juli.jar
Tomcat started in normal mode
VKernel-vOPS:~ #
© ALL RIGHTS RESERVED. Feedback Terms of Use Privacy Cookie Preference Center