$ java -version java version "1.6.0_18" Java(TM) SE Runtime Environment (build 1.6.0_18-b07) Java HotSpot(TM) 64-Bit Server VM (build 16.0-b13, mixed mode)
there is nothing in stderr, but here is part from stdout # # A fatal error has been detected by the Java Runtime Environment: # # SIGSEGV (0xb) at pc=0x00002b19ef8cc34e, pid=12633, tid=1104492864 # # JRE version: 6.0_18-b07 # Java VM: Java HotSpot(TM) 64-Bit Server VM (16.0-b13 mixed mode linux-amd64 ) # Problematic frame: # V [libjvm.so+0x2de34e] # # An error report file with more information is saved as: # /hadoop/mapred/local/taskTracker/jobcache/job_201003072002_0002/attempt_201003072002_0002_r_000019_0/work/hs_err_pid12633.log # # If you would like to submit a bug report, please visit: # http://java.sun.com/webapps/bugreport/crash.jsp # Also, file which is mentioned above (hs_err_pid12633.log) does not exist. Jean-Daniel Cryans-2 wrote: > >> i'm using hadoop 0.20.1 and hbase 0.20.3 > > Sorry I meant java version. > >> >> i already try to put >> >> -XX:ErrorFile=/opt/hadoop/hadoop/logs/java/java_error%p.log >> >> in hadoop-env.sh as HADOOP_OPTS but after reduce crash i did not find any >> file on that path. > > Todd doesn't talk about that, he said: > >> Generally along with a nonzero exit code you should see something in >> the stderr for that attempt. If you look on the TaskTracker inside >> logs/userlogs/attempt_<the failed attempt>/stderr do you see anything >> useful? > > -- View this message in context: http://old.nabble.com/Task-process-exit-with-nonzero-status-of-134...-tp27814144p27814802.html Sent from the HBase User mailing list archive at Nabble.com.
