Skip to main content
FlashGrid.io

Troubleshooting: FlashGrid Cluster initialization problems

  • Updated
  • Products: FlashGrid Cluster on Azure
  • Products: FlashGrid Cluster on GCP
  • Products: FlashGrid Cluster on AWS

Cannot SSH to the first node of the cluster

Symptoms

SSH connection fails

Solution

  1. Double-check the IP address
  2. If connection is refused, wait 2 minutes after the VM is launched
  3. If authentication fails, make sure to connect as correct user (ec2-user on AWS, az-admin on Azure, your user name on GCP) and provide the private key corresponding to the public key provided when creating the cluster.
  4. In the security group settings check that TCP port 22 is open for inbound connections from the system with the SSH client

"Cluster initialization failed" message

Symptoms

After logging in to the first node you see "Cluster initialization failed" message

Solution

On the first node open /tmp/fg_setup.log file and check for an error message at the end of the file. If the error message matches one of the following then implement the corresponding solution. 

  • FAIL DNS server check. Verify that the DNS server IP address you provided in Launcher tool is correct. DNS server is required for downloading Oracle installation files. You can check whether DNS works by running nslookup flashgrid.io on the first node.

 

  • FAIL /u01/app/19.3.0/grid/gridSetup.sh and flashgrid-node command shows warnings similar to these: 
    rac2 node status: Critical
    Not ready: /services/asm,
    /initiators/iqn.2015-04.io.flashgrid:qrm1.xvdba,10.0.2.54,3260,
    /initiators/iqn.2015-04.io.flashgrid:qrm1.xvdbb,10.0.2.55,3260,
    If you are creating the cluster in an existing VPC/VNet then check that the corresponding security group has TCP port 3260 open between the group members. Also, double-check that the same destination port is open for outbound traffic too.

If there is a different error message then please open a support ticket and attach the /tmp/fg_setup.log file.

 

Cluster initialization not completing

Symptoms

More than 2 hours passed after creating the cluster, but when logging in to the first node you still see "Cluster initialization in progress" message.

The /tmp/fg_setup.log file on the first node has repeating messages of the following type:

ssh: connect to host rac2 port 22: No route to host 

Solution

If you are creating the cluster in an existing VPC/VNet then check that the corresponding security group has UDP ports 4801, 4802, 4803 open between the group members. Note that the ports are UDP, not TCP. Also, double-check that the same ports are open for outbound traffic too.