incubator-ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Artem Ervits <are9...@nyp.org>
Subject Re: I am facing issues while using ambari for hadoop installtions
Date Wed, 11 Sep 2013 12:01:10 GMT
That happens to me actually. Try running "ps aux / grep yum" and you will see that yum is in
fact trying to install. I also like to do a manual yum install just to make sure nothing times
out there. Knowing which packages are being installed and manually installing them will let
Ambari go on further.


Artem Ervits
Data Analyst
New York Presbyterian Hospital

From: Yusaku Sako [mailto:yusaku@hortonworks.com]
Sent: Wednesday, September 11, 2013 05:36 AM
To: ambari-user@incubator.apache.org <ambari-user@incubator.apache.org>
Subject: Re: I am facing issues while using ambari for hadoop installtions

Anil,

While you are at it, please make sure that PackageKit is disabled:
http://incubator.apache.org/ambari/1.2.5/installing-hadoop-using-ambari/content/ambari-chap1-5-7.html

Not sure if this is related but I have run into similar issues where the install process hangs
at 3% ("Waiting to install X") for a very long time.
This happens when install fails initially (timeout, no more mirrors to retry, etc.) and then
clicking on Retry afterwards.
What seems to be happening is that yum install tasks that were queued by the previous install
request continue to run in the background.  Retry triggers a new set of install tasks and
issues yum install.  This overlaps with the existing yum installs and ends up taking a very
long time (perhaps due to yum lock).

Yusaku

On Tue, Sep 10, 2013 at 9:22 PM, Sumit Mohanty <smohanty@hortonworks.com<mailto:smohanty@hortonworks.com>>
wrote:
What is the OS/linux version you are using? Also, check if you have HDP.repo file at /etc/yum.repos.d.
It could be that "yum install …" is timing out while trying to install data nodes.

-Sumit

From: Sumit Mohanty <smohanty@hortonworks.com<mailto:smohanty@hortonworks.com>>
Date: Tuesday, September 10, 2013 9:18 PM

To: <ambari-user@incubator.apache.org<mailto:ambari-user@incubator.apache.org>>
Subject: Re: I am facing issues while using ambari for hadoop installtions

Anil,

This version is the latest. And this one has the fix for the issue where server can timeout
but the agent may not.

Can you get the following details:

  *   The request details for the latest request
     *   curl –u username:password http://host:8080/api/v1/clusters/<clustername>/requests<http://host:8080/api/v1/clusters/%3Cclustername%3E/requests>/
will tell you the list of requests and the one with highest id is the latest
     *   Get the details for all tasks associated with the request http://host:8080/api/v1/clusters/<clustername>/requests<http://host:8080/api/v1/clusters/%3Cclustername%3E/requests>/N/tasks?fields=Tasks/*
  *   For tasks that failed, look at the task output (also at /var/lib/ambari-agent/data/output-M.txt
where M is the task id)
  *   Look at the ambari-agent log, for log entries that contain site-M.pp (they will tell
you when the task started and when/if the ended)
  *   Look at the ambari-agent out file for any error
  *   Lets get the current state of the host components. For e.g.
     *   http://localhost:8080/api/v1/clusters/<clustername>/hosts/<hostname>/host_components?fields=HostRoles/state<http://localhost:8080/api/v1/clusters/%3Cclustername%3E/hosts/%3Chostname%3E/host_components?fields=HostRoles/state>
     *   Using the above, we can issue api calls to process one component at a time to debug

Are you stuck at the HDP installation wizard?

Thanks
Sumit

From: AnilKumar B <akumarb2010@gmail.com<mailto:akumarb2010@gmail.com>>
Reply-To: <ambari-user@incubator.apache.org<mailto:ambari-user@incubator.apache.org>>
Date: Tuesday, September 10, 2013 8:30 PM
To: <ambari-user@incubator.apache.org<mailto:ambari-user@incubator.apache.org>>
Subject: Re: I am facing issues while using ambari for hadoop installtions

Should I install another version and try?

Thanks & Regards,
B Anil Kumar.


On Wed, Sep 11, 2013 at 8:54 AM, AnilKumar B <akumarb2010@gmail.com<mailto:akumarb2010@gmail.com>>
wrote:
Hi Siddharth,

Please find the versions below. Is there any issue in this version?
ambari-server-1.2.5.17-1.noarch
ambari-agent-1.2.5.17-1.x86_64

Thanks,
B Anil Kumar.



Thanks & Regards,
B Anil Kumar.


On Tue, Sep 10, 2013 at 11:52 PM, Siddharth Wagle <swagle@hortonworks.com<mailto:swagle@hortonworks.com>>
wrote:
rpm -qa | grep ambari

There is also a version file stored for agent and server at installation time,
Server: /var/lib/ambari-server/resources/version
Agent: /var/lib/ambari-agent/data/version


On Tue, Sep 10, 2013 at 11:04 AM, AnilKumar B <akumarb2010@gmail.com<mailto:akumarb2010@gmail.com>>
wrote:
Hi Siddharth,

How can I check exact ambari-server version?

In ambari.repo it is mentioned as 1.x, and below paths we have 1.2.0, 1.2.1, 1.3.0, 1.3.2

[root@xyz HDPLocal]# pwd
/var/lib/ambari-server/resources/stacks/HDPLocal
[root@xyz HDPLocal]# ls
1.2.0  1.2.1  1.3.0  1.3.2




Thanks & Regards,
B Anil Kumar.


On Tue, Sep 10, 2013 at 10:27 PM, Siddharth Wagle <swagle@hortonworks.com<mailto:swagle@hortonworks.com>>
wrote:
Hi Anil,

Looking at this log statement, "08:59:15,984  WARN ActionManager:128 - The task 7 is not in
progress, ignoring update", hints that the task has timed out on the server but the agent
sent a command report after the task timed out. These was a fix for these in the 1.2.5, where
he puppet task would be killed after timeout.

Could you please provide the server and agent versions that you are running?

Best Regards,
Sid


On Tue, Sep 10, 2013 at 7:58 AM, Sumit Mohanty <smohanty@hortonworks.com<mailto:smohanty@hortonworks.com>>
wrote:
Anil,

Did the command/task eventually time out? Were you able to retry after that?

Can you check

From: xiong <casic_2010@126.com<mailto:casic_2010@126.com>>
Reply-To: <ambari-user@incubator.apache.org<mailto:ambari-user@incubator.apache.org>>
Date: Tuesday, September 10, 2013 6:11 AM
To: <ambari-user@incubator.apache.org<mailto:ambari-user@incubator.apache.org>>
Subject: Re:Re: I am facing issues while using ambari for hadoop installtions

 what about your ambari-agent's configure(locate in /etc/ambari-agent/conf/ambari-agent.ini)?



At 2013-09-10 19:00:11,"AnilKumar B" <akumarb2010@gmail.com<mailto:akumarb2010@gmail.com>>
wrote:
Can anyone help me in resolving this?  From ambari-agent's log, all of them kept into queue
and it's saying no command received from server.


Thanks & Regards,
B Anil Kumar.


On Tue, Sep 10, 2013 at 2:46 PM, AnilKumar B <akumarb2010@gmail.com<mailto:akumarb2010@gmail.com>>
wrote:
I am trying to set up 5 node cluster with Ambari. And install progress on ambari-server UI
is always 3%. It's not at all progressing.

May I know, what could be the issues? Please find the below logs:

1) Ambari-server log:

08:59:15,982  INFO HeartBeatHandler:113 - Received heartbeat from host, hostname=osvm-122-12002.os1.stratus.slc.ebay.com<http://osvm-122-12002.os1.stratus.slc.ebay.com>,
currentResponseId=982, receivedResponseId=982
08:59:15,984  WARN ActionManager:128 - The task 7 is not in progress, ignoring update
08:59:15,985  INFO AgentResource:109 - Sending heartbeat response with response id 983

2) Ambari-agent's log:
INFO 2013-09-10 08:59:02,045 Controller.py:180 - No commands sent from the Server.
INFO 2013-09-10 08:59:07,051 Heartbeat.py:70 - Sending heartbeat with response id: 911 and
timestamp: 1378828747050. Command(s) in progress: True. Components mapped: True
INFO 2013-09-10 08:59:07,140 ActionQueue.py:82 - Adding STATUS_COMMAND for service HBASE of
cluster base to the queue.
INFO 2013-09-10 08:59:07,156 ActionQueue.py:82 - Adding STATUS_COMMAND for service ZOOKEEPER
of cluster base to the queue.
INFO 2013-09-10 08:59:07,177 ActionQueue.py:82 - Adding STATUS_COMMAND for service HDFS of
cluster Hbase to the queue.
INFO 2013-09-10 08:59:07,194 ActionQueue.py:82 - Adding STATUS_COMMAND for service MAPREDUCE
of cluster base to the queue.
INFO 2013-09-10 08:59:07,211 ActionQueue.py:82 - Adding STATUS_COMMAND for service HBASE of
cluster base to the queue.
INFO 2013-09-10 08:59:07,229 ActionQueue.py:82 - Adding STATUS_COMMAND for service GANGLIA
of cluster base to the queue.
INFO 2013-09-10 08:59:07,233 Controller.py:180 - No commands sent from the Server.
INFO 2013-09-10 08:59:12,239 Heartbeat.py:70 - Sending heartbeat with response id: 912 and
timestamp: 1378828752239. Command(s) in progress: True. Components mapped: True
INFO 2013-09-10 08:59:12,542 Controller.py:180 - No commands sent from the Server.
INFO 2013-09-10 08:59:17,549 Heartbeat.py:70 - Sending heartbeat with response id: 913 and
timestamp: 1378828757548. Command(s) in progress: True. Components mapped: True
INFO 2013-09-10 08:59:17,563 Controller.py:180 - No commands sent from the Server.
INFO 2013-09-10 08:59:22,569 Heartbeat.py:70 - Sending heartbeat with response id: 914 and
timestamp: 1378828762568. Command(s) in progress: True. Components mapped: True
INFO 2013-09-10 08:59:22,582 Controller.py:180 - No commands sent from the Server.
INFO 2013-09-10 08:59:27,587 Heartbeat.py:70 - Sending heartbeat with response id: 915 and
timestamp: 1378828767587. Command(s) in progress: True. Components mapped: True
INFO 2013-09-10 08:59:27,600 Controller.py:180 - No commands sent from the Server.


Thanks & Regards,
B Anil Kumar.




CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.


CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.



CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.



CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.


CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to which it is addressed
and may contain information that is confidential, privileged and exempt from disclosure under
applicable law. If the reader of this message is not the intended recipient, you are hereby
notified that any printing, copying, dissemination, distribution, disclosure or forwarding
of this communication is strictly prohibited. If you have received this communication in error,
please contact the sender immediately and delete it from your system. Thank You.

This electronic message is intended to be for the use only of the named recipient, and may
contain information that is confidential or privileged.  If you are not the intended recipient,
you are hereby notified that any disclosure, copying, distribution or use of the contents
of this message is strictly prohibited.  If you have received this message in error or are
not the named recipient, please notify us immediately by contacting the sender at the electronic
mail address noted above, and delete and destroy all copies of this message.  Thank you.
Mime
View raw message