Troubleshooting HMS connections
Resolve common failures when you test or run a Hive or Impala HMS connection in Octopai Client, such as Kerberos ticket, KDC, firewall, and WSL service-account errors.
Match the symptom to a cause and resolution, and confirm the details with your cluster administrator.
| Symptom | Cause | Resolution |
|---|---|---|
kinit: Password incorrect |
Keytab is outdated because of a key version number (KVNO) mismatch | Ask your administrator for a new keytab file |
Cannot contact KDC |
VPN is off or krb5.ini is incorrect | Connect the VPN, and verify the realm and KDC with your administrator |
| Connection timeout to the database | Due to a firewall, an incorrect host or port, or the service is not running | Confirm the host, port, and network path with your administrator |
no pg_hba.conf entry (PostgreSQL) |
Client IP address is not allowed | Ask your administrator to add a rule in pg_hba.conf |
auth_gssapi_client.so not found (MariaDB) |
WSL MariaDB plugin is missing | Install libmariadb3 and set
MysqlGssapiPluginDir |
| WSL Kerberos works in the desktop application but not as a service | Service runs as Local System or the wrong account | Reinstall the service under the local administrator user that owns WSL, and complete the WSL setup while logged in as that user |
| Oracle SQL or schema errors | Metastore schema or grants differ from the cluster defaults | Confirm the metastore schema and permissions with your administrator |
| Oracle Kerberos connection or authentication failure | sqlnet.ora folder is incorrect or missing | Verify OracleTnsAdminPath and sqlnet.ora with your administrator |
