Return-Path: X-Original-To: apmail-hadoop-common-user-archive@www.apache.org Delivered-To: apmail-hadoop-common-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id DE33210D61 for ; Tue, 24 Dec 2013 07:01:31 +0000 (UTC) Received: (qmail 84851 invoked by uid 500); 24 Dec 2013 07:01:16 -0000 Delivered-To: apmail-hadoop-common-user-archive@hadoop.apache.org Received: (qmail 84479 invoked by uid 500); 24 Dec 2013 07:01:15 -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 83828 invoked by uid 99); 24 Dec 2013 07:01:13 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2013 07:01:13 +0000 X-ASF-Spam-Status: No, hits=1.7 required=5.0 tests=FREEMAIL_ENVFROM_END_DIGIT,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of nitinpawar432@gmail.com designates 209.85.128.50 as permitted sender) Received: from [209.85.128.50] (HELO mail-qe0-f50.google.com) (209.85.128.50) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 24 Dec 2013 07:01:07 +0000 Received: by mail-qe0-f50.google.com with SMTP id 1so6048114qec.37 for ; Mon, 23 Dec 2013 23:00:46 -0800 (PST) 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=rfL9siTetztTD998op8n6qh4eAPyZp5mAg6z8RWDHpc=; b=Zh/06t6juPE/16ZmZByDqMCZnwD95C+aR09raDGHC/LOCx6Phq950mnRa8W0A769R1 XSiu+ztIfEWg9zwx9BBlTfLrcCaPmxI8bkw6LwcosHxdVSlZ6jl7wtDbkiAH3I3LU/hD g0RLFSlnMQl57Y6DaaVGqMIgGegTr2cegVkIw/+g3/TF+ljEGeVwECOI9AwJEh4d+n9Z 4uKDfGw61WMck0absfqVzKlsUgWOg2vW5D7J1qVu1aZOUqXfYHYEBJe+tEpYm2FMAfsI +uEHQ7UJIOILPkz5MlZhbWUnfBZD54wWoj990VjE0aTbPPEtEdgcVrSrlUZ0MBzKJjtC nOWw== MIME-Version: 1.0 X-Received: by 10.224.67.200 with SMTP id s8mr49720883qai.75.1387868446052; Mon, 23 Dec 2013 23:00:46 -0800 (PST) Received: by 10.224.194.5 with HTTP; Mon, 23 Dec 2013 23:00:45 -0800 (PST) In-Reply-To: References: Date: Tue, 24 Dec 2013 12:30:45 +0530 Message-ID: Subject: Re: Getting error unrecognized option -jvm on starting nodemanager From: Nitin Pawar To: user@hadoop.apache.org Content-Type: multipart/alternative; boundary=001a11c3218ab8f32604ee424de7 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c3218ab8f32604ee424de7 Content-Type: text/plain; charset=ISO-8859-1 Without log, very hard to guess what's happening. Can you clean up the log directory and then start over and check for the logs again. On Tue, Dec 24, 2013 at 11:44 AM, Sitaraman Vilayannur < vrsitaramanietflists@gmail.com> wrote: > Hi Nitin, > I moved to the release 2.2.0 on starting node manager it remains > silent without errors but nodemanager dosent start....while it does in > the earlier 0.23 version > > > ./hadoop-daemon.sh start namenode > starting namenode, logging to > > /usr/local/Software/hadoop-2.2.0/logs/hadoop-sitaraman-namenode-localhost.localdomain.out > Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library > /usr/local/Software/hadoop-2.2.0/lib/native/libhadoop.so.1.0.0 which > might have disabled stack guard. The VM will try to fix the stack > guard now. > It's highly recommended that you fix the library with 'execstack -c > ', or link it with '-z noexecstack'. > [sitaraman@localhost sbin]$ jps > 13444 Jps > [sitaraman@localhost sbin]$ vi > > /usr/local/Software/hadoop-2.2.0/logs/hadoop-sitaraman-namenode-localhost.localdomain.out > > > ulimit -a for user sitaraman > core file size (blocks, -c) 0 > data seg size (kbytes, -d) unlimited > scheduling priority (-e) 0 > file size (blocks, -f) unlimited > pending signals (-i) 135104 > max locked memory (kbytes, -l) 32 > max memory size (kbytes, -m) unlimited > open files (-n) 1024 > pipe size (512 bytes, -p) 8 > POSIX message queues (bytes, -q) 819200 > real-time priority (-r) 0 > stack size (kbytes, -s) 10240 > cpu time (seconds, -t) unlimited > max user processes (-u) 135104 > virtual memory (kbytes, -v) unlimited > file locks (-x) unlimited > > > On 12/24/13, Nitin Pawar wrote: > > For now you can ignore this warning, > > it was your first program so you can try building other things and slowly > > run the commands mentioned the log message to fix these small warnings. > > > > > > On Tue, Dec 24, 2013 at 10:07 AM, Sitaraman Vilayannur < > > vrsitaramanietflists@gmail.com> wrote: > > > >> Thanks Nitin, That worked, > >> When i run the Pi example, i get the following warning at the end, > >> what must i do about this warning....thanks much for your help. > >> Sitaraman > >> inished in 20.82 seconds > >> Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library > >> /usr/local/Software/hadoop-0.23.10/lib/native/libhadoop.so.1.0.0 which > >> might have disabled stack guard. The VM will try to fix the stack > >> guard now. > >> It's highly recommended that you fix the library with 'execstack -c > >> ', or link it with '-z noexecstack'. > >> 13/12/24 10:05:19 WARN util.NativeCodeLoader: Unable to load > >> native-hadoop library for your platform... using builtin-java classes > >> where applicable > >> Estimated value of Pi is 3.14127500000000000000 > >> [sitaraman@localhost mapreduce]$ > >> > >> On 12/23/13, Nitin Pawar wrote: > >> > Can you try starting the process as non root user. > >> > Give proper permissions to the user and start it as a different user. > >> > > >> > Thanks, > >> > Nitin > >> > > >> > > >> > On Mon, Dec 23, 2013 at 2:15 PM, Sitaraman Vilayannur < > >> > vrsitaramanietflists@gmail.com> wrote: > >> > > >> >> Hi, > >> >> When i attempt to start nodemanager i get the following error. Any > >> >> help > >> >> appreciated. I was able to start resource manager datanode, > namenode > >> >> and > >> >> secondarynamenode, > >> >> > >> >> > >> >> ./yarn-daemon.sh start nodemanager > >> >> starting nodemanager, logging to > >> >> > >> > /usr/local/Software/hadoop-0.23.10/logs/yarn-root-nodemanager-localhost.localdomain.out > >> >> Unrecognized option: -jvm > >> >> Error: Could not create the Java Virtual Machine. > >> >> Error: A fatal exception has occurred. Program will exit. > >> >> [root@localhost sbin]# emacs > >> >> > >> > /usr/local/Software/hadoop-0.23.10/logs/yarn-root-nodemanager-localhost.localdomain.out > >> >> & > >> >> [4] 29004 > >> >> [root@localhost sbin]# jps > >> >> 28402 SecondaryNameNode > >> >> 30280 Jps > >> >> 28299 DataNode > >> >> 6729 Main > >> >> 26044 ResourceManager > >> >> 28197 NameNode > >> >> > >> > > >> > > >> > > >> > -- > >> > Nitin Pawar > >> > > >> > > > > > > > > -- > > Nitin Pawar > > > -- Nitin Pawar --001a11c3218ab8f32604ee424de7 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
Without log, very hard to guess what's happening.=A0
Can you clean up the log directory and then start over an= d check for the logs again.=A0

On Tue, Dec 24, 2013 at 11:44 AM, Sitaraman Vilayannur &l= t;vrsit= aramanietflists@gmail.com> wrote:
Hi Nitin,
=A0I moved to the release 2.2.0 on starting node manager it remains
silent without errors but nodemanager dosent start....while it does in
the earlier 0.23 version


./hadoop-daemon.sh start namenode
starting namenode, logging to
/usr/local/Software/hadoop-2.2.0/logs/hadoop-sitaraman-namenode-localhost.l= ocaldomain.out
Java HotSpot(TM) 64-Bit Server VM warning: You have loade= d library
/usr/local/Software/hadoop-2.2.0/lib/native/libhadoop.so.1.0.0 which<= br>
might have disabled stack guard. The VM will try to fix t= he stack
guard now.
It's highly recommended that you fix the library with 'execstack -c=
<libfile>', or link it with '-z noexecstack'.
[sitaraman@localhost sbin]$ jps
13444 Jps
[sitaraman@localhost sbin]$ vi
/usr/local/Software/hadoop-2.2.0/logs/hadoop-sitaraman-namenode-localhost.l= ocaldomain.out


ulimit -a for user sitaraman
core file size =A0 =A0 =A0 =A0 =A0(blocks, -c) 0
data seg size =A0 =A0 =A0 =A0 =A0 (kbytes, -d) unlimited
scheduling priority =A0 =A0 =A0 =A0 =A0 =A0 (-e) 0
file size =A0 =A0 =A0 =A0 =A0 =A0 =A0 (blocks, -f) unlimited
pending signals =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 (-i) 135104
max locked memory =A0 =A0 =A0 (kbytes, -l) 32
max memory size =A0 =A0 =A0 =A0 (kbytes, -m) unlimited
open files =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(-n) 1024
pipe size =A0 =A0 =A0 =A0 =A0 =A0(512 bytes, -p) 8
POSIX message queues =A0 =A0 (bytes, -q) 819200
real-time priority =A0 =A0 =A0 =A0 =A0 =A0 =A0(-r) 0
stack size =A0 =A0 =A0 =A0 =A0 =A0 =A0(kbytes, -s) 10240
cpu time =A0 =A0 =A0 =A0 =A0 =A0 =A0 (seconds, -t) unlimited
max user processes =A0 =A0 =A0 =A0 =A0 =A0 =A0(-u) 135104
virtual memory =A0 =A0 =A0 =A0 =A0(kbytes, -v) unlimited
file locks =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0(-x) unlimited


On 12/24/13, Nitin Pawar <nit= inpawar432@gmail.com> wrote:
> For now you can ignore this warning,
> it was your first program so you can try building other things and slo= wly
> run the commands mentioned the log message to fix these small warnings= .
>
>
> On Tue, Dec 24, 2013 at 10:07 AM, Sitaraman Vilayannur <
> vrsitaramanietflists= @gmail.com> wrote:
>
>> Thanks Nitin, That worked,
>> When i run the Pi example, i get the following warning at the end,=
>> what must i do about this warning....thanks much for your help. >> Sitaraman
>> inished in 20.82 seconds
>> Java HotSpot(TM) 64-Bit Server VM warning: You have loaded library=
>> /usr/local/Software/hadoop-0.23.10/lib/native/libhadoop.so.1.0.0 w= hich
>> might have disabled stack guard. The VM will try to fix the stack<= br> >> guard now.
>> It's highly recommended that you fix the library with 'exe= cstack -c
>> <libfile>', or link it with '-z noexecstack'. >> 13/12/24 10:05:19 WARN util.NativeCodeLoader: Unable to load
>> native-hadoop library for your platform... using builtin-java clas= ses
>> where applicable
>> Estimated value of Pi is 3.14127500000000000000
>> [sitaraman@localhost mapreduce]$
>>
>> On 12/23/13, Nitin Pawar <nitinpawar432@gmail.com> wrote:
>> > Can you try starting the process as non root user.
>> > Give proper permissions to the user and start it as a differe= nt user.
>> >
>> > Thanks,
>> > Nitin
>> >
>> >
>> > On Mon, Dec 23, 2013 at 2:15 PM, Sitaraman Vilayannur < >> > vrsitaraman= ietflists@gmail.com> wrote:
>> >
>> >> Hi,
>> >> =A0When i attempt to start nodemanager i get the followin= g error. Any
>> >> help
>> >> appreciated. =A0 I was able to start resource manager dat= anode, namenode
>> >> and
>> >> secondarynamenode,
>> >>
>> >>
>> >> =A0 =A0./yarn-daemon.sh start nodemanager
>> >> starting nodemanager, logging to
>> >>
>> /usr/local/Software/hadoop-0.23.10/logs/yarn-root-nodemanager-loca= lhost.localdomain.out
>> >> Unrecognized option: -jvm
>> >> Error: Could not create the Java Virtual Machine.
>> >> Error: A fatal exception has occurred. Program will exit.=
>> >> [root@localhost sbin]# emacs
>> >>
>> /usr/local/Software/hadoop-0.23.10/logs/yarn-root-nodemanager-loca= lhost.localdomain.out
>> >> &
>> >> [4] 29004
>> >> [root@localhost sbin]# jps
>> >> 28402 SecondaryNameNode
>> >> 30280 Jps
>> >> 28299 DataNode
>> >> 6729 Main
>> >> 26044 ResourceManager
>> >> 28197 NameNode
>> >>
>> >
>> >
>> >
>> > --
>> > Nitin Pawar
>> >
>>
>
>
>
> --
> Nitin Pawar
>



--
= Nitin Pawar
--001a11c3218ab8f32604ee424de7--