After the MC was updated from 10.0.1 to 10.1.0 MC was deconfigured
Hi
Centos7
Vertica MC was configured on 10.0.1
Then updated it to 10.1.0
And after that, MC was deconfigured (the configuration wizard pops up).
Here it states that:
- If MC was not previously configured, the Configuration Wizard dialog box appears. Configuration steps are described in Configuring MC.
If MC was previous configured, Vertica prompts you to accept the end-user license agreement (EULA) when you first log in to MC after the upgrade.
So the login windows should have been popped up.
Here is the log of that update:
yum install vertica-console-10.1.0-0.x86_64.RHEL6.rpm
Loaded plugins: fastestmirror, rhnplugin
This system is receiving updates from RHN Classic or Red Hat Satellite.
Examining vertica-console-10.1.0-0.x86_64.RHEL6.rpm: vertica-console-10.1.0-0.x86_64
Marking vertica-console-10.1.0-0.x86_64.RHEL6.rpm as an update to vertica-console-10.0.1-0.x86_64
Resolving Dependencies
--> Running transaction check
---> Package vertica-console.x86_64 0:10.0.1-0 will be updated
---> Package vertica-console.x86_64 0:10.1.0-0 will be an update
--> Finished Dependency ResolutionDependencies Resolved
Package Arch Version Repository Size
Updating:
vertica-console x86_64 10.1.0-0 /vertica-console-10.1.0-0.x86_64.RHEL6 1.2 GTransaction Summary
Upgrade 1 Package
Total size: 1.2 G
Is this ok [y/d/N]: y
Downloading packages:
Running transaction check
Running transaction test
Transaction test succeeded
Running transaction
[preinstall] Starting installation....
[preinstall] Backing up derby database
[preinstall] Backing up config directory
‘/opt/vconsole/config’ -> ‘/opt/vconsole/config.bak’
Updating : vertica-console-10.1.0-0.x86_64 1/2[postinstall] copy vertica-consoled
Unknown operation 'daemon_reload'.
mkdir: cannot create directory ‘tools’: File exists
Cleaning up temp folder...
Starting the vertica management console....
Vertica Console: 2021-02-26 09:50:51.074:INFO::main: Logging initialized @126ms to org.eclipse.jetty.util.log.StdErrLog
2021-02-26 09:50:51.078:INFO:cv.Startup:main: Attempting to load properties from /opt/vconsole/config/console.properties
2021-02-26 09:50:51.081:INFO:cv.Startup:main: Starting Server...
2021-02-26 09:50:51.168:INFO:cv.Startup:main: starting monitor thread
2021-02-26 09:50:51.172:INFO:oejs.Server:main: jetty-9.4.z-SNAPSHOT; built: 2019-04-29T20:42:08.989Z; git: e1bc35120a6617ee3df052294e433f3a25ce7097; jvm 1.8.0_212-b04
2021-02-26 09:50:54.411:INFO:oejshC.webui:main: No Spring WebApplicationInitializer types detected on classpath
2021-02-26 09:50:54.451:INFO:oejs.session:main: DefaultSessionIdManager workerName=node0
2021-02-26 09:50:54.451:INFO:oejs.session:main: No SessionScavenger set, using defaults
2021-02-26 09:50:54.452:INFO:oejs.session:main: node0 Scavenging every 660000ms
2021-02-26 09:50:54.455:INFO:oejshC.webui:main: Initializing Spring root WebApplicationContext
---- Upgrading /opt/vconsole/config/console.properties ----Please open the Vertica Management Console at https://hostname:5450/webui
2021-02-26 09:51:07.076:WARN:oeju.DeprecationWarning:main: Using @Deprecated Class org.eclipse.jetty.servlets.GzipFilter
2021-02-26 09:51:07.077:WARN:oejs.GzipFilter:main: GzipFilter is deprecated. Use GzipHandler
2021-02-26 09:51:07.105:INFO:oejshC.webui:main: Initializing Spring DispatcherServlet 'appServlet'
Feb 26, 2021 9:51:07 AM org.hibernate.validator.internal.util.Version
INFO: HV000001: Hibernate Validator 5.1.3.Final
2021-02-26 09:51:07.935:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@11678469{/webui,file:///opt/vconsole/temp/webapp/,AVAILABLE}{file:/opt/vconsole/lib/webui.war}
2021-02-26 09:51:07.946:INFO:oejus.SslContextFactory:main: x509=X509@2faae7f6(selfsigned,h=[],w=[]) for Server@673a5aa7[provider=null,keyStore=file:///opt/vconsole/config/keystore.jks,trustStore=null]
2021-02-26 09:51:07.966:INFO:oejs.AbstractConnector:main: Started ServerConnector@7de26db8{SSL,[ssl, http/1.1]}{0.0.0.0:5450}
2021-02-26 09:51:07.967:INFO:oejs.Server:main: Started @17020ms
2021-02-26 09:51:07.967:INFO:cv.Startup:main: STARTING jetty server
start OK
[postinstall] Changing permissions of /opt/vconsole
Cleanup : vertica-console-10.0.1-0.x86_64 2/2
Verifying : vertica-console-10.1.0-0.x86_64 1/2
Verifying : vertica-console-10.0.1-0.x86_64 2/2Updated:
vertica-console.x86_64 0:10.1.0-0Complete!
Regards
Raul