3.2. Metastore startup failed for HCatalog Daemon

If the HCatalog daemon is incorrectly configured, the smoke tests fail and you get the following error message on your console:

Metastore startup failed, see /var/log/hcatalog/hcat.err

Solution: You can find the root cause of this exception using the /var/log/hcatalog/hcat.err file on your HCatalog node. Typically, the root cause is either Unknown Host Exception or Failed Initializing Database Error.

Solution - Unknown Host Exception:
1. Open /var/log/hcatalog/hcat.err file to confirm the root cause:
```
 at java.lang.reflect.Method.invoke (Method.java:597)
  at org.apache.hadoop.util.Runjar.main (runjar.java:156)
  Caused by: java.net.UnknownHostException:mysql.host.com atjava.net.InetAddress.getAllByName(INetAddress.java:1157)
```
2. Open the master-install-location/gsInstaller/gsInstaller.properties file in edit mode and update the value for mysqldbhost property.
3. Restart the installation process.
Solution - Failed Initializing Database Error
1. For this error, you should find a message similar to the one shown below in your /var/log/hcatalog/hcat.err file:
```
11/12/29 20:52:04 ERROR DataNucleus.Plugin: Bundle “org.eclipse.jdt.core” required       
11/12/29 20:52:04 ERROR DataNucleus.Plugin: Bundle “org.eclipse.jdt.core” required    
11/12/29 20:52:04 ERROR DataStore.Schema: Failed initialising database   
                                
```
2. Open the master-install-location/gsInstaller/gsInstaller.properties file in edit mode and update the value for mysqldbuser and mysqldbpswd properties.
  Important
  Ensure that $mysqluser has required privileges on the MySQL database as provided under the databasename property in the gsInstaller.properties file.
3. Restart the installation process.

	Important
Ensure that `$mysqluser` has required privileges on the MySQL database as provided under the `databasename` property in the `gsInstaller.properties` file.

Legal notices