Grokbase › Groups › Hadoop › scm-users › November 2013
FAQ
Hi Guys,
we are using Cloudera Standard 4.7.0. It's working smoothly. But we noticed
process com.cloudera.server.cmf.Main class terminated due
to java.lang.NullPointerException

  2013-11-15 07:39:48,128 ERROR
[JmxPeriodicLogging-0:[email protected]] getting attribute
DiagnosticOptions of com.sun.management:type=HotSpotDiagnostic threw an
exception
javax.management.RuntimeMBeanException: java.lang.NullPointerException
  at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:877)
at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:890)
  at
com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:687)
at
com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:672)
  at
com.cloudera.enterprise.JmxJsonWriter.writeAttribute(JmxJsonWriter.java:304)
at com.cloudera.enterprise.JmxJsonWriter.listBeans(JmxJsonWriter.java:281)
  at com.cloudera.enterprise.JmxJsonWriter.read(JmxJsonWriter.java:177)
at com.cloudera.enterprise.JmxJsonWriter.getAll(JmxJsonWriter.java:142)
  at com.cloudera.enterprise.CommonMain$1.run(CommonMain.java:368)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
  at
java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
  at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
at
java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
  at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
  at java.lang.Thread.run(Thread.java:679)

full-log: /var/log/cloudera-scm-server
==============================
http://paste.ubuntu.com/6421869/


Please guide me. How to fix this.

-Dhanasekaran.

Did I learn something today? If not, I wasted it.

To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

Search Discussions

  • Philip Zeyliger at Nov 15, 2013 at 8:40 pm ⇧
    bcc: cdh-user

    Hi,

    Please don't cross-post to two mailing lists; scm-users@ is the appropriate
    forum for this question.

    The the log message looks fearsome, it is not responsible for the CM server
    process dying. Are you sure the process is dead? The first place I would
    check is "dmesg" to see if your system ran out of memory and a java process
    got killed. That's the most common "spontaneous combustion" sort of
    failure I've seen.

    I'd be curious to know what JVM you're using for the log message itself.

    -- Philip




    On Fri, Nov 15, 2013 at 8:12 AM, Dhanasekaran Anbalagan
    wrote:
    Hi Guys,
    we are using Cloudera Standard 4.7.0. It's working smoothly. But we
    noticed process com.cloudera.server.cmf.Main class terminated due
    to java.lang.NullPointerException

    2013-11-15 07:39:48,128 ERROR
    [JmxPeriodicLogging-0:[email protected]] getting attribute
    DiagnosticOptions of com.sun.management:type=HotSpotDiagnostic threw an
    exception
    javax.management.RuntimeMBeanException: java.lang.NullPointerException
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrow(DefaultMBeanServerInterceptor.java:877)
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.rethrowMaybeMBeanException(DefaultMBeanServerInterceptor.java:890)
    at
    com.sun.jmx.interceptor.DefaultMBeanServerInterceptor.getAttribute(DefaultMBeanServerInterceptor.java:687)
    at
    com.sun.jmx.mbeanserver.JmxMBeanServer.getAttribute(JmxMBeanServer.java:672)
    at
    com.cloudera.enterprise.JmxJsonWriter.writeAttribute(JmxJsonWriter.java:304)
    at com.cloudera.enterprise.JmxJsonWriter.listBeans(JmxJsonWriter.java:281)
    at com.cloudera.enterprise.JmxJsonWriter.read(JmxJsonWriter.java:177)
    at com.cloudera.enterprise.JmxJsonWriter.getAll(JmxJsonWriter.java:142)
    at com.cloudera.enterprise.CommonMain$1.run(CommonMain.java:368)
    at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
    at
    java.util.concurrent.FutureTask$Sync.innerRunAndReset(FutureTask.java:351)
    at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:178)
    at
    java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:165)
    at
    java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:267)
    at
    java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1110)
    at
    java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:603)
    at java.lang.Thread.run(Thread.java:679)

    full-log: /var/log/cloudera-scm-server
    ==============================
    http://paste.ubuntu.com/6421869/


    Please guide me. How to fix this.

    -Dhanasekaran.

    Did I learn something today? If not, I wasted it.

    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Dhanasekaran Anbalagan at Nov 18, 2013 at 4:31 am ⇧
    Hi Philip,

    I am sure, Process is dead. Also I noticed one more thing cloudera-manger
    using openjdk-java

    My other process using process using like namenode and jobtracker using
    oracle-jdk

    106 11430 7.6 2.0 15904740 1345048 ? Sl Nov15 277:46 */usr/bin/java
    *-cp .:lib/*:/usr/share/java/mysql-connector-java.jar
    -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties
    -Dcmf.root.logger=INFO,LOGFILE -Dcmf.log.dir=/var/log/cloudera-scm-server
    -Dcmf.log.file=cloudera-scm-server.log -Dcmf.jetty.threshhold=WARN
    -Dcmf.schema.dir=/usr/share/cmf/schema -Djava.awt.headless=true
    -Djava.net.preferIPv4Stack=true -Dpython.home=/usr/share/cmf -Xmx2G
    -XX:MaxPermSize=256m com.cloudera.server.cmf.Main
    [email protected]:~# cd /usr/bin/
    *[email protected]:/usr/bin# ./java -version*
    *java version "1.6.0_24"*
    *OpenJDK Runtime Environment (IcedTea6 1.11.4)
    (6b24-1.11.4-1ubuntu0.12.04.1)*
    *OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)*

    [email protected]:/usr/bin# cd /usr/lib/jvm/j2sdk1.6-oracle/bin/
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin# ./java -version
    *java version "1.6.0_31"*
    *Java(TM) SE Runtime Environment (build 1.6.0_31-b04)*
    *Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)*
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin#

    can you guide me. You to switch back open-jdk to oracle-jdk.

    -Dhanasearan.

    Did I learn something today? If not, I wasted it.

    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Philip Zeyliger at Nov 18, 2013 at 5:05 pm ⇧
    Have you run "dmesg"? Does it say that the kernel killed some processes
    because you ran out of memory?

    Cheers,

    -- Philip


    On Sun, Nov 17, 2013 at 8:31 PM, Dhanasekaran Anbalagan
    wrote:
    Hi Philip,

    I am sure, Process is dead. Also I noticed one more thing cloudera-manger
    using openjdk-java

    My other process using process using like namenode and jobtracker using
    oracle-jdk

    106 11430 7.6 2.0 15904740 1345048 ? Sl Nov15 277:46 */usr/bin/java
    *-cp .:lib/*:/usr/share/java/mysql-connector-java.jar
    -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties
    -Dcmf.root.logger=INFO,LOGFILE -Dcmf.log.dir=/var/log/cloudera-scm-server
    -Dcmf.log.file=cloudera-scm-server.log -Dcmf.jetty.threshhold=WARN
    -Dcmf.schema.dir=/usr/share/cmf/schema -Djava.awt.headless=true
    -Djava.net.preferIPv4Stack=true -Dpython.home=/usr/share/cmf -Xmx2G
    -XX:MaxPermSize=256m com.cloudera.server.cmf.Main
    [email protected]:~# cd /usr/bin/
    *[email protected]:/usr/bin# ./java -version*
    *java version "1.6.0_24"*
    *OpenJDK Runtime Environment (IcedTea6 1.11.4)
    (6b24-1.11.4-1ubuntu0.12.04.1)*
    *OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)*

    [email protected]:/usr/bin# cd /usr/lib/jvm/j2sdk1.6-oracle/bin/
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin# ./java -version
    *java version "1.6.0_31"*
    *Java(TM) SE Runtime Environment (build 1.6.0_31-b04)*
    *Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)*
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin#

    can you guide me. You to switch back open-jdk to oracle-jdk.

    -Dhanasearan.

    Did I learn something today? If not, I wasted it.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Dhanasekaran Anbalagan at Nov 18, 2013 at 5:36 pm ⇧
    Hi Philip,

    dmesg console output.

    http://paste.ubuntu.com/6438503/

    Did I learn something today? If not, I wasted it.

    On Mon, Nov 18, 2013 at 12:04 PM, Philip Zeyliger wrote:

    Have you run "dmesg"? Does it say that the kernel killed some processes
    because you ran out of memory?

    Cheers,

    -- Philip


    On Sun, Nov 17, 2013 at 8:31 PM, Dhanasekaran Anbalagan <
    [email protected]> wrote:
    Hi Philip,

    I am sure, Process is dead. Also I noticed one more thing
    cloudera-manger using openjdk-java

    My other process using process using like namenode and jobtracker using
    oracle-jdk

    106 11430 7.6 2.0 15904740 1345048 ? Sl Nov15 277:46 */usr/bin/java
    *-cp .:lib/*:/usr/share/java/mysql-connector-java.jar
    -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties
    -Dcmf.root.logger=INFO,LOGFILE -Dcmf.log.dir=/var/log/cloudera-scm-server
    -Dcmf.log.file=cloudera-scm-server.log -Dcmf.jetty.threshhold=WARN
    -Dcmf.schema.dir=/usr/share/cmf/schema -Djava.awt.headless=true
    -Djava.net.preferIPv4Stack=true -Dpython.home=/usr/share/cmf -Xmx2G
    -XX:MaxPermSize=256m com.cloudera.server.cmf.Main
    [email protected]:~# cd /usr/bin/
    *[email protected]:/usr/bin# ./java -version*
    *java version "1.6.0_24"*
    *OpenJDK Runtime Environment (IcedTea6 1.11.4)
    (6b24-1.11.4-1ubuntu0.12.04.1)*
    *OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)*

    [email protected]:/usr/bin# cd /usr/lib/jvm/j2sdk1.6-oracle/bin/
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin# ./java -version
    *java version "1.6.0_31"*
    *Java(TM) SE Runtime Environment (build 1.6.0_31-b04)*
    *Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)*
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin#

    can you guide me. You to switch back open-jdk to oracle-jdk.

    -Dhanasearan.

    Did I learn something today? If not, I wasted it.
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
  • Philip Zeyliger at Nov 19, 2013 at 5:50 pm ⇧
    Don't see anything suspicious in dmesg.

    Let's look at /var/log/cloudera-scm-server/cloudera-scm-server.out and
    cloudera-scm-server.log?




    On Mon, Nov 18, 2013 at 9:35 AM, Dhanasekaran Anbalagan
    wrote:
    Hi Philip,

    dmesg console output.

    http://paste.ubuntu.com/6438503/

    Did I learn something today? If not, I wasted it.

    On Mon, Nov 18, 2013 at 12:04 PM, Philip Zeyliger wrote:

    Have you run "dmesg"? Does it say that the kernel killed some processes
    because you ran out of memory?

    Cheers,

    -- Philip


    On Sun, Nov 17, 2013 at 8:31 PM, Dhanasekaran Anbalagan <
    [email protected]> wrote:
    Hi Philip,

    I am sure, Process is dead. Also I noticed one more thing
    cloudera-manger using openjdk-java

    My other process using process using like namenode and jobtracker using
    oracle-jdk

    106 11430 7.6 2.0 15904740 1345048 ? Sl Nov15 277:46 */usr/bin/java
    *-cp .:lib/*:/usr/share/java/mysql-connector-java.jar
    -Dlog4j.configuration=file:/etc/cloudera-scm-server/log4j.properties
    -Dcmf.root.logger=INFO,LOGFILE -Dcmf.log.dir=/var/log/cloudera-scm-server
    -Dcmf.log.file=cloudera-scm-server.log -Dcmf.jetty.threshhold=WARN
    -Dcmf.schema.dir=/usr/share/cmf/schema -Djava.awt.headless=true
    -Djava.net.preferIPv4Stack=true -Dpython.home=/usr/share/cmf -Xmx2G
    -XX:MaxPermSize=256m com.cloudera.server.cmf.Main
    [email protected]:~# cd /usr/bin/
    *[email protected]:/usr/bin# ./java -version*
    *java version "1.6.0_24"*
    *OpenJDK Runtime Environment (IcedTea6 1.11.4)
    (6b24-1.11.4-1ubuntu0.12.04.1)*
    *OpenJDK 64-Bit Server VM (build 20.0-b12, mixed mode)*

    [email protected]:/usr/bin# cd /usr/lib/jvm/j2sdk1.6-oracle/bin/
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin# ./java -version
    *java version "1.6.0_31"*
    *Java(TM) SE Runtime Environment (build 1.6.0_31-b04)*
    *Java HotSpot(TM) 64-Bit Server VM (build 20.6-b01, mixed mode)*
    [email protected]:/usr/lib/jvm/j2sdk1.6-oracle/bin#

    can you guide me. You to switch back open-jdk to oracle-jdk.

    -Dhanasearan.

    Did I learn something today? If not, I wasted it.
    To unsubscribe from this group and stop receiving emails from it, send an
    email to [email protected].
    To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedNov 15, '13 at 4:13p
activeNov 19, '13 at 5:50p
posts6
users2
websitecloudera.com
irc#hadoop

2 users in discussion

Philip Zeyliger: 3 posts Dhanasekaran Anbalagan: 3 posts

Content

People

Support

Translate

site design / logo © 2023 Grokbase