You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-dev@hadoop.apache.org by "Patrick Winters (JIRA)" <ji...@apache.org> on 2008/10/29 17:28:46 UTC

[jira] Commented: (HADOOP-2953) namenode doesn't start if group id cannot be resolved to name

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

Patrick Winters commented on HADOOP-2953:
-----------------------------------------

I have a similar problem running hadoop in the Sun Grid Engine, but this occurs when I'm using the CLI.  It is as (Nicholas) said, that the command `groups` fails.  In SGE, you get assigned an effective gid when your task submission runs, which doesn't map to a name.  I've created a patch which uses only real gid's and ignores effective ones.  Ultimately it uses `id -rgn` instead of `groups`

javax.security.auth.login.LoginException: Login failed: id: cannot find name for group ID 20030
        at org.apache.hadoop.security.UnixUserGroupInformation.login(UnixUserGroupInformation.java:250)

> namenode doesn't start if group id cannot be resolved to name
> -------------------------------------------------------------
>
>                 Key: HADOOP-2953
>                 URL: https://issues.apache.org/jira/browse/HADOOP-2953
>             Project: Hadoop Core
>          Issue Type: Bug
>          Components: dfs
>    Affects Versions: 0.16.0
>         Environment: Linux n510 2.6.22-3-686 #1 SMP Mon Nov 12 08:32:57 UTC 2007 i686 GNU/Linux
> Java:
> java version "1.5.0_14"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_14-b03)
> Java HotSpot(TM) Client VM (build 1.5.0_14-b03, mixed mode, sharing)
> PAM: ldap
>            Reporter: Andrew Gudkov
>            Priority: Minor
>
> Namenode failes to start because unix group name for my user can't be got. First, system threw rather obscure message:
> {quote}
> ERROR dfs.NameNode (NameNode.java:main(856)) - java.lang.NullPointerException
>         at org.apache.hadoop.dfs.FSNamesystem.close(FSNamesystem.java:428)
>         at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:237)
>         at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
>         at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
>         at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
>         at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
>         at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)
> {quote}
> I traversed through stack trace entries, and found (FSNamesystem:237) this code
> {quote}
> 233   FSNamesystem(NameNode nn, Configuration conf) throws IOException {
>  234     try {
>  235       initialize(nn, conf);
>  236     } catch(IOException e) {
>  237       close();
>  238       throw e;
>  239     }
>  240   }
> {quote}
> Inserting e.printStackTrace() gave me next
> {quote}
> dfs.NameNodeMetrics (NameNodeMetrics.java:<init>(76)) - Initializing NameNodeMeterics using context object:org.apache.hadoop.metrics.spi.NullContext
> java.io.IOException: javax.security.auth.login.LoginException: Login failed: id: cannot find name for group ID 1040
>         at org.apache.hadoop.security.UnixUserGroupInformation.login(UnixUserGroupInformation.java:250)
>         at org.apache.hadoop.security.UnixUserGroupInformation.login(UnixUserGroupInformation.java:268)
>         at org.apache.hadoop.dfs.FSNamesystem.setConfigurationParameters(FSNamesystem.java:330)
>         at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:249)
>         at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
>         at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
>         at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
>         at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
>         at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
>         at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)
>         at org.apache.hadoop.dfs.FSNamesystem.setConfigurationParameters(FSNamesystem.java:332)
>         at org.apache.hadoop.dfs.FSNamesystem.initialize(FSNamesystem.java:249)
>         at org.apache.hadoop.dfs.FSNamesystem.<init>(FSNamesystem.java:235)
>         at org.apache.hadoop.dfs.NameNode.initialize(NameNode.java:130)
>         at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:175)
>         at org.apache.hadoop.dfs.NameNode.<init>(NameNode.java:161)
>         at org.apache.hadoop.dfs.NameNode.createNameNode(NameNode.java:843)
>         at org.apache.hadoop.dfs.NameNode.main(NameNode.java:852)
> {quote}
> And this is true - command "groups" returns the same - id: cannot find name for group ID 1040.

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