You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nutch.apache.org by "Brian Whitman (JIRA)" <ji...@apache.org> on 2007/01/24 18:44:49 UTC

[jira] Commented: (NUTCH-432) JAVA_PLATFORM with spaces (i.e. Mac OS X-ppc-32) breaks bin/nutch script

    [ https://issues.apache.org/jira/browse/NUTCH-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12467097 ] 

Brian Whitman commented on NUTCH-432:
-------------------------------------

Relatedly (I didn't want to open a new ticket because it's more or less the same problem) -- if your nutch basedir has spaces in it (like /Users/bwhitman/Desktop/n n/) the bin/nutch script breaks on the logdir:

-Dhadoop.log.dir=/Users/bwhitman/Desktop/n n/logs -Dhadoop.log.file=hadoop.log org.apache.nutch.crawl.Injector
Exception in thread "main" java.lang.NoClassDefFoundError: n/logs


> JAVA_PLATFORM with spaces (i.e. Mac OS X-ppc-32) breaks bin/nutch script
> ------------------------------------------------------------------------
>
>                 Key: NUTCH-432
>                 URL: https://issues.apache.org/jira/browse/NUTCH-432
>             Project: Nutch
>          Issue Type: Bug
>    Affects Versions: 0.9.0
>         Environment: Mac OS X PPC and Mac OS X Intel both break, Linux is so far OK
>            Reporter: Brian Whitman
>
> In some later nightly in the past few weeks (not sure when) the bin/nutch script stopped working on my Macs with 
> Exception in thread "main" java.lang.NoClassDefFoundError: OS
> On any command. I tracked it down to the JAVA_PLATFORM env variable that is used to try to find a native hadoop library. The line
> JAVA_PLATFORM=`CLASSPATH=${CLASSPATH} ${JAVA} org.apache.hadoop.util.PlatformName`
> in bin/nutch returns "Mac OS X-ppc-32", which then appears as
> -Djava.library.path=/Users/bwhitman/Desktop/nn/lib/native/Mac OS X-ppc-32
> in the java command line to start a nutch tool. 
> Not sure the best way to fix this, but I manually put 
> JAVA_PLATFORM='MacOSX/PPC'
> and the error went away.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.