[
https://issues.apache.org/jira/browse/HDFS-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Nauroth updated HDFS-6254:
--------------------------------
Description: When namenode is not started, the libhdfs client will cause
segment fault while connecting. (was: when namenode is not started, the client
will cause segment falut while connecting, gdb info as followed:
Core was generated by `./test -d'.
Program terminated with signal 6, Aborted.
#0 0x0000003735c328e5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.107.el6_4.5.x86_64 jdk-1.7.0_21-fcs.x86_64
keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-10.el6_4.6.x86_64
libcom_err-1.41.12-14.el6_4.4.x86_64 libgcc-4.4.7-3.el6.x86_64
libselinux-2.0.94-5.3.el6_4.1.x86_64 libstdc++-4.4.7-3.el6.x86_64
libxml2-2.7.6-12.el6_4.1.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) bt
#0 0x0000003735c328e5 in raise () from /lib64/libc.so.6
#1 0x0000003735c340c5 in abort () from /lib64/libc.so.6
#2 0x00007f1beacba865 in os::abort(bool) () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#3 0x00007f1beae1ab77 in VMError::report_and_die() () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#4 0x00007f1beacbe370 in JVM_handle_linux_signal () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#5 <signal handler called>
#6 0x00007f1beaad8691 in jni_invoke_nonstatic(JNIEnv_*, JavaValue*, _jobject*,
JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#7 0x00007f1beaaf3ed0 in jni_CallBooleanMethodV () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#8 0x00007f1beb2a1487 in invokeMethod (env=0x2fd01d8, retval=0x7fff94dcb3f0,
methType=INSTANCE, instObj=0x7f1bb8009640,
className=0x7f1beb2a8350 "org/apache/hadoop/fs/FileSystem",
methName=0x7f1beb2a8674 "exists",
methSignature=0x7f1beb2a8e90 "(Lorg/apache/hadoop/fs/Path;)Z")
at
/home/hkx/hadoop-2.2.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/jni_helper.c:252
#9 0x00007f1beb2a39b5 in hdfsExists (fs=0x7f1bb8009640, path=<value optimized
out>)
at
/home/hkx/hadoop-2.2.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/hdfs.c:1366
#10 0x0000000000411561 in CChildProcess::CombineFile (this=0x7fff94dccd20,
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=0x7f1bb8009640) at CChildProcess.cpp:267
#11 0x00000000004120f0 in CChildProcess::Run (this=0x7fff94dccd20) at
CChildProcess.cpp:116
#12 0x000000000040d8cb in CProcessMgr::StartAProcess (this=0x19d1820,
strCustomID="(", pChildProcess=0x7fff94dccd20)
at CProcessMgr.cpp:112
#13 0x000000000041091e in CTimerService::Run (this=0x7fff94dcd280) at
CTimerService.cpp:46
#14 0x000000000040db74 in main (argc=<value optimized out>, argv=<value
optimized out>) at main.cpp:92
(gdb) quit)
Shortening description and moving backtrace to comment:
Core was generated by `./test -d'.
Program terminated with signal 6, Aborted.
#0 0x0000003735c328e5 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
glibc-2.12-1.107.el6_4.5.x86_64 jdk-1.7.0_21-fcs.x86_64
keyutils-libs-1.4-4.el6.x86_64 krb5-libs-1.10.3-10.el6_4.6.x86_64
libcom_err-1.41.12-14.el6_4.4.x86_64 libgcc-4.4.7-3.el6.x86_64
libselinux-2.0.94-5.3.el6_4.1.x86_64 libstdc++-4.4.7-3.el6.x86_64
libxml2-2.7.6-12.el6_4.1.x86_64 zlib-1.2.3-29.el6.x86_64
(gdb) bt
#0 0x0000003735c328e5 in raise () from /lib64/libc.so.6
#1 0x0000003735c340c5 in abort () from /lib64/libc.so.6
#2 0x00007f1beacba865 in os::abort(bool) () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#3 0x00007f1beae1ab77 in VMError::report_and_die() () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#4 0x00007f1beacbe370 in JVM_handle_linux_signal () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#5 <signal handler called>
#6 0x00007f1beaad8691 in jni_invoke_nonstatic(JNIEnv_, JavaValue, _jobject*,
JNICallType, _jmethodID*, JNI_ArgumentPusher*, Thread*) () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#7 0x00007f1beaaf3ed0 in jni_CallBooleanMethodV () from
/usr/java/jdk1.7.0_21/jre/lib/amd64/server/libjvm.so
#8 0x00007f1beb2a1487 in invokeMethod (env=0x2fd01d8, retval=0x7fff94dcb3f0,
methType=INSTANCE, instObj=0x7f1bb8009640,
className=0x7f1beb2a8350 "org/apache/hadoop/fs/FileSystem",
methName=0x7f1beb2a8674 "exists",
methSignature=0x7f1beb2a8e90 "(Lorg/apache/hadoop/fs/Path;)Z")
at
/home/hkx/hadoop-2.2.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/jni_helper.c:252
#9 0x00007f1beb2a39b5 in hdfsExists (fs=0x7f1bb8009640, path=<value optimized
out>)
at
/home/hkx/hadoop-2.2.0-src/hadoop-hdfs-project/hadoop-hdfs/src/main/native/libhdfs/hdfs.c:1366
#10 0x0000000000411561 in CChildProcess::CombineFile (this=0x7fff94dccd20,
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=0x7f1bb8009640) at CChildProcess.cpp:267
#11 0x00000000004120f0 in CChildProcess::Run (this=0x7fff94dccd20) at
CChildProcess.cpp:116
#12 0x000000000040d8cb in CProcessMgr::StartAProcess (this=0x19d1820,
strCustomID="(", pChildProcess=0x7fff94dccd20)
at CProcessMgr.cpp:112
#13 0x000000000041091e in CTimerService::Run (this=0x7fff94dcd280) at
CTimerService.cpp:46
#14 0x000000000040db74 in main (argc=<value optimized out>, argv=<value
optimized out>) at main.cpp:92
(gdb) quit
> 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
> 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)
