Cannot see database after MC installation

kfruchtmankfruchtman Vertica Customer ✭
in General Discussion

Hello,
I need help please.I have an Ubuntu 18.04.4 LTS, on it vertica db 9 with one node.I have installed the MC on the same box.
The MC is not recognizing the running db on it.When I am trying to run "Import a Vertica running cluster" it sais that it cannot connect to the agent.Default port 5444 of the agent is open on the box.
The console log file shows:
3 Feb 2021 17:11:49,389 [qtp1775282465-108] VuiUtils INFO - Check host:35.246.154.161 reachable via port 22
23 Feb 2021 17:11:49,397 [qtp1775282465-108] AgentCommands INFO - agentapi=GET, https://35.246.154.161:5444/
23 Feb 2021 17:13:59,603 [qtp1775282465-108] AgentCommands INFO - Connect to 35.246.154.161:5444 [/35.246.154.161] failed: Connection timed out (Connection timed out)
23 Feb 2021 17:13:59,607 [qtp1775282465-108] AgentCommands WARN - executeCommandWithRetryWithinHost>> host with ip: 35.246.154.161 is null

Any help would be very much appreciated!
Kind regards,
Keren

Tagged:

Answers

  • Jim_KnicelyJim_Knicely - Select Field - Administrator
    edited February 2021

    Make sure you've opened all of the ports needed by Vertica and MC!
    https://www.vertica.com/docs/latest/HTML/Content/Authoring/InstallationGuide/BeforeYouInstall/EnsurePortsAreAvailable.htm

    If it's just a test box (i.e. you said this is a single node install) sometimes it's just easier to disable the firewall completely :)
    https://www.vertica.com/docs/latest/HTML/Content/Authoring/InstallationGuide/BeforeYouInstall/iptablesEnabled.htm

  • kfruchtmankfruchtman Vertica Customer ✭

    Thanks Jim but I read now that the agent needs to be started and when I do
    dbadmin@vertica-sandbox-1:/$ /etc/init.d/vertica_agent start
    -su: /etc/init.d/vertica_agent: No such file or directory
    Or:
    badmin@vertica-sandbox-1:/$ sudo /etc/init.d/vertica_agent status
    sudo: /etc/init.d/vertica_agent: command not found
    dbadmin@vertica-sandbox-1:/$ /etc/init.d/vertica_agent enable
    -su: /etc/init.d/vertica_agent: No such file or directory
    dbadmin@vertica-sandbox-1:/$ sudo /etc/init.d/vertica_agent enable
    sudo: /etc/init.d/vertica_agent: command not found
    dbadmin@vertica-sandbox-1:/$ /etc/init.d/vertica_agent enable
    -su: /etc/init.d/vertica_agent: No such file or directory
    dbadmin@vertica-sandbox-1:/$ /etc/init.d/vertica_agent start
    -su: /etc/init.d/vertica_agent: No such file or directory

    could it be that the agent is not installed?

  • kfruchtmankfruchtman Vertica Customer ✭

    I made sure all the ports are open

  • Jim_KnicelyJim_Knicely - Select Field - Administrator

    Maybe try:
    /opt/vertica/sbin/vertica_agent restart

  • kfruchtmankfruchtman Vertica Customer ✭

    wow its working but asking for a password - which password is it exactly? dbadmn did not work....

  • kfruchtmankfruchtman Vertica Customer ✭

    the pass for the dbadmin user of vertica I meant.It did not work.Which password is he asking for ?

  • Jim_KnicelyJim_Knicely - Select Field - Administrator

    You have to be root or sudo.

  • kfruchtmankfruchtman Vertica Customer ✭

    right now it worked:
    root@vertica-sandbox-1:~# /opt/vertica/sbin/vertica_agent restart
    Stopping vertica agent:
    starting agent
    Opening PID file "/opt/vertica/log/agent.pid".
    Overwriting /opt/vertica/log/agent_dbadmin.log
    Overwriting /opt/vertica/log/agent_dbadmin.err
    OK for user: dbadmin
    *
    but the MC is still giving the same error when I am trying to import the db."Could not establish a connection with the agent" ...... please help!

  • DaveTDaveT Vertica Employee Employee

    I have seen this issue when port 5433 is not open. It is also required for the import. Please double-check that one.

  • kfruchtmankfruchtman Vertica Customer ✭

    when I do netstat -a I get this:

    tcp 0 0 localhost:6010 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:5434 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:39005 0.0.0.0:* LISTEN
    tcp 0 0 localhost:4803 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:5444 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:5450 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:8079 0.0.0.0:* LISTEN
    tcp 0 0 localhost:domain 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:ssh 0.0.0.0:* LISTEN
    tcp 0 0 0.0.0.0:5433 0.0.0.0:* LISTEN

    So it looks open.... no?

  • kfruchtmankfruchtman Vertica Customer ✭

    port 5433 is open for sure.
    Can you advise me further? problem still exists, cannot connect to the db via MC.
    many thanks

  • kfruchtmankfruchtman Vertica Customer ✭

    Hi ! I just want to inform that problem was solved.The problem was that the MC didn't recognize the public ip of the machine and it needed to use the 127.0.0.1 ip for it to work.Many thanks for all your help! much appreciated:-)

  • Jim_KnicelyJim_Knicely - Select Field - Administrator

    @kfruchtman - Thanks for letting us know. For fun, what is the output of:

    SELECT node_name, node_address, export_address FROM nodes ORDER BY 1;

  • kfruchtmankfruchtman Vertica Customer ✭

    here is the output:

  • Jim_KnicelyJim_Knicely - Select Field - Administrator
    edited March 2021

    Ok. That explains it!

    Before you do a whole lot of work, know that you won't be able expand this cluster to more nodes because you installed on the looback address.

    See the Important Notes section here:
    https://www.vertica.com/docs/latest/HTML/Content/Authoring/InstallationGuide/BeforeYouInstall/ConfiguringTheNetwork.htm

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Format
SpoilerCodeQuote
Heading 2Heading 1
Emoji
:):D:(;):/:o:s:p:'(:|B):#:*<3o:)>:)
Url
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file
Home • General DiscussionComment As ...