hadoop datanode 启动失败，没有任何报错的解决

datanode的log日志仅有如下信息，没有报错，但是进程没有起来：

2013-11-25 09:57:01,466 INFO org.apache.hadoop.hdfs.server.datanode.DataNode: STARTUP_MSG:
/************************************************************
STARTUP_MSG: Starting DataNode
STARTUP_MSG:   host = tdw-10-136-149-102/10.136.149.102
STARTUP_MSG:   args = []
STARTUP_MSG:   version = 1.0.4
STARTUP_MSG:   build = https://svn.apache.org/repos/asf/hadoop/common/branches/branch-1.0 -r 1393290; compiled by 'hortonfo' on Wed Oct  3
 05:13:58 UTC 2012
************************************************************/
2013-11-25 09:57:02,013 INFO org.apache.hadoop.metrics2.impl.MetricsConfig: loaded properties from hadoop-metrics2.properties
2013-11-25 09:57:02,028 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source MetricsSystem,sub=Stats registered.
2013-11-25 09:57:02,029 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: Scheduled snapshot period at 10 second(s).
2013-11-25 09:57:02,029 INFO org.apache.hadoop.metrics2.impl.MetricsSystemImpl: DataNode metrics system started
2013-11-25 09:57:02,216 INFO org.apache.hadoop.metrics2.impl.MetricsSourceAdapter: MBean for source ugi registered.

Datanode的outlog：

WARNING: org.apache.hadoop.metrics.jvm.EventCounter is deprecated. Please use org.apache.hadoop.log.metrics.EventCounter in all the log4j.properties files.
log4j:ERROR Could not find value for key log4j.appender.NullAppender
log4j:ERROR Could not instantiate appender named "NullAppender".
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGFPE (0x8) at pc=0x00002b3f7a5a765f, pid=6202, tid=1076017472
#
# JRE version: 6.0_17-b04
# Java VM: Java HotSpot(TM) 64-Bit Server VM (14.3-b01 mixed mode linux-amd64 )
# Problematic frame:
# C  [ld-linux-x86-64.so.2+0x865f]
#
# An error report file with more information is saved as:
# /data/tdwadmin/tdwenv/hadoop-1.0.4/hs_err_pid6202.log
#
# If you would like to submit a bug report, please visit:
#   http://java.sun.com/webapps/bugreport/crash.jsp
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

如上的pid的errlog（截取）：

2aaaaabc4000-2aaaaabd1000 r-xp 00000000 08:04 96256038                   /data/tdwadmin/tdwenv/jdk1.6.0_17/jre/lib/amd64/libverify.so
2aaaaabd1000-2aaaaacd0000 ---p 0000d000 08:04 96256038                   /data/tdwadmin/tdwenv/jdk1.6.0_17/jre/lib/amd64/libverify.so
2aaaaacd0000-2aaaaacd3000 rwxp 0000c000 08:04 96256038                   /data/tdwadmin/tdwenv/jdk1.6.0_17/jre/lib/amd64/libverify.so
2aaaaacd3000-2aaaaacfc000 r-xp 00000000 08:04 96256017                   /data/tdwadmin/tdwenv/jdk1.6.0_17/jre/lib/amd64/libjava.so
2aaaaacfc000-2aaaaadfb000 ---p 00029000 08:04 96256017                   /data/tdwadmin/tdwenv/jdk1.6.0_17/jre/lib/amd64/libjava.so
2aaaaadfb000-2aaaaae02000 rwxp 00028000 08:04 96256017                   /data/tdwadmin/tdwenv/jdk1.6.0_17/jre/lib/amd64/libjava.so

推断是本地动态库有问题，重新编译动态库或拷贝合适的动态库，问题解决。