Unable to import existing database from Management console
mqazi
Community Edition User
I installed a MC 10.0.1-0 and trying to import a 9.2.1 database. When I put IP in Gui to import, it prompts that IP is not reachable. MC logs show it is trying to reach database on ssh port 22 which is blocked. Shouldn't MC connect to agent on port 5444. Is it possible that I can put a custom port for connectivint
==== =========================MC LOG ===========================
30 Nov 2020 21:41:47,092 [qtp636718812-100] VuiUtils INFO - Check host:100.120.87.200 reachable via port 22
30 Nov 2020 21:41:47,094 [qtp636718812-100] VuiUtils INFO - Exception when try to reach host: via port 22 - Connection refused (Connection refused)
==== =============Vertica Console Service Running on MC =================
root@psp6ninms02:/opt/vconsole/log/mc# systemctl status vertica-consoled.service
‚óè vertica-consoled.service - LSB: Startup/shutdown script for the Micro Focus Vertica Management Console
Loaded: loaded (/etc/init.d/vertica-consoled; generated)
Active: active (running) since Mon 2020-11-30 16:42:23 UTC; 5h 7min ago
Docs: man:systemd-sysv-generator(8)
Process: 32779 ExecStart=/etc/init.d/vertica-consoled start (code=exited, status=0/SUCCESS)
Tasks: 82 (limit: 9450)
Memory: 1.2G
CGroup: /system.slice/vertica-consoled.service
└─32801 /opt/vconsole/vendor/OpenJDK/Zulu/java/1.8u212/jre//bin/java -Djava.net.preferIPv4Stack=true -Djava.net.preferIPv4Addresses=true -Duser.language=>
Nov 30 16:42:22 psp6ninms02 vertica-consoled[32825]: INFO: HV000001: Hibernate Validator 5.1.3.Final
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32825]: 2020-11-30 16:42:23.054:INFO:oejsh.ContextHandler:main: Started o.e.j.w.WebAppContext@ce2eaa7{/webui,file:///opt/>
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32825]: 2020-11-30 16:42:23.059:INFO:oejus.SslContextFactory:main: x509=X509@7fc1fd31(selfsigned,h=[],w=[]) for Server@75>
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32825]: 2020-11-30 16:42:23.080:INFO:oejs.AbstractConnector:main: Started ServerConnector@33833882{SSL,[ssl, http/1.1]}{0>
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32825]: 2020-11-30 16:42:23.080:INFO:oejs.Server:main: Started @12984ms
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32825]: 2020-11-30 16:42:23.080:INFO:cv.Startup:main: STARTING jetty server
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32779]: start OK
Nov 30 16:42:23 psp6ninms02 vertica-consoled[32779]: *
Nov 30 16:42:23 psp6ninms02 systemd[1]: Started LSB: Startup/shutdown script for the Micro Focus Vertica Management Console.
Nov 30 16:42:23 psp6ninms02 sudo[32746]: pam_unix(sudo:session): session closed for user root
root@psp6ninms02:/opt/vconsole/log/mc#
https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/InstallationGuide/BeforeYouInstall/PortAvailability.htm
Comments
@mqazi MC requests port 22 and we have mentioned in the the documentation.
https://www.vertica.com/docs/9.2.x/HTML/Content/Authoring/InstallationGuide/InstallingMC/BeforeYouInstallManagementConsole.htm
@SruthiA Is it possible to customize it to some other port? I tested in on other ubuntu server treated as MC server. Initial echo was done followed by connection on 5444 port
dbadmin@ubuntu-server:~$ sudo tcpdump -i any host 67.219.117.3 -nn
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on any, link-type LINUX_SLL (Linux cooked v1), capture size 262144 bytes
23:39:51.203221 IP 192.168.0.52.57032 > 67.219.117.3.7**: Flags [S], seq 2396056077, win 64240, options [mss 1460,sackOK,TS val 3735558930 ecr 0,nop,wscale 7], length 0
23:39:51.300638 IP 67.219.117.3.7 > 192.168.0.52.57032: Flags [R.], seq 0, ack 2396056078, win 0, length 0
23:39:51.326861 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [S], seq 2042144488, win 64240, options [mss 1460,sackOK,TS val 3735559054 ecr 0,nop,wscale 7], length 0
23:39:51.420927 IP 67.219.117.3.5444 > 192.168.0.52.55396: Flags [S.], seq 2061482323, ack 2042144489, win 28960, options [mss 1460,sackOK,TS val 1004546957 ecr 3735559054,nop,wscale 7], length 0
23:39:51.421002 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [.], ack 1, win 502, options [nop,nop,TS val 3735559148 ecr 1004546957], length 0
23:39:51.422829 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [P.], seq 1:205, ack 1, win 502, options [nop,nop,TS val 3735559150 ecr 1004546957], length 204
23:39:51.555686 IP 67.219.117.3.5444 > 192.168.0.52.55396: Flags [.], ack 205, win 235, options [nop,nop,TS val 1004547054 ecr 3735559150], length 0
23:39:51.555900 IP 67.219.117.3.5444 > 192.168.0.52.55396: Flags [P.], seq 1:743, ack 205, win 235, options [nop,nop,TS val 1004547055 ecr 3735559150], length 742
23:39:51.555908 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [.], ack 743, win 501, options [nop,nop,TS val 3735559283 ecr 1004547055], length 0
23:39:51.556959 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [P.], seq 205:344, ack 743, win 501, options [nop,nop,TS val 3735559284 ecr 1004547055], length 139
23:39:51.557165 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [P.], seq 344:350, ack 743, win 501, options [nop,nop,TS val 3735559284 ecr 1004547055], length 6
23:39:51.557314 IP 192.168.0.52.55396 > 67.219.117.3.5444: Flags [P.], seq 350:435, ack 743, win 501, options [nop,nop,TS val 3735559284 ecr 1004547055], length 85
23:39:51.641937 IP 67.219.117.3.5444 > 192.168.0.52.55396: Flags [.], ack 350, win 243, options [nop,nop,TS val 1004547189 ecr 3735559284], length 0'