Activity monitory(navigator) http error 503

[#1]

Hello.

I have activity monitor in green state.

In logs I have smth like this:

ps Sorry for quality, have no internet access in my cluster.

But when I open navigator web ui I see this:

[#2 · Accepted solution]

@Yuriy_but You are likely hitting some known issue. 

If this is greater than CM 5.15.1 then please follow this step and see. 

1. From Cloudera Manager, stop Navigator Metadata Server
2. On the host where Navigator Metadata Server is installed, navigate to the jars directory:
   

   $ cd /usr/share/cmf/cloudera-navigator-server/jars

3. List the contents that start with c3p0:

   $ ls c3p0*

   The list may include two jar files:

   c3p0-0.9.1.2.jar
   c3p0-0.9.5.2.jar

4. If the file c3p0-0.9.5.2.jar is present, remove it:

   $ rm c3p0-0.9.5.2.jar

5. Navigate tothe Navigator wars directory:

   $ cd /usr/share/cmf/cloudera-navigator-server/wars/

6. Delete the same file c3p0-0.9.5.2.jar from the nav-core-webapp* war file:

   $ zip -d nav-core-webapp-2.14.1.war WEB-INF/lib/c3p0-0.9.5.2.jar

7. From Cloudera Manager, start Navigator Metadata Server

If this is air-gapped environment (No internet access) then you might need these: 

1. Identify IP address of the NMS. (can be gathered in Cloudera Management services->instances->Navigator Metadata Server)

2. Add the following line to the bottom of /etc/hosts on the NMS

127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
<NMS_IP_ADDRESS> java.sun.com

3. On NMS, install httpd, depending on your Linux distribution. As this host does not have internet access, you will need to manually import and install rpms.

https://httpd.apache.org/docs/2.4/platform/rpm.html

4. Make a directory for java dtd file, and adjust permissions.

mkdir /var/www/html/dtd; chown 755 /var/www/html/dtd

5. Acquire Java DTD file from the following URL.

http://java.sun.com/dtd/web-app_2_3.dtd

6. Copy the file to /var/www/html/dtd directory on the NMS.  Ensure the file is readable by "other".

7. Enable httpd server

sudo systemctl enable httpd; sudo systemctl start httpd

8. Start NMS.

NOTE: httpd must run for each NMS restart, this is not a one-off workaround. Systemctl command should ensure that this is the case.   If the above workaround is not possible, a patch is also available from Cloudera Support until this is resolved in an upcoming release of Cloudera Manager.