Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

How to resolve "500 server error" for Hive view in Ambari

Solved Go to solution
Highlighted

How to resolve "500 server error" for Hive view in Ambari

Rising Star

When clicking on Hive view from views tab in ambari i am getting "500: server error".

Please help me on this.

Thanks in advance!

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

Rising Star

@Sagar Shimpi Thanks a lot :)

It was resolved by changing the AMBARI_JVM_ARGS variable in /var/lib/ambari-server/ambari-env.sh, by replacing the default -Xmx2048mwith the following:

-Xmx4096m -XX:PermSize=128m -XX:MaxPermSize=128m

View solution in original post

6 REPLIES 6
Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

@Raghu Ramamoorthi Can you let us know which link you followed for HIVE view installation ? Can you check ambari-server logs for fore error log details

Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

Rising Star

@Sagar Shimpi

Hi Sagar i just navigated to ambari views and created Hive View.

The ambari-server log says that:

Jun 15, 2016 12:59:48 AM com.sun.jersey.spi.inject.Errors processErrorMessages WARNING: The following warnings have been detected with resource and/or provider classes: WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.HostComponentService.getHostComponents(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo), should not consume any entity. WARNING: A HTTP GET method, public javax.ws.rs.core.Response org.apache.ambari.server.api.services.HostComponentService.getHostComponent(java.lang.String,javax.ws.rs.core.HttpHeaders,javax.ws.rs.core.UriInfo,java.lang.String,java.lang.String), should not consume any entity. Exception in thread "Server Action Executor" Exception: java.lang.OutOfMemoryError thrown from the UncaughtExceptionHandler in thread "Server Action Executor" Exception in thread "alert-event-bus-2" Exception in thread "alert-event-bus-1" java.lang.OutOfMemoryError: PermGen space java.lang.OutOfMemoryError: PermGen space Jun 15, 2016 10:02:55 AM com.sun.jersey.spi.container.ContainerResponse mapMappableContainerException SEVERE: The exception contained within MappableContainerException could not be mapped to a response, re-throwing to the HTTP container java.lang.OutOfMemoryError: PermGen space Jun 15, 2016 10:02:55 AM com.sun.jersey.spi.container.ContainerResponse mapMappableContainerException SEVERE: The exception contained within MappableContainerException could not be mapped to a response, re-throwing to the HTTP container java.lang.OutOfMemoryError: PermGen space

Please assist me.

Thanks in advance.!

Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

It clearly say its OutOfMemory issue "java.lang.OutOfMemoryError: PermGen space java.lang.OutOfMemoryError: PermGen space"

Pls check this to resolve the issue - https://docs.hortonworks.com/HDPDocuments/Ambari-2.1.2.0/bk_ambari_views_guide/content/ch_preparing_...

Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

Rising Star

@Sagar Shimpi Thanks a lot :)

It was resolved by changing the AMBARI_JVM_ARGS variable in /var/lib/ambari-server/ambari-env.sh, by replacing the default -Xmx2048m with the following:

-Xmx4096m -XX:PermSize=128m -XX:MaxPermSize=128m

Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

Rising Star

@Sagar Shimpi Thanks a lot :)

It was resolved by changing the AMBARI_JVM_ARGS variable in /var/lib/ambari-server/ambari-env.sh, by replacing the default -Xmx2048mwith the following:

-Xmx4096m -XX:PermSize=128m -XX:MaxPermSize=128m

View solution in original post

Highlighted

Re: How to resolve "500 server error" for Hive view in Ambari

Rising Star

@Sagar Shimpi Thanks a lot :)

It was resolved by changing the AMBARI_JVM_ARGS variable in /var/lib/ambari-server/ambari-env.sh, by replacing the default -Xmx2048m with the following:

-Xmx4096m -XX:PermSize=128m -XX:MaxPermSize=128m

Don't have an account?
Coming from Hortonworks? Activate your account here