incubator-ambari-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hitesh Shah <hit...@hortonworks.com>
Subject Re: Ambari 0.9 install won't start
Date Tue, 14 Aug 2012 16:08:05 GMT
Hi Artem, 

Logs to look at:
   - httpd errors logs if there is some issue with the UI or this can show dependency issues
at times when the UI fails to come up
   - main ambari log is /var/log/hmc/hmc.log  - log level controlled by /usr/share/hmc/php/conf/Config.inc
   - puppet logs - there is a /var/log/puppet_agent.log and puppet_apply.log on each agent
host. 
       - puppet agent log is the overall agent log
       - puppet apply log contains the log for the last set of actions for which puppet was
triggered ( gets overwritten each time puppet does something on an agent host )
           - puppet apply log gets pushed into agent.log after each run 
   - sqlite db
       - The transaction and subtransaction status table 
       - every time you take an action on the UI - say deploy or reconfigure something, a
new row in transaction table is created.
       - each transaction may result in a series of steps to be done. these are recorded in
subtransactionstatus. 
       - subtransactionstatus table has txn-id:sub-txn-id:parent-sub-txn-id - this maps into
/var/lib/puppet/reports
       - each txn is done within a background process so some of its logs go into /var/log/hmc/hmc.<txn>.log
    - checking puppet report logs
       - lets consider that during a deploy something failed. Look at the subtxnstatus table
based on above and find the id which failed.
       - check entry in db to see how many failed or timed out. 
       - for failed, look at the relevant dir under var/lib/puppet/reports - there will be
one report per host in the appropriate dir. 
    - for some certain operations like adding nodes ( which bootstraps the node and installs
puppet on it )
       - such commands cannot use puppet of course 
       - the outputs for the setup commands are in directories /var/run/hmc/clusters/<cluster
name>/<stage dir>/

JDK:
   - you should be able to switch to using _33 easily. The code currently has been hardcoded
to _26. You can grep through the source for jdk and or _26 and change all the revelant matches
you find to _33. After that, it is a just a question of re-building and retrying the installs.

   - you may need to remove the 26 install from all hosts before re-trying ( look for /usr/jdk32
and /usr/jdk64 IIRC - these should symlink to the _26 installs )
   - If you get the above changes working, please go ahead and file a jira and submit a patch.

BigTop: 
   - Yes - the plan has always been to have Ambari work with BigTop. BigTop would provide
the packages and repo for the hadoop ecosystem and Ambari would deploy them. It is something
which we have been planning to address but have not gotten around to yet. 

thanks
 -- Hitesh


On Aug 14, 2012, at 4:59 AM, Artem Ervits wrote:

> Ok I did stop the firewall but I didn't touch SElinux this time. I will try that and
look at those logs. Which brings me to the next question. What are some of the most common
logs to look at for errors in general and question #2. I am pushing jdk update 26 to /var/run/hmc/downloads.
There is a 33 update available I believe. That didn't work for me when I was playing with
the 1.0 branch install. I'm concerned about security and prefer to install latest patches.
Please elaborate. Actually question #3. What is the reasoning behind having a project like
Ambari and then having a project like BigTop separately. I think merging the two makes a lot
of sense to me. The ease of install of BigTop with monitoring and ease of deployment of Ambari.

> 
> Thank you for the wonderful product! 
> 
> 
> Artem Ervits
> Data Analyst
> New York Presbyterian Hospital
> 
> ----- Original Message -----
> From: Hitesh Shah [mailto:hitesh@hortonworks.com]
> Sent: Tuesday, August 14, 2012 02:39 AM
> To: ambari-user@incubator.apache.org <ambari-user@incubator.apache.org>
> Subject: Re: Ambari 0.9 install won't start
> 
> Try doing an iptables stop or disable selinux if that is blocking something. 
> 
> Anything in the httpd access or error logs? 
> 
> -- Hitesh 
> 
> On Aug 13, 2012, at 7:31 PM, Artem Ervits wrote:
> 
>> Hello all,
>> 
>> I did an install using HDP repo and 0.9 branch, the install went without any major
issues. The Ambari service started w/out any problems. However, the UI won't show, the browser
window just sits there blank. No error and no output. Any advice would be nice.
>> 
>> 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.
>> 
>> --------------------
>> 
>> 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.
>> 
>> 
>> --------------------
>> 
>> 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.
>> 
>> 
>> 
> 
> 
> 
> --------------------
> 
> 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.
> 
> 
> 
> 
> --------------------
> 
> 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