[
https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13975480#comment-13975480
]
huang ken commented on HDFS-6254:
---------------------------------
Lastest backtrace as followed:
#0 0x0000003735c328e5 in raise () from /lib64/libc.so.6
#1 0x0000003735c340c5 in abort () from /lib64/libc.so.6
#2 0x00007fddc4901535 in os::abort(bool) () from
/usr/java/jdk1.7.0_55/jre/lib/amd64/server/libjvm.so
#3 0x00007fddc4a80457 in VMError::report_and_die() () from
/usr/java/jdk1.7.0_55/jre/lib/amd64/server/libjvm.so
#4 0x00007fddc4905ebf in JVM_handle_linux_signal () from
/usr/java/jdk1.7.0_55/jre/lib/amd64/server/libjvm.so
#5 <signal handler called>
#6 0x00007fddc471dac8 in jni_invoke_nonstatic(JNIEnv_*, JavaValue*, _jobject*,
JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) () from
/usr/java/jdk1.7.0_55/jre/lib/amd64/server/libjvm.so
#7 0x00007fddc4730629 in jni_CallBooleanMethodV () from
/usr/java/jdk1.7.0_55/jre/lib/amd64/server/libjvm.so
#8 0x00007fddc4f59847 in invokeMethod (env=0x15de9e8, retval=0x7fffa6d2bbd0,
methType=INSTANCE, instObj=0x2074998,
className=0x7fddc4f603d0 "org/apache/hadoop/fs/FileSystem",
methName=0x7fddc4f60692 "mkdirs",
methSignature=0x7fddc4f61038 "(Lorg/apache/hadoop/fs/Path;)Z")
at
/home/hkx/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/jni_helper.c:252
#9 0x00007fddc4f5affa in hdfsCreateDirectory (fs=0x2074998,
path=0x7fffa6d2c308 "/tmp/root/00000629/")
at
/home/hkx/hadoop-2.4.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/hdfs.c:1865
#10 0x00000000004115f3 in CChildProcess::CombineFile (this=0x7fffa6d2d510,
objFileName=..., vcSortInfo=<value optimized out>,
files_map=Traceback (most recent call last):
File "/usr/lib64/../share/gdb/python/libstdcxx/v6/printers.py", line 382, in
children
valuetype = self.val.type.template_argument(1)
RuntimeError: No type named hdfsFile_internal.
std::map with 0 elements, fs=0x2074998) at CChildProcess.cpp:283
#11 0x00000000004120f4 in CChildProcess::Run (this=0x7fffa6d2d510) at
CChildProcess.cpp:122
#12 0x000000000040d8f3 in CProcessMgr::StartAProcess (this=0xa34f30,
strCustomID="\210", pChildProcess=0x7fffa6d2d510)
at CProcessMgr.cpp:114
#13 0x000000000041094e in CTimerService::Run (this=0x7fffa6d2da70) at
CTimerService.cpp:46
#14 0x000000000040dba4 in main (argc=<value optimized out>, argv=<value
optimized out>) at main.cpp:92
> hdfsConnect segment fault where namenode not connected
> ------------------------------------------------------
>
> Key: HDFS-6254
> URL: https://issues.apache.org/jira/browse/HDFS-6254
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: libhdfs
> Affects Versions: 2.2.0
> Environment: Linux Centos 64bit
> Reporter: huang ken
>
> When namenode is not started, the libhdfs client will cause segment fault
> while connecting.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
