Fresh Installation - Problem in Creating Database

[id10t]

Hi!

Are you good with KVM/QEMU? I don't recommend to use KVM/QEMU, very hard to configure it.
Probably you did clone and didn't changed all network configurations like MAC or something else.

Node 4: [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
Node 6: [Comms] <INFO> InitSpread: I am node v_mam_node0006 (oid 45035996273704972)

BTW: your nodes do not synchronized.

UPDATE:
did you configured BCast/Mask properly? and what is your installation options? Check your network configuration, coz' its look like you are using a private network (see install_vertica -S/-U options)
Node 04: 10.4.111.288
Node 05: 10.4.218.65
Node 06: 10.4.217.188

[peteclark3]

I'm having this same problem, the 2nd and 3rd nodes never come up... the contents of the thread thus far didn't really help.. would anyone mind having a look? I can attach whatever log files you need..

EDIT: I should note that I am using a "trial" license file, which i have placed on 1 of the 3 boxes (the one where it comes up fine..).... maybe the license is only good for 1 host?

*** Creating database: GMFastReporting ***
10.0.1.235 OK [vertica][(6, 1, 1)][000][x86_64]
10.0.1.175 OK [vertica][(6, 1, 1)][000][x86_64]
10.0.1.174 OK [vertica][(6, 1, 1)][000][x86_64]
Checking full connectivity
Creating database GM
Node Status: v_gmfastreporting_node0001: (VALIDATING LICENSE)
Node Status: v_gmfastreporting_node0001: (UP)
Creating database nodes
Creating node v_gmfastreporting_node0002 (host 10.0.1.175)
Creating node v_gmfastreporting_node0003 (host 10.0.1.174)
Node Status: v_gmfastreporting_node0001: (UP) v_gmfastreporting_node0002: (DOWN) v_gmfastreporting_node0003: (DOWN)
Node Status: v_gmfastreporting_node0001: (UP) v_gmfastreporting_node0002: (DOWN) v_gmfastreporting_node0003: (DOWN)
Node Status: v_gmfastreporting_node0001: (UP) v_gmfastreporting_node0002: (DOWN) v_gmfastreporting_node0003: (DOWN)

[JimKnicely]

Hi,

Have you checked you dbLog file? It is located in your /catalog-path/database-name directory. Because Vertica writes to this file before the Vertica log file is initialized, this is where you'll find start up issues listed. Check all the nodes.

I hope this helps!

[JimKnicely]

#peteclark3,

Please read #sKwa's post right above your post. You seem to be having the same issue as #imsaravanan79. That is, your nodes are on different subnets.

Can you post the exact command you ran to install Vertica? We need to see what options you used when invoking the install_vertica script.

Thanks!

[peteclark3]

My command to install vertica:
sudo /opt/vertica/sbin/install_vertica -s agg1,agg2,agg3 -r vertica-6.1.1-0.x86_64.RHEL5.rpm -u dbadmin

so 10.0.1.174/175/235 are on different subnets..?

Re: the dbLog, I am seeing:

node2:
Connected to spread at host 10.0.1.175(10.0.1.175) port 4803
FATAL: Unable to bind server on port 5433
05/13/13 21:03:25 SP_connect: DEBUG: Auth list is: NULL

node3:
Connected to spread at host 10.0.1.175(10.0.1.175) port 4803
FATAL: Unable to bind server on port 5433
05/13/13 21:03:25 SP_connect: DEBUG: Auth list is: NULL

... I guess some ports between the machines are not open..? Is this my agg2 and agg3 servers trying to talk to my agg1 server (which initialized and is up?)

[JimKnicely]

Oops. Sorry, I was looking at the previous posters' IPs when I said yours were on different subnets. Duh!

Did you disable the firewall between your nodes? Vertical recommends not to use firewalls.

[peteclark3]

Previously I was seeing connectivity errors for port 5443 in the dbLog, but now I don't see that, now that I think all the ports have been opened between the machines on the VPC. This is all I see in the dblog now..

Connected to spread at host 10.0.1.235(10.0.1.235) port 4803

.. and I still have node1 stuck in INITIALIZING with Nodes 2 and 3 DOWN.. seeing this on nodes 2 and 3 in the vertica.log:
2013-05-20 13:36:27.000 Cluster Inviter:0x7f6c5c00f190 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2013-05-20 13:36:27.000 Cluster Inviter:0x7f6c5c00f190 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2013-05-20 13:36:27.004 nameless:0x6a936f0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2013-05-20 13:36:28.004 nameless:0x6a936f0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2013-05-20 13:36:29.001 nameless:0x6a936f0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name

.. and all I see is stuff like this in the vertica.log on node1 while it's stuck in INITIALIZING..

2013-05-20 13:35:09.000 Timer Service:0x75a8080 [Util] <INFO> Task 'LicenseSizeAuditor' enabled
2013-05-20 13:35:15.502 Spread Client:0x7256950 [Comms] <INFO> Saw membership message 4352 on Vertica:all
2013-05-20 13:35:15.554 Spread Client:0x7256950 [Comms] <INFO> Saw membership message 5120 on Vertica:all
2013-05-20 13:35:29.000 Timer Service:0x75a8080 [Util] <INFO> Task 'ManageEpochs' enabled
2013-05-20 13:35:29.000 Timer Service:0x75a8080 [Util] <INFO> Task 'AnalyzeRowCount' enabled
2013-05-20 13:35:29.000 Timer Service:0x75a8080 [Util] <INFO> Task 'LicenseSizeAuditor' enabled
2013-05-20 13:35:34.034 Spread Client:0x7256950 [Comms] <INFO> Saw membership message 4352 on Vertica:all
2013-05-20 13:35:34.085 Spread Client:0x7256950 [Comms] <INFO> Saw membership message 5120 on Vertica:all
2013-05-20 13:35:34.543 Spread Client:0x7256950 [Comms] <INFO> Saw membership message 4352 on Vertica:all
2013-05-20 13:35:34.595 Spread Client:0x7256950 [Comms] <INFO> Saw membership message 5120 on Vertica:all