Return-Path: Delivered-To: apmail-hadoop-core-user-archive@www.apache.org Received: (qmail 52420 invoked from network); 18 Mar 2008 14:52:08 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Mar 2008 14:52:08 -0000 Received: (qmail 72827 invoked by uid 500); 18 Mar 2008 14:52:02 -0000 Delivered-To: apmail-hadoop-core-user-archive@hadoop.apache.org Received: (qmail 72784 invoked by uid 500); 18 Mar 2008 14:52:02 -0000 Mailing-List: contact core-user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: core-user@hadoop.apache.org Delivered-To: mailing list core-user@hadoop.apache.org Received: (qmail 72775 invoked by uid 99); 18 Mar 2008 14:52:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2008 07:52:02 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of earzur@gmail.com designates 209.85.200.170 as permitted sender) Received: from [209.85.200.170] (HELO wf-out-1314.google.com) (209.85.200.170) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Mar 2008 14:51:24 +0000 Received: by wf-out-1314.google.com with SMTP id 27so6382385wfd.2 for ; Tue, 18 Mar 2008 07:51:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=sOv3/kL8RwHeZhp3ReBZ+AXJAVjInUgseuFAIIWtMcE=; b=EELNsXvexWvPbnAUgVvAyt4PB4GNxafIvV7F+ukvT0IM+Jh4nYJfig1D/zNj3uRoEETLkGKXqlHi0kn7NI+nRTfnsC1uKSO6otFrBexx+5jIS8A2i5iyfx+OpZI9M65h1ZVuw/5pkyTikl23QVUEC/k4y+QLryrzpArUTTohEdM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=QIYJtuYC5ckHgCD/vvplWyJ+kagztokGl6vMwp+yo+ozqyvUG0IKOywOd5czo0vzJLSuWSRmmhCxim9ERok3ZGgdUmbIPrgxbeCASBkzw9FttjCDryHYov9I1+C7TVcbtc8CaIyfgxupfQiZiQ0W6PnQ0ZxHqEAYEP/kaPRKd5E= Received: by 10.142.178.13 with SMTP id a13mr1022566wff.129.1205851887704; Tue, 18 Mar 2008 07:51:27 -0700 (PDT) Received: by 10.143.163.18 with HTTP; Tue, 18 Mar 2008 07:51:27 -0700 (PDT) Message-ID: Date: Tue, 18 Mar 2008 15:51:27 +0100 From: "Erwan Arzur" To: core-user@hadoop.apache.org Subject: Re: User information in 0.16.1 problems In-Reply-To: <643aa4870803160530h25de59ebybea500e23e236c97@mail.gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_24480_31160826.1205851887728" References: <643aa4870803160530h25de59ebybea500e23e236c97@mail.gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_24480_31160826.1205851887728 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hey, i was hit by the same issue. I have been able to run a MiniDFSCluster for my own unit tests under windows by setting: conf.set ("hadoop.job.ugi", "hadoop,hadoop"); That forces UnixUserGroupInfo to use the specified user,group. I think that UnixUserGroupInfo is not portable enough, even between unix (as one user reports whoami cannot be found under Solaris). Maybe using System.getProperty ("user.name") in the UnixUserGroupInformation class would solve that specific problem and be more portable ? That doesn't solve the groups listing which uses "bash -c groups" ... wow. I know a few BOFHs who would try to bite anyone daring to install bash on their boxes :-) I am not too familiar with the intricacies of UnixUserGroupInfo & hadoop's permissions, but maybe forcing to group "nobody" if the command fails would work ? Erwan On Sun, Mar 16, 2008 at 1:30 PM, Naama Kraus wrote: > Hi All > > I've been upgrading from 0.15.3 to 0.16.1. I ran some tests in the local > mode (no HDFS). The tests perform some MapReduce jobs. I ran into the > following problems: > > On Windows it complained that it does not find the 'whoami' command. Once > I > fixed that, it did work. BUT, it didn't use to complain in 0.15.3. > On Linux, it had some problems with the 'id' command - "Failed to get the > current user's information: Login failed: id: cannot find name for group > ID > 1102921537" which it didn't use to in 0.15.3. > > Both look related to getting user information. > > My question is what has changed in 0.16.1 and whether there are new > requirements now for being able to submit jobs . > > Thanks for any help, > Naama > > -- > oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo 00 oo > 00 oo 00 oo > "If you want your children to be intelligent, read them fairy tales. If > you > want them to be more intelligent, read them more fairy tales." (Albert > Einstein) > ------=_Part_24480_31160826.1205851887728--