You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by "Suresh Srinivas (JIRA)" <ji...@apache.org> on 2012/10/05 18:00:03 UTC

[jira] [Commented] (HADOOP-8884) DEBUG should be WARN for DEBUG util.NativeCodeLoader: Failed to load native-hadoop with error: java.lang.UnsatisfiedLinkError

    [ https://issues.apache.org/jira/browse/HADOOP-8884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13470417#comment-13470417 ] 

Suresh Srinivas commented on HADOOP-8884:
-----------------------------------------

Anthony, thanks for the patch. Making these logs from debug to warning makes sense. 

I suggest combining both those logs into a single log, along the lines:
{noformat}
        LOG.warn("Continuing after failing to load native-hadoop - java.library.path=" +
            System.getProperty("java.library.path") + " with error: "+ t);
{noformat}

                
> DEBUG should be WARN for DEBUG util.NativeCodeLoader: Failed to load native-hadoop with error: java.lang.UnsatisfiedLinkError
> -----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: HADOOP-8884
>                 URL: https://issues.apache.org/jira/browse/HADOOP-8884
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: util
>    Affects Versions: 2.0.1-alpha
>            Reporter: Anthony Rojas
>            Assignee: Anthony Rojas
>         Attachments: HADOOP-8884.patch
>
>
> Recommending to change the following debug message and promote it to a warning instead:
> 12/07/02 18:41:44 DEBUG util.NativeCodeLoader: Failed to load native-hadoop with error: java.lang.UnsatisfiedLinkError: /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0: /lib64/libc.so.6: version `GLIBC_2.6' not found (required by /usr/lib/hadoop/lib/native/libhadoop.so.1.0.0)

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira