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 "Eli Collins (JIRA)" <ji...@apache.org> on 2012/08/01 05:32:35 UTC
[jira] [Moved] (HADOOP-8639) Shell doesn't give specific details
about why it can't create a file
[ https://issues.apache.org/jira/browse/HADOOP-8639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eli Collins moved HDFS-1913 to HADOOP-8639:
-------------------------------------------
Component/s: (was: hdfs client)
fs
Affects Version/s: (was: 0.20.2)
Issue Type: Improvement (was: Bug)
Key: HADOOP-8639 (was: HDFS-1913)
Project: Hadoop Common (was: Hadoop HDFS)
> Shell doesn't give specific details about why it can't create a file
> --------------------------------------------------------------------
>
> Key: HADOOP-8639
> URL: https://issues.apache.org/jira/browse/HADOOP-8639
> Project: Hadoop Common
> Issue Type: Improvement
> Components: fs
> Reporter: Kathleen Ting
> Labels: newbie
>
> It would be a lot more useful to print an error message indicating why that you can't create the file - e.g. can't create a directory with the name of the file you're trying to write to.
> Also, the log file isn't much better. You'll see exceptions that look like this:
> 2011-04-14 12:29:37,757 WARN org.apache.hadoop.security.ShellBasedUnixGroupsMapping: got exception trying to get groups for user ___
> org.apache.hadoop.util.Shell$ExitCodeException: id: ___: No such user
> at org.apache.hadoop.util.Shell.runCommand(Shell.java:255)
> at org.apache.hadoop.util.Shell.run(Shell.java:182)
> at org.apache.hadoop.util.Shell$ShellCommandExecutor.execute(Shell.java:375) at org.apache.hadoop.util.Shell.execCommand(Shell.java:461)
> at org.apache.hadoop.util.Shell.execCommand(Shell.java:444) at org.apache.hadoop.security.ShellBasedUnixGroupsMapping.getUnixGroups(ShellBasedUnixGroupsMapping.java:66)
> at org.apache.hadoop.security.ShellBasedUnixGroupsMapping.getGroups(ShellBasedUnixGroupsMapping.java:43)
> at org.apache.hadoop.security.Groups.getGroups(Groups.java:79)
> at org.apache.hadoop.security.UserGroupInformation.getGroupNames(UserGroupInformation.java:1022)
> at org.apache.hadoop.hdfs.server.namenode.FSPermissionChecker.<init>(FSPermissionChecker.java:50)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkPermission(FSNamesystem.java:4920)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.checkTraverse(FSNamesystem.java:4903)
> at org.apache.hadoop.hdfs.server.namenode.FSNamesystem.getFileInfo(FSNamesystem.java:1878)
> at org.apache.hadoop.hdfs.server.namenode.NameNode.getFileInfo(NameNode.java:795)
> at sun.reflect.GeneratedMethodAccessor88.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.hadoop.ipc.RPC$Server.call(RPC.java:557)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1416)
> at org.apache.hadoop.ipc.Server$Handler$1.run(Server.java:1412)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.security.auth.Subject.doAs(Subject.java:396)
> at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1115)
> at org.apache.hadoop.ipc.Server$Handler.run(Server.java:1410)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira