Return-Path: X-Original-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Delivered-To: apmail-hadoop-hdfs-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 417DD109AD for ; Mon, 12 Aug 2013 10:40:45 +0000 (UTC) Received: (qmail 56092 invoked by uid 500); 12 Aug 2013 10:40:40 -0000 Delivered-To: apmail-hadoop-hdfs-user-archive@hadoop.apache.org Received: (qmail 55751 invoked by uid 500); 12 Aug 2013 10:40:39 -0000 Mailing-List: contact user-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hadoop.apache.org Delivered-To: mailing list user@hadoop.apache.org Received: (qmail 55744 invoked by uid 99); 12 Aug 2013 10:40:39 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 10:40:39 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of wellington.chevreuil@gmail.com designates 209.85.216.43 as permitted sender) Received: from [209.85.216.43] (HELO mail-qa0-f43.google.com) (209.85.216.43) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 12 Aug 2013 10:40:34 +0000 Received: by mail-qa0-f43.google.com with SMTP id cl20so918327qab.16 for ; Mon, 12 Aug 2013 03:40:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=nWfWGpszQnQ2MDSkAGon1rG6nG4e/iHG7BGaYSwtugY=; b=gqbmDKF/hVbe9Q1PIiXyov9840E2iJlSXT5yamTp9PpZuxInMhSMT99MGx5kpOKuEQ 3ktksniumZLTjwmv9mgzIIyxXOAsgk30SyTr6W4toMro+8UprVtcP0Uy0Py6fTWGXZ3j RClRz6oabxg/An9HhntR8NdpQ8pRgqVFwhiHxMMYyvGVdSORND3AXm1V5PTZlMGWW45c fAJBigN/hkRc4zyguSbtjtDlpKqnkaxfT1TDdfUoEJLIuvbwdH8+9yWGkvhZaZJcZflh ItHKM4KEg7AWTwjXC5OXXg7tA+3UkzdhmYHgmPJ0CBLkQTqLAjgp0S5c9ijZgDGGjvGl nbuw== MIME-Version: 1.0 X-Received: by 10.224.4.2 with SMTP id 2mr24106023qap.55.1376304013412; Mon, 12 Aug 2013 03:40:13 -0700 (PDT) Received: by 10.224.208.201 with HTTP; Mon, 12 Aug 2013 03:40:13 -0700 (PDT) In-Reply-To: References: Date: Mon, 12 Aug 2013 11:40:13 +0100 Message-ID: Subject: Re: How exactly Oozie works internally? From: Wellington Chevreuil To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=047d7b604eb2d396e704e3bdbf89 X-Virus-Checked: Checked by ClamAV on apache.org --047d7b604eb2d396e704e3bdbf89 Content-Type: text/plain; charset=ISO-8859-1 I had similar issue before... I'm not sure, but I think in my case oozie was always connecting through ssh as oozie user, event if I was running it as a different user. If it's not a big effort to you, I would recommend you to try create oozie usr in your edge node and give it all required rights to perform your action. Cheers, Wellington. 2013/8/12 Kasa V Varun Tej > Hi WC, > > I'm triggering the job as root user and i want to run some command on the > edge node. > Yes i made sure of the permissions. > > Thanks, > Kasa > > > > On Mon, Aug 12, 2013 at 3:07 PM, Wellington Chevreuil < > wellington.chevreuil@gmail.com> wrote: > >> Hi Kasa, >> >> did you create the oozie user on the target ssh server, and does this >> have all user rights to execute want it should on the target server? >> >> Regards, >> Wellington. >> >> >> 2013/8/12 Kasa V Varun Tej >> >>> Folks, >>> >>> I have been working on this oozie SSH action from past 2 days. I'm >>> unable to implement anything using SSH action. I'm facing some permissions >>> issues, so i thought if someone can provide me with some information how it >>> actually works, it may help me debug the issues i'm facing. >>> >>> Task i want to perform is to read a file on a particular node and push >>> those values to email action. >>> >>> Thanks, >>> Kasa >>> >>> >>> >> > --047d7b604eb2d396e704e3bdbf89 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I had similar issue before... I'm not sure, = but I think in my case oozie was always connecting through ssh as oozie use= r, event if I was running it as a different user. If it's not a big eff= ort to you, I would recommend you to try create oozie usr in your edge node= and give it all required rights to perform your action.

Cheers,
Wellington.
=

2013/8/12 Kasa V Varun Tej <kasavarun= @gmail.com>
Hi WC,

I= 'm triggering the job as root user and i want to run some command on th= e edge node.
Yes i made sure of the permissions.

Thanks,
Kasa



On Mon, Aug 12, 2013 at 3:07 PM, Wellington Chevreuil &l= t;welli= ngton.chevreuil@gmail.com> wrote:
Hi Kasa,
=
did you create the oozie user on the target ssh server, and does = this have all user rights to execute want it should on the target server?
Regards,
Wellington.


2013/8/12 Kasa V Varun Tej <kasavarun@gmail.com&g= t;
Folks,

I have been working on this oozi= e SSH action from past 2 days. I'm unable to implement anything using S= SH action. I'm facing some permissions issues, so i thought if someone = can provide me with some information how it actually works, it may help me = debug the issues i'm facing.

Task i want to perform is to read a file on a particula= r node and push those values to email action.

Than= ks,
Kasa





--047d7b604eb2d396e704e3bdbf89--