DEV Community

mmllllzcn
mmllllzcn

Posted on

GBase Database(GBase 8a) Installation: 4 Ways to Troubleshoot SSH Login Failures

#gbase #database #数据库 #todayilearned

When a distributed GBase Database(GBase 8a) installation stops at the file distribution stage with an error like Fail to login xxx errno:-1 Permission denied (publickey...), the message tells you that SSH authentication failed, but not why.

GBase Database multi-node deployment depends on the DBA user being able to connect to every node and distribute installation files. A single broken SSH connection can interrupt the entire installation.

Here are four layers to check, usually enough to pinpoint the problem within ten minutes.

1. Verify SSH Login Manually

Before changing configuration, test the connection manually from the first node to the target node using the DBA user.

su - gbase
ssh -p 22 172.27.237.164
ssh -v -p 22 172.27.237.164
Enter fullscreen mode Exit fullscreen mode

Two situations help narrow down the cause:

  • Manual login works, but the installation script fails: check the installation configuration.
  • Manual login also fails: investigate the SSH service, network, authentication, or system settings.

Use ssh -v to inspect the authentication process. If publickey appears in the authentication methods but is rejected, focus on SSH key configuration.

2. Check the SSH Port

If the cluster uses a non-default SSH port, make sure sshPort in demo.options matches the actual port.

For example:

sshPort = 2222
dbaUser = gbase
dbaPwd = gbase
Enter fullscreen mode Exit fullscreen mode

A port mismatch can produce the same login failure during GBase Database installation.

3. Check Password Configuration

Special characters in passwords may cause parsing problems in some installation scripts.

In a controlled test environment, you can temporarily use simple test passwords to determine whether password parsing is the cause. Restore the required strong passwords before production deployment.

Check both dbaPwd and rootPwd where applicable, and follow the configuration requirements in your GBase Database version-specific manual.

4. Check SSH Key Permissions

For passwordless SSH authentication, verify that the public keys are correctly configured and that file permissions are not too permissive.

Typical permissions are:

  • .ssh directory: 700
  • authorized_keys file: 600

Check them with:

ls -ld ~/.ssh
ls -l ~/.ssh/authorized_keys
Enter fullscreen mode Exit fullscreen mode

Also verify file ownership and confirm that the correct public key has been copied to every target node. In multi-node environments, it is easy to overlook one machine during key distribution.

Check SSH Logs Before Retrying

If all four checks look correct, inspect the target node's SSH service logs and the GBase Database installation logs. They can provide the exact authentication rejection reason.

One important rule: fix SSH login first, then rerun the installation.

Avoid changing passwords or SSH settings while reinstalling. Otherwise, the failure conditions keep changing, making troubleshooting much harder.

Build an SSH Pre-Installation Checklist

Before starting a multi-node GBase Database deployment, verify these items on every node:

  • Node IP address and SSH port
  • Manual login result using the DBA account
  • Password configuration and special characters
  • SSH key availability, ownership, and permissions

SSH connectivity is the foundation of GBase Database distributed installation. Spending ten minutes verifying every node before file distribution can save much more time troubleshooting a failed deployment.

For SSH port settings and parameter syntax, always refer to the manual for your specific GBase Database version.

Top comments (0)