hadoop-mapreduce-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Chris Nauroth <cnaur...@hortonworks.com>
Subject Re: broken start-all.sh script
Date Tue, 05 May 2015 16:07:51 GMT
Hello Mahmood,

This looks similar to the problem reported in jira HADOOP-10988.

https://issues.apache.org/jira/browse/HADOOP-10988

The root cause appears to have something to do with running the 32-bit
libhadoop.so included in the tar ball on a 64-bit architecture.  In your
case, it appears that this triggers some kind of special handling which
then throws off the launch scripts.

You have a few options for resolving this:

1. Run without the native code by getting rid of the bundled libhadoop.so.
 Your cluster will be functional, but you'll miss out on a few features
and performance enhancements.

2. Rebuild the native code for your platform as documented here:
http://hadoop.apache.org/docs/r2.7.0/hadoop-project-dist/hadoop-common/Nati
veLibraries.html


3. Use Bigtop for a complete packaging solution that lets you install from
rpm or deb packages.
http://bigtop.apache.org/


I hope this helps.

--Chris Nauroth


From:  Mahmood N <nt_mahmood@yahoo.com>
Reply-To:  "user@hadoop.apache.org" <user@hadoop.apache.org>, Mahmood N
<nt_mahmood@yahoo.com>
Date:  Tuesday, May 5, 2015 at 1:10 AM
To:  "user@hadoop.apache.org" <user@hadoop.apache.org>
Subject:  broken start-all.sh script


Hi,
May I ask what does the following messages mean? I have extracted a fresh
downloaded package of hadoop 2.2.0


[mahmood@tiger ~]$ which start-all.sh
~/bigdatabench/apache/hadoop-2.2.0/sbin/start-all.sh

[mahmood@tiger ~]$ start-all.sh
This script is Deprecated. Instead use start-dfs.sh and start-yarn.sh
15/05/05 12:37:00 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
Starting namenodes on [OpenJDK 64-Bit Server VM warning: You have loaded
library 
/home/mahmood/bigdatabench/apache/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
<libfile>', or link it with '-z noexecstack'.
localhost]
sed: -e expression #1, char 6: unknown option to `s'
-c: Unknown cipher type 'cd'
localhost: starting namenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-2.2.0/logs/hadoop-mahmood-namenode
-tiger.out
noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or
service not known
stack: ssh: Could not resolve hostname stack: Name or service not known
The: ssh: Could not resolve hostname The: Name or service not known
which: ssh: Could not resolve hostname which: Name or service not known
OpenJDK: ssh: Could not resolve hostname OpenJDK: Name or service not known
the: ssh: Could not resolve hostname the: Name or service not known
now.: ssh: Could not resolve hostname now.: Name or service not known
fix: ssh: Could not resolve hostname fix: Name or service not known
library: ssh: Could not resolve hostname library: Name or service not known
VM: ssh: Could not resolve hostname VM: Name or service not known
You: ssh: Could not resolve hostname You: Name or service not known
guard.: ssh: Could not resolve hostname guard.: Name or service not known
stack: ssh: Could not resolve hostname stack: Name or service not known
try: ssh: Could not resolve hostname try: Name or service not known
recommended: ssh: Could not resolve hostname recommended: Name or service
not known
VM: ssh: Could not resolve hostname VM: Name or service not known
have: ssh: Could not resolve hostname have: Name or service not known
disabled: ssh: Could not resolve hostname disabled: Name or service not
known
It's: ssh: Could not resolve hostname It's: Name or service not known
have: ssh: Could not resolve hostname have: Name or service not known
might: ssh: Could not resolve hostname might: Name or service not known
to: ssh: Could not resolve hostname to: Name or service not known
64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known
loaded: ssh: Could not resolve hostname loaded: Name or service not known
with: ssh: Could not resolve hostname with: Name or service not known
<libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service
not known
guard: ssh: Could not resolve hostname guard: Name or service not known
with: ssh: Could not resolve hostname with: Name or service not known
it: ssh: Could not resolve hostname it: No address associated with hostname
fix: ssh: Could not resolve hostname fix: Name or service not known
'execstack: ssh: Could not resolve hostname 'execstack: Name or service
not known
warning:: ssh: Could not resolve hostname warning:: Name or service not
known
the: ssh: Could not resolve hostname the: Name or service not known
library: ssh: Could not resolve hostname library: Name or service not known
that: ssh: Could not resolve hostname that: Name or service not known
or: ssh: Could not resolve hostname or: Name or service not known
'-z: ssh: Could not resolve hostname '-z: Name or service not known
you: ssh: Could not resolve hostname you: Name or service not known
Server: ssh: Could not resolve hostname Server: Name or service not known
will: ssh: Could not resolve hostname will: Name or service not known
link: ssh: Could not resolve hostname link: Name or service not known
highly: ssh: Could not resolve hostname highly: Name or service not known
localhost: starting datanode, logging to
/home/mahmood/bigdatabench/apache/hadoop-2.2.0/logs/hadoop-mahmood-datanode
-tiger.out
Starting secondary namenodes [OpenJDK 64-Bit Server VM warning: You have
loaded library 
/home/mahmood/bigdatabench/apache/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
<libfile>', or link it with '-z noexecstack'.
0.0.0.0]
sed: -e expression #1, char 6: unknown option to `s'
-c: Unknown cipher type 'cd'
0.0.0.0: starting secondarynamenode, logging to
/home/mahmood/bigdatabench/apache/hadoop-2.2.0/logs/hadoop-mahmood-secondar
ynamenode-tiger.out
stack: ssh: Could not resolve hostname stack: Name or service not known
now.: ssh: Could not resolve hostname now.: Name or service not known
guard: ssh: Could not resolve hostname guard: Name or service not known
stack: ssh: Could not resolve hostname stack: Name or service not known
The: ssh: Could not resolve hostname The: Name or service not known
disabled: ssh: Could not resolve hostname disabled: Name or service not
known
it: ssh: Could not resolve hostname it: No address associated with hostname
have: ssh: Could not resolve hostname have: Name or service not known
VM: ssh: Could not resolve hostname VM: Name or service not known
OpenJDK: ssh: Could not resolve hostname OpenJDK: Name or service not known
Server: ssh: Could not resolve hostname Server: Name or service not known
It's: ssh: Could not resolve hostname It's: Name or service not known
recommended: ssh: Could not resolve hostname recommended: Name or service
not known
you: ssh: Could not resolve hostname you: Name or service not known
the: ssh: Could not resolve hostname the: Name or service not known
which: ssh: Could not resolve hostname which: Name or service not known
noexecstack'.: ssh: Could not resolve hostname noexecstack'.: Name or
service not known
'-z: ssh: Could not resolve hostname '-z: Name or service not known
guard.: ssh: Could not resolve hostname guard.: Name or service not known
highly: ssh: Could not resolve hostname highly: Name or service not known
will: ssh: Could not resolve hostname will: Name or service not known
the: ssh: Could not resolve hostname the: Name or service not known
with: ssh: Could not resolve hostname with: Name or service not known
VM: ssh: Could not resolve hostname VM: Name or service not known
64-Bit: ssh: Could not resolve hostname 64-Bit: Name or service not known
fix: ssh: Could not resolve hostname fix: Name or service not known
try: ssh: Could not resolve hostname try: Name or service not known
library: ssh: Could not resolve hostname library: Name or service not known
that: ssh: Could not resolve hostname that: Name or service not known
warning:: ssh: Could not resolve hostname warning:: Name or service not
known
might: ssh: Could not resolve hostname might: Name or service not known
have: ssh: Could not resolve hostname have: Name or service not known
fix: ssh: Could not resolve hostname fix: Name or service not known
You: ssh: Could not resolve hostname You: Name or service not known
library: ssh: Could not resolve hostname library: Name or service not known
with: ssh: Could not resolve hostname with: Name or service not known
or: ssh: Could not resolve hostname or: Name or service not known
'execstack: ssh: Could not resolve hostname 'execstack: Name or service
not known
<libfile>',: ssh: Could not resolve hostname <libfile>',: Name or service
not known
loaded: ssh: Could not resolve hostname loaded: Name or service not known
link: ssh: Could not resolve hostname link: Name or service not known
to: ssh: Could not resolve hostname to: Name or service not known
15/05/05 12:37:26 WARN util.NativeCodeLoader: Unable to load native-hadoop
library for your platform... using builtin-java classes where applicable
starting yarn daemons
starting resourcemanager, logging to
/home/mahmood/bigdatabench/apache/hadoop-2.2.0/logs/yarn-mahmood-resourcema
nager-tiger.out
localhost: starting nodemanager, logging to
/home/mahmood/bigdatabench/apache/hadoop-2.2.0/logs/yarn-mahmood-nodemanage
r-tiger.out
[
 
Regards,
Mahmood


Mime
View raw message