nutch-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebastian Nagel (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (NUTCH-2514) Segmentation Fault issue while running crawl job.
Date Thu, 10 May 2018 11:00:00 GMT

     [ https://issues.apache.org/jira/browse/NUTCH-2514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Sebastian Nagel resolved NUTCH-2514.
------------------------------------
       Resolution: Incomplete
    Fix Version/s:     (was: 2.4)

Hi [~kshitij], Nutch does not have any native code which could cause a segmentation fault,
only Java, the native Hadoop library, or a third-party library could be responsible.

It's also not possible to localize the reason with the provided information. We need the native
stack trace (eg. hs_err_pid*.log) of the crashed task. If you can provide more details, please
reopen the issue. Thanks!

> Segmentation Fault issue  while running crawl job.
> --------------------------------------------------
>
>                 Key: NUTCH-2514
>                 URL: https://issues.apache.org/jira/browse/NUTCH-2514
>             Project: Nutch
>          Issue Type: Bug
>          Components: crawldb, fetcher, indexer, parser
>    Affects Versions: 2.3.1
>         Environment: OS- centos-release-6-9.el6.12.3.x86_64
> Hadoop-2.5.2 cluster with 5 nodes
> Nutch - 2.3.1
> Hbase-0.98.8
> Solr-5.4.1
>            Reporter: Kshitij Shukla
>            Priority: Major
>
> Error occurs while running crawl job in on fetching, parsing and indexing phase. error
posting below:-
> ExitCodeException exitCode=139: /bin/bash: line 1: 68684 Segmentation fault      /usr/lib/jvm/java-1.7.0-openjdk-1.7.0.161.x86_64/bin/java
-Djava.net.preferIPv4Stack=true -Dhadoop.metrics.log.level=WARN -Xmx13312m -Djava.io.tmpdir=/tmp/hadoop-root/nm-local-dir/usercache/root/appcache/application_1519286094099_0016/container_1519286094099_0016_01_000003/tmp
-Dlog4j.configuration=container-log4j.properties -Dyarn.app.container.log.dir=/home/c1/hadoop-2.5.2/logs/userlogs/application_1519286094099_0016/container_1519286094099_0016_01_000003
-Dyarn.app.container.log.filesize=0 -Dhadoop.root.logger=INFO,CLA org.apache.hadoop.mapred.YarnChild
95.142.101.139 35714 attempt_1519286094099_0016_r_000000_0 3 > /home/c1/hadoop-2.5.2/logs/userlogs/application_1519286094099_0016/container_1519286094099_0016_01_000003/stdout
2> /home/c1/hadoop-2.5.2/logs/userlogs/application_1519286094099_0016/container_1519286094099_0016_01_000003/stderr
> 	at org.apache.hadoop.util.Shell.runCommand(Shell.java:538)
> 	at org.apache.hadoop.util.Shell.run(Shell.java:455)
> 	at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:702)
> 	at org.apache.hadoop.yarn.server.nodemanager.DefaultContainerExecutor.launchContainer(DefaultContainerExecutor.java:195)
> 	at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:300)
> 	at org.apache.hadoop.yarn.server.nodemanager.containermanager.launcher.ContainerLaunch.call(ContainerLaunch.java:81)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1152)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:622)
> 	at java.lang.Thread.run(Thread.java:748)



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message