You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@oozie.apache.org by Savitha Devi Inbasekaran <Sa...@smartek21.com> on 2014/04/06 15:31:01 UTC
Oozie not starting in Amazon EMR
Hi All,
I installed Apache Oozie in Amazon EMR. I was able to do the complete installation without any issue. But the problem is when I tried to check the oozie status I am getting the error.
"Error: IO_ERROR : java.net.ConnectException: Connection refused"
Command I used to check the status : bin/oozie admin -oozie http://localhost:11000/oozie -status
I have attached the full trace of the error.
Any help would be appreciated.
Thanks!
RE: Oozie not starting in Amazon EMR
Posted by Savitha Devi Inbasekaran <Sa...@smartek21.com>.
I have added the jar files in /libext and tried even that is throwing same error.
-----Original Message-----
From: Mona Chitnis [mailto:chitnis@yahoo-inc.com]
Sent: Monday, April 07, 2014 10:36 PM
To: user@oozie.apache.org
Subject: Re: Oozie not starting in Amazon EMR
Savitha,
You don¹t manually need to add jars to
"/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-server/web
apps/oozie/WEB-INF/lib". The contents of libext will be injected to that location. Also you don¹t need to put those same jars in "oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/lib/³. This location is not used by tomcat for classpath as far as I can see.
So just fix the contents of the libext to include all hadoop, derby related jars and rerun the oozie-setup step
On 4/7/14, 7:01 AM, "Tousif" <to...@gmail.com> wrote:
>Did you add required library jar files(hadoop jar) into libext folder ?
>
>
>On Mon, Apr 7, 2014 at 6:32 PM, Savitha Devi Inbasekaran <
>Savithadi@smartek21.com> wrote:
>
>> Hi All,
>>
>>
>>
>> Today again I tried to install in another EMR cluster I am getting
>> the same error. But different error trace. Attached the same.
>>
>> Followed the below link for installation:
>>
>> http://pkavuri.blogspot.in/2013/08/oozie-installation-is-simplified.h
>> tml
>>
>>
>>
>> The following steps I did after encountering the error:
>>
>> · Moved the Hadoop and common jar files to the folders
>>
>>"/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-serve
>>r/w
>>ebapps/oozie/WEB-INF/lib"
>> and "oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/lib/"
>>
>> · Installed derby in oozie-3.3.2/libext
>>
>>
>>
>> Thanks,
>>
>> Savitha
>>
>>
>>
>> *From:* Savitha Devi Inbasekaran [mailto:Savithadi@smartek21.com]
>> *Sent:* Sunday, April 06, 2014 7:01 PM
>> *To:* 'user@oozie.apache.org'
>> *Subject:* Oozie not starting in Amazon EMR
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I installed Apache Oozie in Amazon EMR. I was able to do the complete
>> installation without any issue. But the problem is when I tried to
>> check the oozie status I am getting the error.
>>
>>
>>
>> "Error: IO_ERROR : java.net.ConnectException: Connection refused"
>>
>>
>>
>> Command I used to check the status : bin/oozie admin -oozie
>> http://localhost:11000/oozie -status
>>
>>
>>
>> I have attached the full trace of the error.
>>
>>
>>
>> Any help would be appreciated.
>>
>>
>>
>> Thanks!
>>
>
>
>
>--
>
>
>Regards
>Tousif Khazi
Re: Oozie not starting in Amazon EMR
Posted by Mona Chitnis <ch...@yahoo-inc.com>.
Savitha,
You don¹t manually need to add jars to
"/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-server/web
apps/oozie/WEB-INF/lib". The contents of libext will be injected to that
location. Also you don¹t need to put those same jars in
"oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/lib/³. This
location is not used by tomcat for classpath as far as I can see.
So just fix the contents of the libext to include all hadoop, derby
related jars and rerun the oozie-setup step
On 4/7/14, 7:01 AM, "Tousif" <to...@gmail.com> wrote:
>Did you add required library jar files(hadoop jar) into libext folder ?
>
>
>On Mon, Apr 7, 2014 at 6:32 PM, Savitha Devi Inbasekaran <
>Savithadi@smartek21.com> wrote:
>
>> Hi All,
>>
>>
>>
>> Today again I tried to install in another EMR cluster I am getting the
>> same error. But different error trace. Attached the same.
>>
>> Followed the below link for installation:
>>
>> http://pkavuri.blogspot.in/2013/08/oozie-installation-is-simplified.html
>>
>>
>>
>> The following steps I did after encountering the error:
>>
>> · Moved the Hadoop and common jar files to the folders
>>
>>"/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-server/w
>>ebapps/oozie/WEB-INF/lib"
>> and "oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/lib/"
>>
>> · Installed derby in oozie-3.3.2/libext
>>
>>
>>
>> Thanks,
>>
>> Savitha
>>
>>
>>
>> *From:* Savitha Devi Inbasekaran [mailto:Savithadi@smartek21.com]
>> *Sent:* Sunday, April 06, 2014 7:01 PM
>> *To:* 'user@oozie.apache.org'
>> *Subject:* Oozie not starting in Amazon EMR
>>
>>
>>
>> Hi All,
>>
>>
>>
>> I installed Apache Oozie in Amazon EMR. I was able to do the complete
>> installation without any issue. But the problem is when I tried to check
>> the oozie status I am getting the error.
>>
>>
>>
>> "Error: IO_ERROR : java.net.ConnectException: Connection refused"
>>
>>
>>
>> Command I used to check the status : bin/oozie admin -oozie
>> http://localhost:11000/oozie -status
>>
>>
>>
>> I have attached the full trace of the error.
>>
>>
>>
>> Any help would be appreciated.
>>
>>
>>
>> Thanks!
>>
>
>
>
>--
>
>
>Regards
>Tousif Khazi
Re: Oozie not starting in Amazon EMR
Posted by Tousif <to...@gmail.com>.
Did you add required library jar files(hadoop jar) into libext folder ?
On Mon, Apr 7, 2014 at 6:32 PM, Savitha Devi Inbasekaran <
Savithadi@smartek21.com> wrote:
> Hi All,
>
>
>
> Today again I tried to install in another EMR cluster I am getting the
> same error. But different error trace. Attached the same.
>
> Followed the below link for installation:
>
> http://pkavuri.blogspot.in/2013/08/oozie-installation-is-simplified.html
>
>
>
> The following steps I did after encountering the error:
>
> · Moved the Hadoop and common jar files to the folders
> "/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-server/webapps/oozie/WEB-INF/lib"
> and "oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/lib/"
>
> · Installed derby in oozie-3.3.2/libext
>
>
>
> Thanks,
>
> Savitha
>
>
>
> *From:* Savitha Devi Inbasekaran [mailto:Savithadi@smartek21.com]
> *Sent:* Sunday, April 06, 2014 7:01 PM
> *To:* 'user@oozie.apache.org'
> *Subject:* Oozie not starting in Amazon EMR
>
>
>
> Hi All,
>
>
>
> I installed Apache Oozie in Amazon EMR. I was able to do the complete
> installation without any issue. But the problem is when I tried to check
> the oozie status I am getting the error.
>
>
>
> "Error: IO_ERROR : java.net.ConnectException: Connection refused"
>
>
>
> Command I used to check the status : bin/oozie admin -oozie
> http://localhost:11000/oozie -status
>
>
>
> I have attached the full trace of the error.
>
>
>
> Any help would be appreciated.
>
>
>
> Thanks!
>
--
Regards
Tousif Khazi
RE: Oozie not starting in Amazon EMR
Posted by Savitha Devi Inbasekaran <Sa...@smartek21.com>.
Hi All,
Today again I tried to install in another EMR cluster I am getting the same error. But different error trace. Attached the same.
Followed the below link for installation:
http://pkavuri.blogspot.in/2013/08/oozie-installation-is-simplified.html
The following steps I did after encountering the error:
* Moved the Hadoop and common jar files to the folders "/oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/oozie-server/webapps/oozie/WEB-INF/lib" and "oozie-3.3.2/distro/target/oozie-3.3.2-distro/oozie-3.3.2/lib/"
* Installed derby in oozie-3.3.2/libext
Thanks,
Savitha
From: Savitha Devi Inbasekaran [mailto:Savithadi@smartek21.com]
Sent: Sunday, April 06, 2014 7:01 PM
To: 'user@oozie.apache.org'
Subject: Oozie not starting in Amazon EMR
Hi All,
I installed Apache Oozie in Amazon EMR. I was able to do the complete installation without any issue. But the problem is when I tried to check the oozie status I am getting the error.
"Error: IO_ERROR : java.net.ConnectException: Connection refused"
Command I used to check the status : bin/oozie admin -oozie http://localhost:11000/oozie -status
I have attached the full trace of the error.
Any help would be appreciated.
Thanks!