From generalqcarrillo@example.net Wed Jul 01 05:17:39 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 70318 invoked from network); 1 Jul 2009 05:17:39 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 05:17:39 -0000 Received: (qmail 5162 invoked by uid 500); 1 Jul 2009 05:17:49 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 5081 invoked by uid 500); 1 Jul 2009 05:17:49 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 5071 invoked by uid 99); 1 Jul 2009 05:17:48 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 05:17:48 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO e23smtp06.au.ibm.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 05:17:38 +0000 Received: from d23relay02.au.ibm.com (d23relay02.au.ibm.com [83.161.120.155]) by e23smtp06.au.ibm.com (8.13.1/8.13.1) with ESMTP id n615H5O8026571 for <qcarrillo@example.net>; Wed, 1 Jul 2009 15:17:05 +1000 Received: from d23av04.au.ibm.com (d23av04.au.ibm.com [83.161.120.155]) by d23relay02.au.ibm.com (8.13.8/8.13.8/NCO v9.2) with ESMTP id n615HFNe884786 for <qcarrillo@example.net>; Wed, 1 Jul 2009 15:17:15 +1000 Received: from d23av04.au.ibm.com (loopback [83.161.120.155]) by d23av04.au.ibm.com (83.161.120.15560308/8.13.3) with ESMTP id n615HFg4004197 for <qcarrillo@example.net>; Wed, 1 Jul 2009 15:17:15 +1000 Received: from d23m0037.cn.ibm.com (d23m0037.cn.ibm.com [83.161.120.155]) by d23av04.au.ibm.com (83.161.120.15560308/8.12.11) with ESMTP id n615HEES004162; Wed, 1 Jul 2009 15:17:15 +1000 In-Reply-To: <qcarrillo@example.net> To: Konstantin Shvachko <qcarrillo@example.net> Cc: qcarrillo@example.net, Feng WF Wang <qcarrillo@example.net>, qcarrillo@example.net MIME-Version: 1.0 Subject: Re: HDFS name node HA roadmap X-Mailer: Lotus Notes Release 7.0 HF277 June 21, 2006 Message-ID: <qcarrillo@example.net> From: Jie Qiu <qcarrillo@example.net> Date: Wed, 1 Jul 2009 13:17:20 +0800 X-MIMETrack: Serialize by Router on D23M0037/23/M/IBM(Release 8.0.1|February 07, 2008) at 07/01/2009 13:17:21, Serialize complete at 07/01/2009 13:17:21 Content-Type: multipart/alternative; boundary="=_alternative 001D0AFA482575E6_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 001D0AFA482575E6_= Content-Type: text/plain; charset="US-ASCII" Dear Shv I created new item for Hadoop HA in Hadoop. So, we can use it to start our discussion and put the feature in the roadmap of hadoop. https://issues.apache.org/jira/browse/HADOOP-6121 ================================================== True insight comes from within! Qiu Jie Cloud Computing Technology IBM China Research Lab. Tel: 8610-58748086 Tieline: 905-8086 FAX: 8610-58748330 Add.: Building 19 Zhongguancun Software Park, 8 Dongbeiwang WestRoad, Haidian District, Beijing,P.R.C.100094 Email: qcarrillo@example.net ================================================== --=_alternative 001D0AFA482575E6_=-- From generalqcarrillo@example.net Wed Jul 01 14:35:36 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 62954 invoked from network); 1 Jul 2009 14:35:36 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 14:35:36 -0000 Received: (qmail 23558 invoked by uid 500); 1 Jul 2009 14:35:46 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 23513 invoked by uid 500); 1 Jul 2009 14:35:45 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 23496 invoked by uid 99); 1 Jul 2009 14:35:45 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 14:35:45 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-vw0-f172.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 14:35:36 +0000 Received: by vwj2 with SMTP id 2so451406vwj.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 07:35:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=vHuCNp0JedKXaflJ7/o3kD/sUjIUkuO1gaSNa0mQCkM=; b=UoWx6KlscDP2xrbJC5hd+nWvVyadjwZdrqFwmLrt0CfqqbulLF4PkifRGvlWUuDmXG 84MblYf6nQTXivL3CEP6KIsCfhJpZ2WHi88mI634KToRwcPeQSqHjarDK+kHS733A8Ca EUh1MsB9UhZn0uDx6JBmdTX9WSfsFEflblSXo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=bQMuDH57dt0GimZgjupBoeVT9kDAL1tCp/Vq/WVr1+Dva+WAfvnFP8MuoqsiQgZsmZ asbLv649ZB5HM4FfHaRabxEAPT6mg6nic3H5Wf1luZGp1So65jlaF+72Tbw2fWbJC44g WyePBYe3Kgu2Cb7hIyWfu9KChPK1SOyEF2q+U= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id f20mr9001341vcj.70.1246458915125; Wed, 01 Jul 2009 07:35:15 -0700 (PDT) Date: Wed, 1 Jul 2009 22:35:15 +0800 Message-ID: <qcarrillo@example.net> Subject: fail to setup passphraseless ssh and need some help From: fred wang <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: multipart/alternative; boundary=0016e6475d18dcfc12046da5d4a5 X-Virus-Checked: Checked by ClamAV on apache.org --0016e6475d18dcfc12046da5d4a5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi all, I failed to setup passphraseless ssh(I mean, I still need to input password to do ssh localhost) when I tried to configure Hadoop to run on psuedo-distributed operation, could anyone help me solve this issue? Thanks! (1)I use the Putty0.6 to remote access to Ubuntu by SSH. (2) execution steps and ouput $ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa Generating public/private dsa key pair. Your identification has been saved in /home/xxx/.ssh/id_dsa. Your public key has been saved in /home/xxx/.ssh/id_dsa.pub. The key fingerprint is: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 xxx **note: it doesn't have message 'Enter passphrase (empty for no passphrase): Enter same passphrase again: ' which appear in some introductory paper. " $ cat ~/.ssh/id_dsa.pub >> ~/.ssh/authorized_keys no output $ ssh localhost The authenticity of host 'localhost (83.161.120.155)' can't be established. RSA key fingerprint is 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4. Are you sure you want to continue connecting (yes/no)? yes Warning: Permanently added 'localhost' (RSA) to the list of known hosts. xxx@localhost's password: --0016e6475d18dcfc12046da5d4a5-- From generalqcarrillo@example.net Wed Jul 01 15:19:59 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 78111 invoked from network); 1 Jul 2009 15:19:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 15:19:59 -0000 Received: (qmail 3218 invoked by uid 500); 1 Jul 2009 15:20:09 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 3136 invoked by uid 500); 1 Jul 2009 15:20:08 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 3126 invoked by uid 99); 1 Jul 2009 15:20:08 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 15:20:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO qw-out-2122.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 15:19:57 +0000 Received: by qw-out-2122.google.com with SMTP id 8so379824qwh.35 for <qcarrillo@example.net>; Wed, 01 Jul 2009 08:19:36 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=vyGAoU8Qr9Xmda7cpYufjslSa1Ne51VvtxN+U1D+CtU=; b=m6PZ2cec3zUfOEF7nukV4OTTpWSkz5jI/L8dRcQlb2WXHDnh96SbUAwb76l0SXiEEt zWuuyPKkAYJEZRY9UpV82u8/FFK+1ZEKUPrR8ISptGd8noIxSeoX9bNiPxyocm9pDStz Xb1UVxuN7QycAX6qkVDFdXdECrM1Js/UuNEPM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=HwtWqxc3rnxR0DUDRoaTKkk2ZL9u97FIQfVB80+CGA8djeAvRWvMNgt4vVTRi378qu 8IgQHhvDpDI4HHxg7DqTiQQi+p0u/nLLnoF+VuQCybpGzgdDI2+ZLaP9urJ7d2EujJIf uIHbDDvwyD8+HbdB9TzKgZbkfEzSm/MHPMzUs= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id f6mr2457756iba.9.1246461576265; Wed, 01 Jul 2009 08:19:36 -0700 (PDT) Date: Wed, 1 Jul 2009 17:19:36 +0200 Message-ID: <qcarrillo@example.net> Subject: I have a problem is sending you an email From: C J <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: multipart/alternative; boundary=00221532cb647ac0da046da6737c X-Virus-Checked: Checked by ClamAV on apache.org --00221532cb647ac0da046da6737c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hallo, I am trying to send an email as a follow up to my previous one that I have sent yesterday, but for some reasons my email is filtered. Do you have any filtering rules on the content of the email, title of the email,... thank you for helping,me --00221532cb647ac0da046da6737c-- From generalqcarrillo@example.net Wed Jul 01 16:16:11 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 8746 invoked from network); 1 Jul 2009 16:16:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 16:16:11 -0000 Received: (qmail 94014 invoked by uid 500); 1 Jul 2009 16:16:21 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 93959 invoked by uid 500); 1 Jul 2009 16:16:21 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 93948 invoked by uid 99); 1 Jul 2009 16:16:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 16:16:20 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO mrout1.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 16:16:09 +0000 Received: from [83.161.120.155] (snvvpn1-10-73-152-c44.hq.corp.yahoo.com [83.161.120.155]) by mrout1.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id n61GFM2b004992 for <qcarrillo@example.net>; Wed, 1 Jul 2009 09:15:23 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:content-type:content-transfer-encoding; b=algaMinGqSXM2z2FLw52ejAD57MOWOPzer6Df2EDFDxtD4YVysP3IwZGgRHG9bNy Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 09:15:21 -0700 From: Konstantin Boudnik <qcarrillo@example.net> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: "qcarrillo@example.net" <qcarrillo@example.net> Subject: Re: fail to setup passphraseless ssh and need some help References: <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Make sure that your ~/.ssh/authorized_keys has permissions 600 Cos On 7/1/09 7:35 AM, fred wang wrote: > Hi all, > > I failed to setup passphraseless ssh(I mean, I still need to input > password to do ssh localhost) when I tried to configure Hadoop to run on > psuedo-distributed operation, could anyone help me solve this issue? > Thanks! > > (1)I use the Putty0.6 to remote access to Ubuntu by SSH. > > (2) execution steps and ouput > > $ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa > Generating public/private dsa key pair. > Your identification has been saved in /home/xxx/.ssh/id_dsa. > Your public key has been saved in /home/xxx/.ssh/id_dsa.pub. > The key fingerprint is: > 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 xxx > > > **note: it doesn't have message 'Enter passphrase (empty for no > passphrase): > Enter same passphrase again: ' which appear in some introductory paper. > " > > $ cat ~/.ssh/id_dsa.pub>> ~/.ssh/authorized_keys > no output > > $ ssh localhost > The authenticity of host 'localhost (83.161.120.155)' can't be established. > RSA key fingerprint is 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4. > Are you sure you want to continue connecting (yes/no)? yes > Warning: Permanently added 'localhost' (RSA) to the list of known hosts. > xxx@localhost's password: From generalqcarrillo@example.net Wed Jul 01 17:16:17 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 35966 invoked from network); 1 Jul 2009 17:16:17 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 17:16:17 -0000 Received: (qmail 4821 invoked by uid 500); 1 Jul 2009 17:16:27 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 4751 invoked by uid 500); 1 Jul 2009 17:16:27 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 4741 invoked by uid 99); 1 Jul 2009 17:16:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 17:16:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-px0-f171.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 17:16:19 +0000 Received: by pxi1 with SMTP id 1so900633pxi.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 10:15:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=u/DKF2sN2nBHr6KBPUjPDsCAGsf+F8otNVoecBpHleg=; b=RQjnLGfT18Oy+XC+/ldLfUs5/jgL9TfY6beK5MlTAzrjd1S+GaNHXQ2Xc9Rto0vVFY tMUenSwW4DoGPU8chID5LbgV9tPxLZJfdkYNR2Q6H70rYvTAigaGCbCFr2xUfdncmUQ3 AUKlOpX7sOISHdyjlUeDOZKShgwv8485wSZ/0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=fiM4SH061sJDkJi2rx5wF7SfOAnLkFOmkmX+Vw9siJoH1ee4yCgiXJRDbglILBlGEP Rh8vv2p34uPKQsNQNSadRG9c+3K+IvTGuDRuetPQGlbHP5oJXao5JeSbNPbAuEJdk1ss ww2gCLcDNNzOsDH9QecxaodF3n5YzaI1ZJDNo= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id b19mr1113091wfc.185.1246468559366; Wed, 01 Jul 2009 10:15:59 -0700 (PDT) Date: Thu, 2 Jul 2009 02:15:59 +0900 Message-ID: <qcarrillo@example.net> Subject: 0.20: Configured Capacity: 0 (0 KB) From: "Bogdan M. Maryniuk" <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello! Not sure I am on right mailing list, because I had a hard time to subscribe to at least one of those listed... Sorry in advance. I've just installed pretty much standard way on a 4 nodes hadoop cluster, redirected all tmp/fsimage stuff to a pretty much solid space, but I am getting zero capacity and inability to put any kind of file. Is this is a correct behavior? If no, what I am missing, please? Version: 0.20, Java 1.6 Update 13. I see no tracebacks, no errors, no warnings in any logs. Directories are all writable by hadoop user and no problem with a space. All daemons are running, everything looks OK so far. Just zero capacity filesystem that are already 100% full. Thanks! $ hadoop dfsadmin -report Configured Capacity: 0 (0 KB) Present Capacity: 27648 (27 KB) DFS Remaining: 0 (0 KB) DFS Used: 27648 (27 KB) DFS Used%: 100% Under replicated blocks: 0 Blocks with corrupt replicas: 0 Missing blocks: 0 ------------------------------------------------- Datanodes available: 3 (3 total, 0 dead) Name: 83.161.120.155:50010 Decommission Status : Normal Configured Capacity: 0 (0 KB) DFS Used: 9216 (9 KB) Non DFS Used: 0 (0 KB) DFS Remaining: 0(0 KB) DFS Used%: 100% DFS Remaining%: 0% Last contact: Thu Jul 02 02:03:06 JST 2009 Name: 83.161.120.155:50010 Decommission Status : Normal Configured Capacity: 0 (0 KB) DFS Used: 9216 (9 KB) Non DFS Used: 0 (0 KB) DFS Remaining: 0(0 KB) DFS Used%: 100% DFS Remaining%: 0% Last contact: Thu Jul 02 02:03:04 JST 2009 Name: 83.161.120.155:50010 Decommission Status : Normal Configured Capacity: 0 (0 KB) DFS Used: 9216 (9 KB) Non DFS Used: 0 (0 KB) DFS Remaining: 0(0 KB) DFS Used%: 100% DFS Remaining%: 0% Last contact: Thu Jul 02 02:03:04 JST 2009 -- Kind regards, BM Things, that are stupid at the beginning, rarely ends up wisely. From generalqcarrillo@example.net Wed Jul 01 18:55:22 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 2714 invoked from network); 1 Jul 2009 18:55:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 18:55:22 -0000 Received: (qmail 43847 invoked by uid 500); 1 Jul 2009 18:55:32 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 43793 invoked by uid 500); 1 Jul 2009 18:55:32 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 43783 invoked by uid 99); 1 Jul 2009 18:55:32 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 18:55:32 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-pz0-f196.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 18:55:23 +0000 Received: by pzk34 with SMTP id 34so990064pzk.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 11:55:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=9xItdnLVk0VFGJowT00MxTuwSX23xrR95zubhwOIQOo=; b=TWOGWItBSLzSFhlkYWRUaQucy85U9D9CxWWyUX4b+gLOoojqWqGPhti43LFkpPcTDG kEYvoFrkmbhtM1Gr0bYooHOWMXaIZz+QWrOi+vt8VT43K48e0J1DHnZHKHfUuYZ06qg3 QgSWYdUA9VmCGs9c/EaDsUURFdsMQgWxjponU= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=tNDku90edpOiz0SyAx6BLA/D5WRnTRTY9eYn15xmllCVIwZsTXi/8sVUL3KJIVrMu2 8zkNGsPSdGSUWsKOHpmTzSE9BFz13HlA0mHNqHqfjUHk26GuMGKxb41p4/9ZY5Mggjsu cKw4rS1oawB+heAtB2C13QBUB6VrQAP/cpBZ4= Received: by 83.161.120.155 with SMTP id b14mr831413wfe.67.1246474502783; Wed, 01 Jul 2009 11:55:02 -0700 (PDT) Received: from ?83.161.120.155? (c-76-103-176-123.hsd1.ca.comcast.net [83.161.120.155]) by mx.google.com with ESMTPS id 22sm4833064wfi.32.283.161.120.155.55.01 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 01 Jul 2009 11:55:01 -0700 (PDT) Sender: Doug Cutting <qcarrillo@example.net> Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 11:54:59 -0700 From: Doug Cutting <qcarrillo@example.net> User-Agent: Thunderbird 83.161.120.155 (X11/20090608) MIME-Version: 1.0 To: qcarrillo@example.net Subject: Re: jira notifications on common, hdfs, and mapreduce References: <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Owen O'Malley wrote: > create/resolved/reopen events are sent to {common,mapreduce,hdfs}-dev > all jira events are sent to {common,mapreduce,hdfs}-issues I'd like to remove create/resolved/reopen from the -issues lists, so that folks who subscribe to both lists do not see such events twice. This would change the policy to: - create/resolved/reopen events are sent to {common,mapreduce,hdfs}-dev - all *other* jira events are sent to {common,mapreduce,hdfs}-issues Objections? Doug From generalqcarrillo@example.net Wed Jul 01 19:04:44 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 7204 invoked from network); 1 Jul 2009 19:04:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 19:04:44 -0000 Received: (qmail 58690 invoked by uid 500); 1 Jul 2009 19:04:54 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 58596 invoked by uid 500); 1 Jul 2009 19:04:54 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 58586 invoked by uid 99); 1 Jul 2009 19:04:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 19:04:54 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO mrout1-b.corp.re1.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 19:04:43 +0000 Received: from walkduty-lm.corp.yahoo.com (walkduty-lm.corp.yahoo.com [83.161.120.155]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id n61J2v1X043326 for <qcarrillo@example.net>; Wed, 1 Jul 2009 12:02:57 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:from:to:in-reply-to:content-type: content-transfer-encoding:mime-version:subject:date:references:x-mailer; b=sn26EECsmqa2fp3R+JI3M446SEONasm8zJAL6GAdrpLFcN6rFacRinz0qk68KQkn Message-Id: <qcarrillo@example.net> From: Arun C Murthy <qcarrillo@example.net> To: qcarrillo@example.net In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: jira notifications on common, hdfs, and mapreduce Date: Wed, 1 Jul 2009 12:02:57 -0700 References: <qcarrillo@example.net> <qcarrillo@example.net> X-Mailer: Apple Mail (2.935.3) X-Virus-Checked: Checked by ClamAV on apache.org On Jul 1, 2009, at 11:54 AM, Doug Cutting wrote: > Owen O'Malley wrote: >> create/resolved/reopen events are sent to {common,mapreduce,hdfs}-dev >> all jira events are sent to {common,mapreduce,hdfs}-issues > > I'd like to remove create/resolved/reopen from the -issues lists, so > that folks who subscribe to both lists do not see such events twice. > This would change the policy to: > > - create/resolved/reopen events are sent to {common,mapreduce,hdfs}- > dev > - all *other* jira events are sent to {common,mapreduce,hdfs}-issues > > Objections? > -1 from me. The create/resolve/reopen traffic is very minor compared to the comments. I'd prefer to have the whole thread in one place (*-issues) rather than fiddle with multiple mailboxes. *smile* Arun From generalqcarrillo@example.net Wed Jul 01 19:07:12 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 8279 invoked from network); 1 Jul 2009 19:07:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 19:07:12 -0000 Received: (qmail 62915 invoked by uid 500); 1 Jul 2009 19:07:22 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 62845 invoked by uid 500); 1 Jul 2009 19:07:22 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 62835 invoked by uid 99); 1 Jul 2009 19:07:22 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 19:07:22 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO web56205.mail.re3.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Wed, 01 Jul 2009 19:07:13 +0000 Received: (qmail 39068 invoked by uid 60001); 1 Jul 2009 19:06:52 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1246475212; bh=54x5iP1gpscCkuej+eMtBXvl/scpGMmvosCbTuVGdF8=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=SX7PaFcOFrmb47cgS5IzLN03PNWX+2P/isVrSvTtESjPLd8TO7jNKtK3hxugq2WIuGcIFIRq+89dAH/egaH0l03w6taLcbxXOGXlaXgKQ3fiHKc92BVbYI30ucdLSQ9oQxTvgjInb+FpwyecScxEG9wc3iAAtCcNPx3fUcCuFXk= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:References:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=sEIurb0PHeJfJ0QGoEBM1JpYgCRCKvKrKOBVmDLs/0PNFMURT0JDmQFCXslXK2KmRSmRXinqj7V8Cm5W3k2JyZwQNgdszrFl3qDPRWUX3SozQu/FiSenkmB5nJ/wow4RPshFfUrp/I8u1Nb1/zgB7cyIhGim91C9/KuiEgzUJqI=; Message-ID: <{{EMAIL+PHONE}}> X-YMail-OSG: 4bGNIRUVM1nbHtVNLCB8XTzd0DSbOF9GqzIEuxuofgttMRrtY5b_Oylid.77Daop4Lpu2KqTVyGDiaSnD.OQk0pAw4la4_iuQNcnLCHnrFKarKgJz.yIBjP5rU.I0C2cMnDESRDFNsJwE21JLI_0DFZhkvlRmH.KG60HybxukcqgOy7hKFjKPU286Eth0BmucukkEIqrnBx9kkQwb8tuMoi5_W_hyuVe0RQXaAx_9xQ_8leOgGDWTQ8Ly6IOZ2B7aBb2XbiOW_dTTLb3CZZ0fsf8k44PgY7MFpDsq0uEH6NEET2SVXUYiS6v1dkkDGBFmlByamDry14klbkr28_bbCbTKbbEOIXbxVprL8Xz Received: from [83.161.120.155] by web56205.mail.re3.yahoo.com via HTTP; Wed, 01 Jul 2009 12:06:51 PDT X-Mailer: YahooMailRC/1357.22 YahooMailWebService/0.7.289.15 References: <qcarrillo@example.net> <qcarrillo@example.net> Date: Wed, 1 Jul 2009 12:06:51 -0700 (PDT) From: "Tsz Wo \(Nicholas\), Sze" <qcarrillo@example.net> Subject: Re: jira notifications on common, hdfs, and mapreduce To: qcarrillo@example.net In-Reply-To: <qcarrillo@example.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked by ClamAV on apache.org +1 on Doug's suggestion. I am getting > 100 emails everyday. I map the emails to different accounts. It is good to reduce it. Otherwise, I probably need to put them on hdfs. :) Nicholas Sze ----- Original Message ---- > From: Doug Cutting <qcarrillo@example.net> > To: qcarrillo@example.net > Sent: Wednesday, July 1, 2009 11:54:59 AM > Subject: Re: jira notifications on common, hdfs, and mapreduce > > Owen O'Malley wrote: > > create/resolved/reopen events are sent to {common,mapreduce,hdfs}-dev > > all jira events are sent to {common,mapreduce,hdfs}-issues > > I'd like to remove create/resolved/reopen from the -issues lists, so that folks > who subscribe to both lists do not see such events twice. This would change the > policy to: > > - create/resolved/reopen events are sent to {common,mapreduce,hdfs}-dev > - all *other* jira events are sent to {common,mapreduce,hdfs}-issues > > Objections? > > Doug From generalqcarrillo@example.net Wed Jul 01 19:22:51 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 20418 invoked from network); 1 Jul 2009 19:22:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 19:22:51 -0000 Received: (qmail 89220 invoked by uid 500); 1 Jul 2009 19:23:01 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 89159 invoked by uid 500); 1 Jul 2009 19:23:01 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 89149 invoked by uid 99); 1 Jul 2009 19:23:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 19:23:01 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-pz0-f196.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 19:22:51 +0000 Received: by pzk34 with SMTP id 34so1004972pzk.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 12:22:30 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=QFUpPJKMHDXrgQAU5QUYanr0IPGfZMXduc+L+dctW7s=; b=hAb9892AwT5J1Z4v0Xt9r8wRsn90TTn5/ahd/jSbdks4qmchQkYVErLZMJwvkI2Yx4 H5bfn2+7pSXLECuc/vsjaKTcvemp1XjN3OUYjhELWk/ao3g0hYB8NsqN6vSduWdIv+yJ BvO+Qy1wgIAzRWrd9IWsoFjsK0XrsnyP0X6e4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Vmao7nE4dml6FyyjbWgmRbZQCa5lZLEhIf5x3x4BBd5R5Mt9reL0KXDP8HDLgl4/tV zlAxSyNnsh8nBKPo70thPyq2eEUJvi8Z2BrezrzhG+ZggqIiVv0h0OlmaIfVTxl26jCA 6yshi92gaFgISDfFEPsZFkEfXSpQ9U+p9RHEg= Received: by 83.161.120.155 with SMTP id c12mr1301132wfb.286.1246476148717; Wed, 01 Jul 2009 12:22:28 -0700 (PDT) Received: from ?83.161.120.155? (c-76-103-176-123.hsd1.ca.comcast.net [83.161.120.155]) by mx.google.com with ESMTPS id 24sm4643795wff.38.283.161.120.155.22.27 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 01 Jul 2009 12:22:28 -0700 (PDT) Sender: Doug Cutting <qcarrillo@example.net> Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 12:22:25 -0700 From: Doug Cutting <qcarrillo@example.net> User-Agent: Thunderbird 83.161.120.155 (X11/20090608) MIME-Version: 1.0 To: qcarrillo@example.net Subject: Re: jira notifications on common, hdfs, and mapreduce References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Arun C Murthy wrote: > -1 from me. > The create/resolve/reopen traffic is very minor compared to the > comments. I'd prefer to have the whole thread in one place (*-issues) > rather than fiddle with multiple mailboxes. *smile* I assume you mean "thread" loosely, since all messages related to an issue are not threaded together by any mail reader that I know of, since Jira changes the subject and does not set a "References" or "In-Reply-To" header. You subscribe to both lists and really prefer receiving create/resolve messages twice? I subscribe to both, and have a filter that marks-as-read messages sent to -issues, so I have the full set of messages available to searches, but only am notified about new and watched issues. Doug From generalqcarrillo@example.net Wed Jul 01 20:06:45 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 35883 invoked from network); 1 Jul 2009 20:06:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 20:06:45 -0000 Received: (qmail 73152 invoked by uid 500); 1 Jul 2009 20:06:55 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 73072 invoked by uid 500); 1 Jul 2009 20:06:55 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 73062 invoked by uid 99); 1 Jul 2009 20:06:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 20:06:55 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO mrout2.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 20:06:44 +0000 Received: from [83.161.120.155] (goodenter-lm.corp.yahoo.com [83.161.120.155]) by mrout2.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id n61K62Jd073418 for <qcarrillo@example.net>; Wed, 1 Jul 2009 13:06:02 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:content-type:content-transfer-encoding; b=2CcdXRseXKyTxPW/ZnpWSn7FxxB5t7yH8oOmkltLllK9gyXe4R/5543G+MA6AX41 Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 13:06:02 -0700 From: Konstantin Boudnik <qcarrillo@example.net> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: "qcarrillo@example.net" <qcarrillo@example.net> Subject: Re: jira notifications on common, hdfs, and mapreduce References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org On 7/1/09 12:22 PM, Doug Cutting wrote: > Arun C Murthy wrote: >> -1 from me. >> The create/resolve/reopen traffic is very minor compared to the >> comments. I'd prefer to have the whole thread in one place (*-issues) >> rather than fiddle with multiple mailboxes. *smile* > > I assume you mean "thread" loosely, since all messages related to an > issue are not threaded together by any mail reader that I know of, since > Jira changes the subject and does not set a "References" or > "In-Reply-To" header. Actually, Thunderbird and Mutt are at least two which does thread JIRA's threads properly. The way they do so is exactly by using Message-ID and In-Reply-To fields of a RFC-822 header. Cos > You subscribe to both lists and really prefer receiving create/resolve > messages twice? > > I subscribe to both, and have a filter that marks-as-read messages sent > to -issues, so I have the full set of messages available to searches, > but only am notified about new and watched issues. > > Doug From generalqcarrillo@example.net Wed Jul 01 20:29:25 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 41930 invoked from network); 1 Jul 2009 20:29:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 20:29:23 -0000 Received: (qmail 9480 invoked by uid 500); 1 Jul 2009 20:29:33 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 9402 invoked by uid 500); 1 Jul 2009 20:29:33 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 9392 invoked by uid 99); 1 Jul 2009 20:29:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 20:29:33 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wf-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 20:29:23 +0000 Received: by wf-out-1314.google.com with SMTP id 23so433761wfg.2 for <qcarrillo@example.net>; Wed, 01 Jul 2009 13:29:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:sender:message-id:date:from :user-agent:mime-version:to:subject:references:in-reply-to :content-type:content-transfer-encoding; bh=QiO5E9NlYw/D9pmxZPj3ynYSAnXyDMLMOf2w2Sfx3tw=; b=VbANDl3g4hUs3iAdXOo9cbtrp9yEVfMugO31nABKewGSWpVaRvi1Yx4gd90ldIUANu ayJF8rr9zZ/qR78WnwamtLxNv2b/fNX8nJ7Y1RL7Sl6EjIZns8SgUO5m4Ul8qlSyD3M2 HtrVwfUjAHm15Fj+RIb0aatkJ/cxJM00q7VYE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=sender:message-id:date:from:user-agent:mime-version:to:subject :references:in-reply-to:content-type:content-transfer-encoding; b=Z6zgL6WsuFyOUHMswHDVAO7f4s/7h5BEAqKRYPA3POQyvkYBe/8uwbCcUqTcAJZfxR BjubEzXmhEQ9FSps/pixFxsP2oGCEWwauu4ILL8oS+u20tt374WURD8WjsCdzGSIEmvO 3RZZ50pBjRbg3/RYAT07mxmPGcMcE7B5TxK7A= Received: by 83.161.120.155 with SMTP id x12mr1301253wfb.206.1246480143614; Wed, 01 Jul 2009 13:29:03 -0700 (PDT) Received: from ?83.161.120.155? (c-76-103-176-123.hsd1.ca.comcast.net [83.161.120.155]) by mx.google.com with ESMTPS id 28sm4794241wfd.24.283.161.120.155.29.02 (version=TLSv1/SSLv3 cipher=RC4-MD5); Wed, 01 Jul 2009 13:29:02 -0700 (PDT) Sender: Doug Cutting <qcarrillo@example.net> Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 13:29:00 -0700 From: Doug Cutting <qcarrillo@example.net> User-Agent: Thunderbird 83.161.120.155 (X11/20090608) MIME-Version: 1.0 To: qcarrillo@example.net Subject: Re: jira notifications on common, hdfs, and mapreduce References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Konstantin Boudnik wrote: > Actually, Thunderbird and Mutt are at least two which does thread JIRA's > threads properly. > > The way they do so is exactly by using Message-ID and In-Reply-To fields > of a RFC-822 header. The Message-ID is different for each message, and is thus alone not useful for threading. I don't see an In-Reply-To header in Jira-sent messages, nor a References header. These are the preferred means for threading according to RFC2822, although some readers thread by subject too. Thus all comments relative to an issue may be threaded, but not together with other updates, like assignment, attachment, etc., since these use different subjects. For example, do you see these headers in http://tinyurl.com/lw3cse? Doug From generalqcarrillo@example.net Wed Jul 01 20:42:22 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 45416 invoked from network); 1 Jul 2009 20:42:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Jul 2009 20:42:22 -0000 Received: (qmail 33274 invoked by uid 500); 1 Jul 2009 20:42:32 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 33196 invoked by uid 500); 1 Jul 2009 20:42:32 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 33186 invoked by uid 99); 1 Jul 2009 20:42:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 20:42:32 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mrout1-b.corp.re1.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2009 20:42:20 +0000 Received: from [83.161.120.155] (goodenter-lm.corp.yahoo.com [83.161.120.155]) by mrout1-b.corp.re1.yahoo.com (8.13.8/8.13.8/y.out) with ESMTP id n61KeUt6080347 for <qcarrillo@example.net>; Wed, 1 Jul 2009 13:40:31 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:content-type:content-transfer-encoding; b=HmtoJJx1QCWabN2n2HgMhvlmjT/lJxtGBSSKj3zdCAyaI3YnuVrinlXow127F6FF Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 13:40:30 -0700 From: Konstantin Boudnik <qcarrillo@example.net> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: "qcarrillo@example.net" <qcarrillo@example.net> Subject: Re: jira notifications on common, hdfs, and mapreduce References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Doug, Message-ID is unique. However, what I can see in my mail is that all subsequent emails (after JIRA created message) have its Message-ID in their In-Reply-To field. Say, Subject: [jira] Created: (HADOOP-6110) test-patch takes 45min! Thread-Topic: [jira] Created: (HADOOP-6110) test-patch takes 45min! Thread-Index: Acn2Jd4/MZg/3jVETQKT5ZEGzVtNCA== Message-ID: <1892144747.1245997027374.JavaMail.jira@brutus> List-Help: <mailto:qcarrillo@example.net> and Subject: [jira] Updated: (HADOOP-6110) test-patch takes 45min! Thread-Topic: [jira] Updated: (HADOOP-6110) test-patch takes 45min! Thread-Index: Acn4rGYcaU6FaceJSyGggrQ+1INmpg== Message-ID: <1159605925.1246274687243.JavaMail.jira@brutus> List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> In-Reply-To: <1892144747.1245997027374.JavaMail.jira@brutus> I don't see In-Reply-To field in the example you've sent to me. Is it because some tags are being stripped out by mail archiving software? Cos On 7/1/09 1:29 PM, Doug Cutting wrote: > Konstantin Boudnik wrote: >> Actually, Thunderbird and Mutt are at least two which does thread JIRA's >> threads properly. >> >> The way they do so is exactly by using Message-ID and In-Reply-To fields >> of a RFC-822 header. > > The Message-ID is different for each message, and is thus alone not > useful for threading. I don't see an In-Reply-To header in Jira-sent > messages, nor a References header. These are the preferred means for > threading according to RFC2822, although some readers thread by subject > too. Thus all comments relative to an issue may be threaded, but not > together with other updates, like assignment, attachment, etc., since > these use different subjects. > > For example, do you see these headers in http://tinyurl.com/lw3cse? > > Doug > > > > From generalqcarrillo@example.net Thu Jul 02 02:03:06 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 388 invoked from network); 2 Jul 2009 02:03:06 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Jul 2009 02:03:06 -0000 Received: (qmail 50108 invoked by uid 500); 2 Jul 2009 02:03:16 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 50042 invoked by uid 500); 2 Jul 2009 02:03:16 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 50032 invoked by uid 99); 2 Jul 2009 02:03:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 02:03:16 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-pz0-f196.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 02:03:08 +0000 Received: by pzk34 with SMTP id 34so1170453pzk.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 19:02:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type:content-transfer-encoding; bh=P6TBPMqnhTn/sAqf+CY8Q3FK/u1z7j3/O+iCs+6+UH0=; b=U7JogvrbUIWVeBNqKr1JCrZi7jZWuRTqqnfO++PGPo1ZgahBTZShtHuLnZgu78x76T YzNt8QFOc29J3lGrfacmoFgrNGUpXbY68yQA+VzJrLqvajCaPUlzoCc9463xpyJRivAo UJVUH4zG2ZJdK9+ioeQkcvaiyxIEUFyo+jQQM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type :content-transfer-encoding; b=rxOerbsz+xz2A+X1sKWbrNZjFhgFzwQiNUEbHOpbWUL+BsqHz/9zllynkshPhH9qsy im7d1hljgW5XqLkRtOoYKOXs9UswYrrNtrelSHy1hI+qniXV7ANnn8vVAQ/L89ACAttR dd5zyH4Bk+wXwf06kKjzUL5tXVC/GhSL4vZaM= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id t20mr1285708wfh.181.1246500167886; Wed, 01 Jul 2009 19:02:47 -0700 (PDT) Date: Thu, 2 Jul 2009 11:02:47 +0900 Message-ID: <qcarrillo@example.net> Subject: Mailing lists are broken? From: "Bogdan M. Maryniuk" <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hello. Tried http://hadoop.apache.org/core/mailing_lists.html Address "qcarrillo@example.net" returns error. Is that's OK? -- Kind regards, BM Things, that are stupid at the beginning, rarely ends up wisely. From generalqcarrillo@example.net Thu Jul 02 05:11:31 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 64200 invoked from network); 2 Jul 2009 05:11:31 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Jul 2009 05:11:31 -0000 Received: (qmail 78770 invoked by uid 500); 2 Jul 2009 05:11:40 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 78547 invoked by uid 500); 2 Jul 2009 05:11:39 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 78537 invoked by uid 99); 2 Jul 2009 05:11:39 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 05:11:39 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-vw0-f172.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 05:11:29 +0000 Received: by vwj2 with SMTP id 2so839381vwj.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 22:11:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=8PQ12GXd1XJ6wG/RFgmMpHmwwt36qZBqBqMmRKuw/5g=; b=szEuS7QQ78msdNBSlZSaTm2uoO8AKu/EogeD74deGQJKd1cJQo2ljPS0NKkAbYYeTi wgDrZlU9tbi/A9ShsRLjjv3YzuzENm61HLqRUxVgMID4RwTEn5MQD6ZM6tphmot3jM/j /dhOv31bHpw6FnKiaPsKg1t36hTLuEHb5rgF0= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=eOHYtAJcrJADb4m1oBb5ov4WL1aIPEDngPa2PxWOi7GglOg4mvACfnpxcLej1Xc7Wp 48+bpzeXivc96TJpEn5S80996B/RlabD5ybJSfXb7IhltM0uSfQosSmlDIzk3iMHeKj6 kQMZQzJbNDrQoemyOV2ggdFuKWW2F0gCnKXWQ= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id l15mr8333999vcj.4.1246511468614; Wed, 01 Jul 2009 22:11:08 -0700 (PDT) In-Reply-To: <qcarrillo@example.net> References: <qcarrillo@example.net> <qcarrillo@example.net> Date: Thu, 2 Jul 2009 13:11:08 +0800 Message-ID: <qcarrillo@example.net> Subject: Re: fail to setup passphraseless ssh and need some help From: fred wang <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: multipart/alternative; boundary=0016e64755aa4b95e1046db2118b X-Virus-Checked: Checked by ClamAV on apache.org --0016e64755aa4b95e1046db2118b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I have setup ./.ssh/authorized keys has permssion 600, but it didn't work. Thanks anyway ls -l .ssh/authorized_keys -rw------- 1 xxx xxx 1222 2009-07-02 13:08 .ssh/authorized_keys On Thu, Jul 2, 2009 at 12:15 AM, Konstantin Boudnik <qcarrillo@example.net>wrote: > Make sure that your ~/.ssh/authorized_keys has permissions 600 > > Cos > > > On 7/1/09 7:35 AM, fred wang wrote: > >> Hi all, >> >> I failed to setup passphraseless ssh(I mean, I still need to input >> password to do ssh localhost) when I tried to configure Hadoop to run on >> psuedo-distributed operation, could anyone help me solve this issue? >> Thanks! >> >> (1)I use the Putty0.6 to remote access to Ubuntu by SSH. >> >> (2) execution steps and ouput >> >> $ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa >> Generating public/private dsa key pair. >> Your identification has been saved in /home/xxx/.ssh/id_dsa. >> Your public key has been saved in /home/xxx/.ssh/id_dsa.pub. >> The key fingerprint is: >> 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 xxx >> >> >> **note: it doesn't have message 'Enter passphrase (empty for no >> passphrase): >> Enter same passphrase again: ' which appear in some introductory >> paper. >> " >> >> $ cat ~/.ssh/id_dsa.pub>> ~/.ssh/authorized_keys >> no output >> >> $ ssh localhost >> The authenticity of host 'localhost (83.161.120.155)' can't be established. >> RSA key fingerprint is 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4. >> Are you sure you want to continue connecting (yes/no)? yes >> Warning: Permanently added 'localhost' (RSA) to the list of known hosts. >> xxx@localhost's password: >> > --0016e64755aa4b95e1046db2118b-- From generalqcarrillo@example.net Thu Jul 02 05:18:44 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 66751 invoked from network); 2 Jul 2009 05:18:44 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Jul 2009 05:18:44 -0000 Received: (qmail 84565 invoked by uid 500); 2 Jul 2009 05:18:54 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 84495 invoked by uid 500); 2 Jul 2009 05:18:54 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 84485 invoked by uid 99); 2 Jul 2009 05:18:54 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 05:18:54 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO mrout2.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 05:18:43 +0000 Received: from [83.161.120.155] (snvvpn1-10-73-152-c179.hq.corp.yahoo.com [83.161.120.155]) by mrout2.yahoo.com (8.13.6/8.13.6/y.out) with ESMTP id n625I833078548 for <qcarrillo@example.net>; Wed, 1 Jul 2009 22:18:08 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; s=serpent; d=yahoo-inc.com; c=nofws; q=dns; h=message-id:date:from:user-agent:mime-version:to:subject: references:in-reply-to:content-type:content-transfer-encoding; b=mnbWGIubH/4ldClQmm+yCwFk+jD6mHH4Ubl1uD/w0YFp6cJQRwlx8NkJJ0CqYDWA Message-ID: <qcarrillo@example.net> Date: Wed, 01 Jul 2009 22:18:07 -0700 From: Konstantin Boudnik <qcarrillo@example.net> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090223 Thunderbird/3.0b2 MIME-Version: 1.0 To: "qcarrillo@example.net" <qcarrillo@example.net> Subject: Re: fail to setup passphraseless ssh and need some help References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> In-Reply-To: <qcarrillo@example.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Yet another possibility is that your SSH daemon isn't configured to accept publickey as a valid authorization mean. Try to do ssh -v localhost and check if there's something similar to the following: debug1: Authentications that can continue: publickey,password,keyboard-interactive debug1: Next authentication method: publickey debug1: Trying private key: /home/xxx/.ssh/identity debug1: Trying private key: /home/xxx/.ssh/id_rsa debug1: Offering public key: /home/xxx/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 435 debug1: read PEM private key done: type DSA debug1: Authentication succeeded (publickey). Cos On 7/1/09 10:11 PM, fred wang wrote: > I have setup ./.ssh/authorized keys has permssion 600, but it didn't work. > Thanks anyway > > ls -l .ssh/authorized_keys > -rw------- 1 xxx xxx 1222 2009-07-02 13:08 .ssh/authorized_keys > > On Thu, Jul 2, 2009 at 12:15 AM, Konstantin Boudnik<qcarrillo@example.net>wrote: > >> Make sure that your ~/.ssh/authorized_keys has permissions 600 >> >> Cos >> >> >> On 7/1/09 7:35 AM, fred wang wrote: >> >>> Hi all, >>> >>> I failed to setup passphraseless ssh(I mean, I still need to input >>> password to do ssh localhost) when I tried to configure Hadoop to run on >>> psuedo-distributed operation, could anyone help me solve this issue? >>> Thanks! >>> >>> (1)I use the Putty0.6 to remote access to Ubuntu by SSH. >>> >>> (2) execution steps and ouput >>> >>> $ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa >>> Generating public/private dsa key pair. >>> Your identification has been saved in /home/xxx/.ssh/id_dsa. >>> Your public key has been saved in /home/xxx/.ssh/id_dsa.pub. >>> The key fingerprint is: >>> 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 xxx >>> >>> >>> **note: it doesn't have message 'Enter passphrase (empty for no >>> passphrase): >>> Enter same passphrase again: ' which appear in some introductory >>> paper. >>> " >>> >>> $ cat ~/.ssh/id_dsa.pub>> ~/.ssh/authorized_keys >>> no output >>> >>> $ ssh localhost >>> The authenticity of host 'localhost (83.161.120.155)' can't be established. >>> RSA key fingerprint is 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4. >>> Are you sure you want to continue connecting (yes/no)? yes >>> Warning: Permanently added 'localhost' (RSA) to the list of known hosts. >>> xxx@localhost's password: >>> From generalqcarrillo@example.net Thu Jul 02 05:51:41 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 87290 invoked from network); 2 Jul 2009 05:51:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Jul 2009 05:51:40 -0000 Received: (qmail 24541 invoked by uid 500); 2 Jul 2009 05:51:51 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 24460 invoked by uid 500); 2 Jul 2009 05:51:50 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 24450 invoked by uid 99); 2 Jul 2009 05:51:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 05:51:50 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-vw0-f172.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 05:51:39 +0000 Received: by vwj2 with SMTP id 2so849797vwj.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 22:51:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=gIYFVxl742VOZs6j1CjQxzM1PMiRvoOnSDlGhjCbpsg=; b=iuF7MQ5R3SkvO4HkPBPzmQHt14+JjDPoyyKfdcXL7d6N8hPO5QFOKFs3/x9Zby4BrJ cQXi0ULKVug3v0qY7tPIz6c2z8cyREP8NWjoMvnlq6MUY/rEsNwSKnAPOpYqoTTF6LqX 1dhCdcJFv83I+LSwjT++/X5HDqHWV7gFgcp6s= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=qG8fhGq8oU8tyx30hFyOZel2JCw1F0DRaB6KarF4UCCITlZrHGtEIsgA2wNuZo4dbJ oKVK0QBIQ6DeVU/NDIpolsugnlTmikaaKl+GR7UkVUdLXySL1muvx2odvl9V4xQMDoC+ xOrbW5FyWksQI5fueqnwJdO2HEUaVl+u7vdOo= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id f6mr10710972vcj.16.1246513878067; Wed, 01 Jul 2009 22:51:18 -0700 (PDT) In-Reply-To: <qcarrillo@example.net> References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> Date: Thu, 2 Jul 2009 13:51:18 +0800 Message-ID: <qcarrillo@example.net> Subject: Re: fail to setup passphraseless ssh and need some help From: fred wang <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: multipart/alternative; boundary=001485e8d216e8e9c2046db2a032 X-Virus-Checked: Checked by ClamAV on apache.org --001485e8d216e8e9c2046db2a032 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Here is the output of ssh -v localhost and the configuration of ssh_config, xxx@xxx-desktop:~$ ssh -v localhost OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to localhost [83.161.120.155] port 22. debug1: Connection established. debug1: identity file /home/xxx/.ssh/identity type -1 debug1: identity file /home/xxx/.ssh/id_rsa type -1 debug1: identity file /home/xxx/.ssh/id_dsa type 2 debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 Debian-8ubuntu1.2 debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host 'localhost' is known and matches the RSA host key. debug1: Found key in /home/xxx/.ssh/known_hosts:1 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Trying private key: /home/xxx/.ssh/identity debug1: Trying private key: /home/xxx/.ssh/id_rsa debug1: Offering public key: /home/xxx/.ssh/id_dsa debug1: Authentications that can continue: publickey,password debug1: Next authentication method: password xxx@localhost's password: xxx@xxx:~$ vi /etc/ssh/sshd_config #KerberosOrLocalPasswd yes #KerberosTicketCleanup yes # GSSAPI options #GSSAPIAuthentication no #GSSAPICleanupCredentials yes X11Forwarding yes X11DisplayOffset 10 PrintMotd no PrintLastLog yes TCPKeepAlive yes #UseLogin no #MaxStartups 10:30:60 #Banner /etc/issue.net # Allow client to pass locale environment variables AcceptEnv LANG LC_* Subsystem sftp /usr/lib/openssh/sftp-server UsePAM yes On Thu, Jul 2, 2009 at 1:18 PM, Konstantin Boudnik <qcarrillo@example.net>wrote: > Yet another possibility is that your SSH daemon isn't configured to accept > publickey as a valid authorization mean. > > Try to do ssh -v localhost and check if there's something similar to the > following: > > debug1: Authentications that can continue: > publickey,password,keyboard-interactive > debug1: Next authentication method: publickey > debug1: Trying private key: /home/xxx/.ssh/identity > debug1: Trying private key: /home/xxx/.ssh/id_rsa > debug1: Offering public key: /home/xxx/.ssh/id_dsa > debug1: Server accepts key: pkalg ssh-dss blen 435 > debug1: read PEM private key done: type DSA > debug1: Authentication succeeded (publickey). > > Cos > > > On 7/1/09 10:11 PM, fred wang wrote: > >> I have setup ./.ssh/authorized keys has permssion 600, but it didn't work. >> Thanks anyway >> >> ls -l .ssh/authorized_keys >> -rw------- 1 xxx xxx 1222 2009-07-02 13:08 .ssh/authorized_keys >> >> On Thu, Jul 2, 2009 at 12:15 AM, Konstantin Boudnik<qcarrillo@example.net >> >wrote: >> >> Make sure that your ~/.ssh/authorized_keys has permissions 600 >>> >>> Cos >>> >>> >>> On 7/1/09 7:35 AM, fred wang wrote: >>> >>> Hi all, >>>> >>>> I failed to setup passphraseless ssh(I mean, I still need to input >>>> password to do ssh localhost) when I tried to configure Hadoop to run on >>>> psuedo-distributed operation, could anyone help me solve this issue? >>>> Thanks! >>>> >>>> (1)I use the Putty0.6 to remote access to Ubuntu by SSH. >>>> >>>> (2) execution steps and ouput >>>> >>>> $ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa >>>> Generating public/private dsa key pair. >>>> Your identification has been saved in /home/xxx/.ssh/id_dsa. >>>> Your public key has been saved in /home/xxx/.ssh/id_dsa.pub. >>>> The key fingerprint is: >>>> 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 xxx >>>> >>>> >>>> **note: it doesn't have message 'Enter passphrase (empty for no >>>> passphrase): >>>> Enter same passphrase again: ' which appear in some introductory >>>> paper. >>>> " >>>> >>>> $ cat ~/.ssh/id_dsa.pub>> ~/.ssh/authorized_keys >>>> no output >>>> >>>> $ ssh localhost >>>> The authenticity of host 'localhost (83.161.120.155)' can't be established. >>>> RSA key fingerprint is 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4. >>>> Are you sure you want to continue connecting (yes/no)? yes >>>> Warning: Permanently added 'localhost' (RSA) to the list of known hosts. >>>> xxx@localhost's password: >>>> >>>> --001485e8d216e8e9c2046db2a032-- From generalqcarrillo@example.net Thu Jul 02 06:09:59 2009 Return-Path: <generalqcarrillo@example.net> Delivered-To: qcarrillo@example.net Received: (qmail 98107 invoked from network); 2 Jul 2009 06:09:58 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 2 Jul 2009 06:09:58 -0000 Received: (qmail 36396 invoked by uid 500); 2 Jul 2009 06:10:08 -0000 Delivered-To: qcarrillo@example.net Received: (qmail 36314 invoked by uid 500); 2 Jul 2009 06:10:08 -0000 Mailing-List: contact qcarrillo@example.net; run by ezmlm Precedence: bulk List-Help: <mailto:qcarrillo@example.net> List-Unsubscribe: <mailto:qcarrillo@example.net> List-Post: <mailto:qcarrillo@example.net> List-Id: <general.hadoop.apache.org> Reply-To: qcarrillo@example.net Delivered-To: mailing list qcarrillo@example.net Received: (qmail 36304 invoked by uid 99); 2 Jul 2009 06:10:08 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 06:10:08 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of qcarrillo@example.net designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-vw0-f172.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 02 Jul 2009 06:09:58 +0000 Received: by vwj2 with SMTP id 2so854680vwj.5 for <qcarrillo@example.net>; Wed, 01 Jul 2009 23:09:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=aJterOkRMMmKPRay8bi65WyiOhbEjd4dz2nNl3583XA=; b=x0hEiDcygINbH+KYuzKCCdPbxsBrNLQz7aRz25Z/aa5BA0C5uOHdkg6/i4q3PXhHzz /TPJOXHZBegss5RR4G9Kd2qe07qSuXzB0gG47zjPq22wjVut+sGk1DEwPNHbdS3R6C9l 6MLKmvoVcdNBEFmU3ygJVbH0su+FrXPaDIN9M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=CSovY1BHB3A+U8xwd8XsM0HHaPkI46wPysL40nwRpf4mfhjOc52+nRE1AhrkiGIP/t m9rLaHmOY5Jq8Hczt68dlq0qD64gx5yCyz85YiOdYmNHesS7R3Djkhi9UDfAZw8R3By1 tb98mADQk7UG9+Dcu3h/nuvKKDUpeBZOqn3pk= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id l15mr8439952vcj.4.1246514977022; Wed, 01 Jul 2009 23:09:37 -0700 (PDT) In-Reply-To: <qcarrillo@example.net> References: <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> <qcarrillo@example.net> Date: Thu, 2 Jul 2009 14:09:36 +0800 Message-ID: <qcarrillo@example.net> Subject: Re: fail to setup passphraseless ssh and need some help From: fred wang <qcarrillo@example.net> To: qcarrillo@example.net Content-Type: multipart/alternative; boundary=0016e64755aa69abfd046db2e2bd X-Virus-Checked: Checked by ClamAV on apache.org --0016e64755aa69abfd046db2e2bd Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit sorry, should incopy ssh_config(instead of sshd_config) vi /etc/ssh/ssh_config # 1. command line options # 2. user-specific file # 3. system-wide file # Any configuration value is only changed the first time it is set. # Thus, host-specific definitions should be at the beginning of the # configuration file, and defaults at the end. # Site-wide defaults for some commonly used options. For a comprehensive # list of available options, their meanings and defaults, please see the # ssh_config(5) man page. Host * # ForwardAgent no # ForwardX11 no # ForwardX11Trusted yes # RhostsRSAAuthentication no # RSAAuthentication yes # PasswordAuthentication yes # HostbasedAuthentication no # GSSAPIAuthentication no # GSSAPIDelegateCredentials no # GSSAPIKeyExchange no # GSSAPITrustDNS no # BatchMode no # CheckHostIP yes # AddressFamily any # ConnectTimeout 0 # StrictHostKeyChecking ask # IdentityFile ~/.ssh/identity # IdentityFile ~/.ssh/id_rsa # IdentityFile ~/.ssh/id_dsa # Port 22 # Protocol 2,1 # Cipher 3des # Ciphers aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,arcfour,aes192-cbc,aes256-cbc # MACs hmac-md5,hmac-sha1,qcarrillo@example.net,hmac-ripemd160 # EscapeChar ~ # Tunnel no # TunnelDevice any:any # PermitLocalCommand no SendEnv LANG LC_* HashKnownHosts yes GSSAPIAuthentication yes GSSAPIDelegateCredentials no On Thu, Jul 2, 2009 at 1:51 PM, fred wang <qcarrillo@example.net> wrote: > Here is the output of ssh -v localhost and the configuration of > ssh_config, > > xxx@xxx-desktop:~$ ssh -v localhost > > OpenSSH_4.7p1 Debian-8ubuntu1.2, OpenSSL 0.9.8g 19 Oct 2007 > > debug1: Reading configuration data /etc/ssh/ssh_config > > debug1: Applying options for * > > debug1: Connecting to localhost [83.161.120.155] port 22. > > debug1: Connection established. > > debug1: identity file /home/xxx/.ssh/identity type -1 > > debug1: identity file /home/xxx/.ssh/id_rsa type -1 > > debug1: identity file /home/xxx/.ssh/id_dsa type 2 > > debug1: Remote protocol version 2.0, remote software version OpenSSH_4.7p1 > Debian-8ubuntu1.2 > > debug1: match: OpenSSH_4.7p1 Debian-8ubuntu1.2 pat OpenSSH* > > debug1: Enabling compatibility mode for protocol 2.0 > > debug1: Local version string SSH-2.0-OpenSSH_4.7p1 Debian-8ubuntu1.2 > > debug1: SSH2_MSG_KEXINIT sent > > debug1: SSH2_MSG_KEXINIT received > > debug1: kex: server->client aes128-cbc hmac-md5 none > > debug1: kex: client->server aes128-cbc hmac-md5 none > > debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent > > debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP > > debug1: SSH2_MSG_KEX_DH_GEX_INIT sent > > debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY > > debug1: Host 'localhost' is known and matches the RSA host key. > > debug1: Found key in /home/xxx/.ssh/known_hosts:1 > > debug1: ssh_rsa_verify: signature correct > > debug1: SSH2_MSG_NEWKEYS sent > > debug1: expecting SSH2_MSG_NEWKEYS > > debug1: SSH2_MSG_NEWKEYS received > > debug1: SSH2_MSG_SERVICE_REQUEST sent > > debug1: SSH2_MSG_SERVICE_ACCEPT received > > debug1: Authentications that can continue: publickey,password > > debug1: Next authentication method: publickey > > debug1: Trying private key: /home/xxx/.ssh/identity > > debug1: Trying private key: /home/xxx/.ssh/id_rsa > > debug1: Offering public key: /home/xxx/.ssh/id_dsa > > debug1: Authentications that can continue: publickey,password > > debug1: Next authentication method: password > > xxx@localhost's password: > > > > > > > > xxx@xxx:~$ vi /etc/ssh/sshd_config > > #KerberosOrLocalPasswd yes > > #KerberosTicketCleanup yes > > > > # GSSAPI options > > #GSSAPIAuthentication no > > #GSSAPICleanupCredentials yes > > > > X11Forwarding yes > > X11DisplayOffset 10 > > PrintMotd no > > PrintLastLog yes > > TCPKeepAlive yes > > #UseLogin no > > > > #MaxStartups 10:30:60 > > #Banner /etc/issue.net > > > > # Allow client to pass locale environment variables > > AcceptEnv LANG LC_* > > > > Subsystem sftp /usr/lib/openssh/sftp-server > > > > UsePAM yes > > > > On Thu, Jul 2, 2009 at 1:18 PM, Konstantin Boudnik <qcarrillo@example.net>wrote: > >> Yet another possibility is that your SSH daemon isn't configured to accept >> publickey as a valid authorization mean. >> >> Try to do ssh -v localhost and check if there's something similar to the >> following: >> >> debug1: Authentications that can continue: >> publickey,password,keyboard-interactive >> debug1: Next authentication method: publickey >> debug1: Trying private key: /home/xxx/.ssh/identity >> debug1: Trying private key: /home/xxx/.ssh/id_rsa >> debug1: Offering public key: /home/xxx/.ssh/id_dsa >> debug1: Server accepts key: pkalg ssh-dss blen 435 >> debug1: read PEM private key done: type DSA >> debug1: Authentication succeeded (publickey). >> >> Cos >> >> >> On 7/1/09 10:11 PM, fred wang wrote: >> >>> I have setup ./.ssh/authorized keys has permssion 600, but it didn't >>> work. >>> Thanks anyway >>> >>> ls -l .ssh/authorized_keys >>> -rw------- 1 xxx xxx 1222 2009-07-02 13:08 .ssh/authorized_keys >>> >>> On Thu, Jul 2, 2009 at 12:15 AM, Konstantin Boudnik<qcarrillo@example.net >>> >wrote: >>> >>> Make sure that your ~/.ssh/authorized_keys has permissions 600 >>>> >>>> Cos >>>> >>>> >>>> On 7/1/09 7:35 AM, fred wang wrote: >>>> >>>> Hi all, >>>>> >>>>> I failed to setup passphraseless ssh(I mean, I still need to input >>>>> password to do ssh localhost) when I tried to configure Hadoop to run >>>>> on >>>>> psuedo-distributed operation, could anyone help me solve this issue? >>>>> Thanks! >>>>> >>>>> (1)I use the Putty0.6 to remote access to Ubuntu by SSH. >>>>> >>>>> (2) execution steps and ouput >>>>> >>>>> $ ssh-keygen -t dsa -P '' -f ~/.ssh/id_dsa >>>>> Generating public/private dsa key pair. >>>>> Your identification has been saved in /home/xxx/.ssh/id_dsa. >>>>> Your public key has been saved in /home/xxx/.ssh/id_dsa.pub. >>>>> The key fingerprint is: >>>>> 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 xxx >>>>> >>>>> >>>>> **note: it doesn't have message 'Enter passphrase (empty for no >>>>> passphrase): >>>>> Enter same passphrase again: ' which appear in some introductory >>>>> paper. >>>>> " >>>>> >>>>> $ cat ~/.ssh/id_dsa.pub>> ~/.ssh/authorized_keys >>>>> no output >>>>> >>>>> $ ssh localhost >>>>> The authenticity of host 'localhost (83.161.120.155)' can't be established. >>>>> RSA key fingerprint is 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4:888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4. >>>>> Are you sure you want to continue connecting (yes/no)? yes >>>>> Warning: Permanently added 'localhost' (RSA) to the list
{'source': 'Apache Software Foundation Public Mail Archives'}