Reply
vga
Explorer
Posts: 14
Registered: ‎09-30-2016

Re: Manager doesn't start due to JVM PermGen and JVM MaxHeap

Great.. Thank you. I'm very new to cloudera, I've one more question. I'm getting this error while installation, getting above message before completing cloudera manager installation. So it doesn't even saying me to go localhost:7180 to complete the installation. When do I need to change the  /etc/init.d/cloudera-scm-server file?. Thanks again

 

Regards

Vga

Posts: 455
Topics: 1
Kudos: 106
Solutions: 59
Registered: ‎04-22-2014

Re: Manager doesn't start due to JVM PermGen and JVM MaxHeap

Hi,

 

Are you using the .bin installer?

Can you print out exactly what you see?

If you are hitting the bug, CM should still start since the conditional that would lead to a start failure should fail so you just get some messages printed to your terminal, but CM starts.

 

Please also do the following:

 

(1)

 

netstat -nap |grep 718

 

(2)

 

grep 718 /var/log/cloudera-scm-server/cloudera-scm-server.log

 

Post that info to the case so we can help root cause the issue.

vga
Explorer
Posts: 14
Registered: ‎09-30-2016

Re: Manager doesn't start due to JVM PermGen and JVM MaxHeap

Thank you Bgooley.

 

Yes, I'm installing using .bin. There are 2 issues for me.

 

1. If do NOT install oracle 7 java before installing cloudera manager, I'm getting below JVM PremGen and JVM MaxHeap error. That is related to our subject .

 

2 If I install oracle 7 JAVA before installing cloudera manager, I'm NOT getting JVM PremGen and JVMmaxHeap errors.  but I'm getting below errors at the time of starting the services (almost at the end of installation where it start services).  Any idea?

 

stderr:

 

java.io.IOException: Cannot create directory /dfs/nn/current
at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:343)
at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:548)
at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:569)
at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:159)
at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1046)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1484)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1611)
16/10/15 15:22:52 ERROR namenode.NameNode: Failed to start namenode.
java.io.IOException: Cannot create directory /dfs/nn/current
at org.apache.hadoop.hdfs.server.common.Storage$StorageDirectory.clearDirectory(Storage.java:343)
at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:548)
at org.apache.hadoop.hdfs.server.namenode.NNStorage.format(NNStorage.java:569)
at org.apache.hadoop.hdfs.server.namenode.FSImage.format(FSImage.java:159)
at org.apache.hadoop.hdfs.server.namenode.NameNode.format(NameNode.java:1046)
at org.apache.hadoop.hdfs.server.namenode.NameNode.createNameNode(NameNode.java:1484)
at org.apache.hadoop.hdfs.server.namenode.NameNode.main(NameNode.java:1611)

 

Stdout:

 

Tue Oct 11 21:18:15 MDT 2016
JAVA_HOME=/usr/lib/jvm/java-7-oracle
using /usr/lib/jvm/java-7-oracle as JAVA_HOME
using 5 as CDH_VERSION
using /run/cloudera-scm-agent/process/18-hdfs-SECONDARYNAMENODE as CONF_DIR
using  as SECURE_USER
using  as SECURE_GROUP
64
Tue Oct 11 21:18:31 MDT 2016
JAVA_HOME=/usr/lib/jvm/java-7-oracle
using /usr/lib/jvm/java-7-oracle as JAVA_HOME
using 5 as CDH_VERSION
using /run/cloudera-scm-agent/process/18-hdfs-SECONDARYNAMENODE as CONF_DIR
using  as SECURE_USER
using  as SECURE_GROUP
64
Tue Oct 11 21:18:40 MDT 2016
JAVA_HOME=/usr/lib/jvm/java-7-oracle
using /usr/lib/jvm/java-7-oracle as JAVA_HOME
using 5 as CDH_VERSION
using /run/cloudera-scm-agent/process/18-hdfs-SECONDARYNAMENODE as CONF_DIR
using  as SECURE_USER
using  as SECURE_GROUP
64
Tue Oct 11 21:18:48 MDT 2016
JAVA_HOME=/usr/lib/jvm/java-7-oracle
using /usr/lib/jvm/java-7-oracle as JAVA_HOME
using 5 as CDH_VERSION
using /run/cloudera-scm-agent/process/18-hdfs-SECONDARYNAMENODE as CONF_DIR
using  as SECURE_USER
using  as SECURE_GROUP

 

Highlighted
New Contributor
Posts: 1
Registered: ‎06-01-2016

Re: Manager doesn't start due to JVM PermGen and JVM MaxHeap

It's stupid Cloudera test by regex in bash script. To fix add 

-XX:MaxPermSize=256m

parameter to CMF_JAVA_OPTS in /etc/default/cloudera-scm-server file:

Announcements