Steps to Avoid/Resolve Navigator Metadata Server Start Error while Upgrading to BDA 4.1 or Higher Release from BDA 4.0 or Lower Release (Doc ID 1967283.1)

Last updated on OCTOBER 11, 2016

Applies to:

Big Data Appliance Integrated Software - Version 4.1.0 and later
Linux x86-64

Goal

While upgrading to BDA 4.1 or higher Release from BDA 4.0 or lower release with Navigator service enabled thru Cloudera Manager(CM) on BDA, step 7(startcloudera.sh) fails as Navigator Metadata Server(NMDS) cannot be started. Navigator Metadata Server logs show one of the below error

When there is NO navms database /user in MySQL database

 Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Access denied for user ''@'localhost' to database 'navms'
    at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
    at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)
    at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

When navms database /user exist in MySQL database but cannot be accessed due to navms.db.host or navms.db.password not being set correctly

Unable to access schema version in database
java.lang.RuntimeException: com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure
...
Caused by: java.net.ConnectException: Connection refused
at java.net.PlainSocketImpl.socketConnect(Native Method)
    at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:339)
    at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:200)
    at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:182)
    at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392)
    at java.net.Socket.connect(Socket.java:579)
    at java.net.Socket.connect(Socket.java:528)
    at java.net.Socket.<init>(Socket.java:425)
    at java.net.Socket.<init>(Socket.java:241)
    at com.mysql.jdbc.StandardSocketFactory.connect(StandardSocketFactory.java:257)
    at com.mysql.jdbc.MysqlIO.<init>(MysqlIO.java:294) 

Prior to CDH 5.2 version no backend database is needed for Navigator Metadata Server to store the metadata.

During upgrade to CDH 5.3 release , Navigator Metadata Server default settings of database are set to mysql database named navms on localhost with user name called navms. As there is no navms mysql database failure occurs.

This document provides steps to avoid the error during upgrade and also steps to follow once the upgrade fails due to NMDS not residing on node03 or preupgrade steps not being followed.

Solution

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms